Compare commits

...

214 Commits

Author SHA1 Message Date
github-actions[bot] 150f71e20d Automatic translations update 2026-05-07 14:00:32 +00:00
Catalan Lover 4af35777b3 Update Draupnir from 3.0.0 to 3.1.0 and introduce Zero Touch Deployment to mdad. (#5205) 2026-05-07 16:59:53 +03:00
github-actions[bot] d6a1679cad Automatic translations update 2026-05-07 14:55:32 +03:00
Slavi Pantaleev 2b082eea26 Attribute Tuwunel's status as the conduwuit successor
The former conduwuit maintainer (@x86pup, formerly @girlbossceo)
clarified in the PR thread that they endorse Tuwunel as conduwuit's
successor, and the archived conduwuit repo's README points there too.
Update the migration section in the conduwuit doc and the Tuwunel
CHANGELOG entry to reflect this with attribution.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/5200.
2026-05-07 14:15:11 +03:00
renovate[bot] 1846f7be27 Update dependency sable to v1.15.2-0 2026-05-07 13:56:37 +03:00
renovate[bot] 2393b31ebc Update dependency valkey to v9.0.4-0 2026-05-07 09:58:20 +03:00
renovate[bot] 68cc4a1c12 Update dependency etherpad to v2.7.3-0 2026-05-07 09:58:17 +03:00
Slavi Pantaleev 7d904e6a02 update-translations.yml: pin astral-sh/setup-uv to v8.1.0
Upstream stopped publishing rolling major/minor tags (v8, v8.0) as
of their v8.0.0 release for supply-chain security reasons, breaking
our workflow which referenced @v8.
2026-05-07 09:57:17 +03:00
Slavi Pantaleev 600d04ad16 CHANGELOG.md: announce Tuwunel support
Adds a top-level entry mirroring the style of the past Continuwuity
announcement: brief intro, the conduwuit-fork lineage, the migration
path via the binary-swap tag, and the standard caveat about not being
able to swap homeserver implementations on an existing deployment.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/5200.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-07 09:49:31 +03:00
Slavi Pantaleev b171429e9f configuring-playbook-conduwuit.md: link Tuwunel as a migration target
Previously only Continuwuity was offered as a migration path. Tuwunel
is a fork of conduwuit which reads the database directly via the new
`tuwunel-migrate-from-conduwuit` tag, so it deserves a parallel entry.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/5200.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-07 09:48:02 +03:00
Slavi Pantaleev e53d828157 matrix-tuwunel: pin version to v1.6.1
Repo convention is to pin homeserver-role versions to a specific tag
so renovate can track updates and so the deployment is reproducible.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/5200.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-07 09:47:22 +03:00
Jason Volk c111008d25 matrix-tuwunel: add Tuwunel homeserver role (#5200)
Tuwunel is a Matrix homeserver maintained by the matrix-construct
organisation. See https://matrix-construct.github.io/tuwunel/.

The rendered TOML emits only keys exposed as Ansible variables; the
rest fall back to tuwunel's upstream defaults. Anything not surfaced
can be set via the TUWUNEL_* env extension or by overriding the
template path.

Popular features Tuwunel adds variables for:

- OAuth2/OIDC identity providers (a list of `[[global.identity_provider]]`
  blocks; brand-aware defaults for Google, GitHub, Keycloak, MAS, etc)
- LDAP and JWT authentication
- Media storage providers (native local and S3 with multipart upload)
- RocksDB tuning (compression, direct_io, parallelism, online backups)
- Native TLS dual-protocol mode
- Blurhashing, Sentry crash reporting

Auto-wired from existing playbook globals: well-known client URL,
TURN/coturn, MatrixRTC LiveKit URL, federation.

The `tuwunel-migrate-from-conduwuit` tag performs a binary-swap
migration. Migration from any other Conduit derivative is unsupported
and would corrupt the database.

Signed-off-by: Jason Volk <jason@zemos.net>
2026-05-07 09:45:29 +03:00
renovate[bot] 5251be8691 Update dependency markdown-it-py to v4.1.0 2026-05-06 21:06:24 +03:00
Suguru Hirahara 94db291c85 Update maintenance-upgrading-services.md: add a section about the migration validation system
Signed-off-by: Suguru Hirahara <did:key:z6MkvVZk1A3KBApWJXv2Ju4H14ErDfRGxh8zxdXSZ4vACDg5>
2026-05-06 16:58:20 +03:00
renovate[bot] ce5b429a06 Update docker.io/metio/matrix-alertmanager-receiver Docker tag to v2026.5.6 2026-05-06 12:21:36 +03:00
Suguru Hirahara f6766d66fb Update the instruction to update the playbook and role without using just or make
Signed-off-by: Suguru Hirahara <did:key:z6MkvVZk1A3KBApWJXv2Ju4H14ErDfRGxh8zxdXSZ4vACDg5>
2026-05-06 12:20:40 +03:00
renovate[bot] e93e376497 Update dependency traefik to v3.7.0-0 2026-05-06 08:20:45 +03:00
renovate[bot] b56e28df6b Update dependency sable to v1.15.1-0 2026-05-06 08:17:00 +03:00
renovate[bot] 6ea36fa521 Update dependency prek to v0.3.13 2026-05-05 21:44:35 +03:00
renovate[bot] 9d6be858f1 Update dependency prek to v0.3.12 2026-05-05 14:52:39 +03:00
Slavi Pantaleev f475710150 requirements.yml: bump 22 mash roles to versions using modern community.docker modules
These external roles were modernized to switch off the deprecated-shape
`community.docker.docker_image` module in favour of `docker_image_pull`
and `docker_image_build`, matching the in-tree role sweep.

Roles bumped: backup_borg, cinny, container_socket_proxy, coturn,
ddclient, etherpad, exim_relay, grafana, hydrogen, jitsi, livekit_server,
ntfy, postgres, postgres_backup, prometheus, prometheus_nginxlog_exporter,
prometheus_node_exporter, prometheus_postgres_exporter, sable, traefik,
traefik_certs_dumper, valkey.

Closes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 23:19:24 +03:00
Slavi Pantaleev 152a3bbc2a matrix-synapse: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules across all
four task files (synapse, reverse_proxy_companion, goofys,
rust-synapse-compress-state). Drops the `ansible_version` compatibility
ladder and removes four `_container_image_force_pull` variables (the new
pull module handles registry refresh natively via `pull: always`).

The Synapse self-build path uses `ansible.builtin.shell` for BuildKit
support and is left as-is. The customizations image build (which builds
on top of the locally-tagged synapse image) is converted to
`docker_image_build` with `pull: false`, preserving its existing
rebuild-trigger semantics.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:25:44 +03:00
Slavi Pantaleev b91ce393e6 matrix-user-verification-service: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:25:11 +03:00
Slavi Pantaleev 78e86ca354 matrix-registration: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:24:38 +03:00
Slavi Pantaleev ac7f805dcc matrix-pantalaimon: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:24:04 +03:00
Slavi Pantaleev d943939f28 matrix-synapse-auto-compressor: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:23:30 +03:00
Slavi Pantaleev 867969a823 matrix-static-files: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:22:57 +03:00
Slavi Pantaleev 9d89b317f8 matrix-matrixto: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_build` module. Drops the `ansible_version` compatibility
ladder.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:17:09 +03:00
Slavi Pantaleev 921c050e34 matrix-ldap-registration-proxy: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_build` module. Drops the `ansible_version` compatibility
ladder.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:16:35 +03:00
Slavi Pantaleev 3976c3e317 matrix-livekit-jwt-service: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:16:02 +03:00
Slavi Pantaleev dc11821f91 matrix-ketesa: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:15:29 +03:00
Slavi Pantaleev 69e9cfd053 matrix-media-repo: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:14:55 +03:00
Slavi Pantaleev a721125568 matrix-element-call: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:14:21 +03:00
Slavi Pantaleev 4f8c639350 matrix-element-admin: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:13:48 +03:00
Slavi Pantaleev f58d7b497a matrix-dendrite: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:13:15 +03:00
Slavi Pantaleev a80eac6c72 matrix-cactus-comments: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:09:37 +03:00
Slavi Pantaleev a1695ff347 matrix-client-schildichat: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:09:03 +03:00
Slavi Pantaleev 445771c9be matrix-client-fluffychat: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:08:30 +03:00
Slavi Pantaleev b6831fbd54 matrix-client-element: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:07:56 +03:00
Slavi Pantaleev 0d6fc9b766 matrix-client-commet: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:07:22 +03:00
Slavi Pantaleev ef90387ce3 matrix-continuwuity: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:06:48 +03:00
Slavi Pantaleev 1ce8ab804f matrix-conduit: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:06:15 +03:00
Slavi Pantaleev eb98f3e09f matrix-cactus-comments-client: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:05:41 +03:00
Slavi Pantaleev 0048da1638 matrix-bridge-wechat: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:01:17 +03:00
Slavi Pantaleev d9bb4cbdc0 matrix-bridge-steam: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:00:43 +03:00
Slavi Pantaleev e81f295b60 matrix-bridge-mx-puppet-steam: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 22:00:09 +03:00
Slavi Pantaleev 7e71d66d86 matrix-bridge-mx-puppet-groupme: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:59:35 +03:00
Slavi Pantaleev 2182a1bf87 matrix-bridge-beeper-linkedin: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:59:00 +03:00
Slavi Pantaleev 4b74d0b2ff matrix-bridge-appservice-kakaotalk: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:58:24 +03:00
Slavi Pantaleev f4768aeed1 matrix-bridge-mautrix-wsproxy: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:57:50 +03:00
Slavi Pantaleev d7ffb7a4c0 matrix-bridge-sms: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:57:16 +03:00
Slavi Pantaleev f84d419baf matrix-bridge-mautrix-whatsapp: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:53:22 +03:00
Slavi Pantaleev 6b6370e1f2 matrix-bridge-mautrix-twitter: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:52:49 +03:00
Slavi Pantaleev c0b3367914 matrix-bridge-mautrix-slack: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:52:17 +03:00
Slavi Pantaleev 9251e31b6c matrix-bridge-mautrix-meta-messenger: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:51:44 +03:00
Slavi Pantaleev 6bc4c22a02 matrix-bridge-mautrix-meta-instagram: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:51:11 +03:00
Slavi Pantaleev da0033330f matrix-bridge-mautrix-googlechat: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:50:38 +03:00
Slavi Pantaleev af8f92dff9 matrix-bridge-mautrix-gmessages: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:50:05 +03:00
Slavi Pantaleev 61a29571de matrix-bridge-mautrix-bluesky: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:49:32 +03:00
Slavi Pantaleev 70ee2fbecb matrix-bridge-postmoogle: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:45:32 +03:00
Slavi Pantaleev 12ec2dd157 matrix-bridge-mautrix-telegram: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:45:00 +03:00
Slavi Pantaleev c578b08183 matrix-bridge-mautrix-discord: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:44:27 +03:00
Slavi Pantaleev 509222719b matrix-bridge-hookshot: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:43:54 +03:00
Slavi Pantaleev eddebb3e12 matrix-bridge-appservice-irc: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:43:22 +03:00
Slavi Pantaleev ebd6ebaeb9 matrix-bot-maubot: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:42:48 +03:00
Slavi Pantaleev d2c604f0fa matrix-bot-matrix-reminder-bot: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:42:15 +03:00
Slavi Pantaleev 603f113c13 matrix-bot-matrix-registration-bot: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:41:42 +03:00
Slavi Pantaleev 19999f583d matrix-bot-buscarron: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:41:10 +03:00
Slavi Pantaleev c82415cd7b matrix-bot-baibot: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:40:37 +03:00
Slavi Pantaleev 5b041201a4 matrix-bridge-meshtastic-relay: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:40:04 +03:00
Slavi Pantaleev 5affe5fdd4 matrix-bridge-heisenbridge: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:39:31 +03:00
Slavi Pantaleev 4952029e0c matrix-bridge-appservice-discord: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:38:58 +03:00
Slavi Pantaleev b7d97d960d matrix-authentication-service: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:38:25 +03:00
Slavi Pantaleev 7a33b5939d matrix-rageshake: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:27:03 +03:00
Slavi Pantaleev 3d0d5d4cd5 matrix-bot-go-neb: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:26:28 +03:00
Slavi Pantaleev 28a12776a6 matrix-corporal: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:20:34 +03:00
Slavi Pantaleev 70c4490d64 matrix-bridge-mautrix-signal: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:20:00 +03:00
Slavi Pantaleev 8f9c5f0b0b matrix-bot-mjolnir: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:19:24 +03:00
Slavi Pantaleev 8ad0858725 matrix-bot-honoroit: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` and `docker_image_build` split modules. Drops the
`ansible_version` compatibility ladder and the now-redundant
`_container_image_force_pull` variable (the new pull module handles
registry refresh natively via `pull: always`). Also registers
`_container_image_build_result` so that a self-build rebuild correctly
triggers a service restart.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:18:49 +03:00
Slavi Pantaleev 8ac2ea6cb0 matrix-synapse-usage-exporter: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:18:13 +03:00
Slavi Pantaleev d3b940f706 matrix-sygnal: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:17:37 +03:00
Slavi Pantaleev 1e68a05717 matrix-alertmanager-receiver: switch to modern community.docker docker_image modules
Replaces `community.docker.docker_image` with the modern
`docker_image_pull` module. Drops the `ansible_version` compatibility
ladder and the now-redundant `_container_image_force_pull` variable
(the new pull module handles registry refresh natively via `pull: always`).

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 21:17:02 +03:00
Slavi Pantaleev d3c967ed64 collections/requirements.yml: pin community.docker to >=3.6.0
The Draupnir roles now use `community.docker.docker_image_pull` and
`community.docker.docker_image_build`, both first available in
community.docker 3.6.0 (Jan 2024, shipped with Ansible 9.2.0).

This pin only takes effect for AWX / Automation Platform users (CLI
users do not install collections from this file), but those are the
users most likely to hit the issue with a stale collection cached in
their controller.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/5187.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 16:22:07 +03:00
Slavi Pantaleev b37531b6a8 collections/requirements.yml: document purpose and audience
The file is not used by the playbook's standard CLI install flow
(`make roles` / `just roles` only install roles via ansible-galaxy, not
collections). It exists for AWX / Ansible Automation Platform users,
where it is auto-detected during project sync.

Without this comment, the file looks like an unused leftover and is a
recurring source of confusion when discussing collection version pins
(should we add one here, etc.). Documenting the actual audience makes
those decisions more obvious.

No functional change.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 16:21:20 +03:00
Slavi Pantaleev b51881c90a docs/draupnir: polish "running both modes" sections
Sentence-case the heading to match the rest of the file, fix a broken
"appservice mode](url)(Draupnir for all)" link by folding the
parenthetical into the link text, hyphenate "non-release tag" and
"force-restart", correct "a update" -> "an update", and reword "work
perfectly" to the more accurate "work correctly".

Follow-up to 75f097e55 (#5187).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 16:18:21 +03:00
Catalan Lover 75f097e55c Modernise Draupnir Role ansible modules and update restart logic (#5187) 2026-05-04 16:15:18 +03:00
renovate[bot] c0ba02c83f Update jeremiah-k/mmrelay Docker tag to v1.3.7 2026-05-03 20:04:38 +03:00
renovate[bot] 7d6a0e6f07 Update dependency traefik_certs_dumper to v2.10.0-6 2026-05-03 16:49:23 +03:00
Slavi Pantaleev d830c88275 Fix Draupnir conditional restart not triggering on force-pulled image updates
matrix-bot-draupnir and matrix-appservice-draupnir-for-all share the same
upstream container image. When both are enabled and force-pull is on
(e.g. when pinning to a rolling tag like `latest` or `main`), the second
role to run during a single playbook invocation sees the image as already
up-to-date locally because the first role just pulled it. The
community.docker.docker_image module reports `changed: false` in that
case, so the second role's restart_necessary stays false and the
conditional restart logic skips it. Result: the first service picks up
the new image on restart, while the second keeps running the old one.

For other versions which don't get force-pulled (other than `latest`),
systemd service files also get updated by the playbook and these updates
done by each role properly flip the "requires restarting" variable
regardless of pulling. So it's just force-pulling that causes the problem.

Treating force-pull itself as a restart trigger sidesteps the lossy
"did this specific pull task fetch new bytes" heuristic. The downside
is that both Draupnir services now restart on every run when force-pull
is enabled, even when the upstream image has not moved. That is a small
amount of waste compared to silently running an outdated container.

Localized to these two roles via a comment that documents the
constraint, rather than applied playbook-wide, since this is the only
known image-sharing pair and other roles do not need the extra
restarts.

Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5186

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-01 00:16:27 +03:00
Slavi Pantaleev 966368ed06 docs/federation: correct documented default for room directory exposure
Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5178
2026-04-30 14:46:49 +03:00
Slavi Pantaleev 5901f491f4 matrix-synapse: support quarantined_media_changes stream writers
Synapse v1.152 introduces a new `quarantined_media_changes` stream and
requires that any worker serving `/_synapse/admin/v1/quarantine_media/`
be declared as a writer for that stream. Otherwise quarantining media
fails on the worker.

Add `quarantined_media_changes` as a web-facing stream writer alongside
the other stream-backed APIs and route the admin endpoint via the same
explicit writer-or-main model used for `device_lists`, `thread_subscriptions`,
etc. The endpoint is removed from `matrix_synapse_workers_media_repository_endpoints`
so the old media-repository route does not shadow (or conflict with) the
new writer-or-main route. Without that move, the previously-shipping
default of routing `/quarantine_media` to the `media_repository` worker
would silently break after the v1.152.0 image bump.

Default count is 1 in the `one-of-each` and `specialized-workers` presets
(matching `device_lists`), and 0 in `little-federation-helper` (which
also has no media-repository worker, so falling back to main is fine).

Refs:
- https://github.com/element-hq/synapse/blob/develop/docs/upgrade.md#upgrading-to-v11520
- https://element-hq.github.io/synapse/latest/workers.html#the-quarantined_media_changes-stream

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-30 14:12:25 +03:00
renovate[bot] e59e6682be Update ghcr.io/element-hq/synapse Docker tag to v1.152.0 2026-04-30 14:00:49 +03:00
renovate[bot] 889df54fff Update ghcr.io/element-hq/element-web Docker tag to v1.12.17 2026-04-30 14:00:39 +03:00
renovate[bot] f7c5dd9e06 Update dependency prek to v0.3.11 2026-04-30 13:59:11 +03:00
renovate[bot] 60b66e0d73 Update dependency traefik to v3.6.15-0 2026-04-30 13:57:55 +03:00
renovate[bot] 82790be3cd Update jeremiah-k/mmrelay Docker tag to v1.3.6 2026-04-30 08:56:12 +03:00
renovate[bot] 6b9e4243e6 Update docker.io/metio/matrix-alertmanager-receiver Docker tag to v2026.4.29 2026-04-29 16:40:07 +03:00
renovate[bot] 8a7b1087c6 Update ghcr.io/element-hq/matrix-authentication-service Docker tag to v1.16.0 2026-04-28 21:00:49 +03:00
renovate[bot] 61e4a47a2d Update ghcr.io/element-hq/element-web Docker tag to v1.12.16 2026-04-28 20:58:55 +03:00
renovate[bot] c9e54c73a4 Update dependency prometheus to v3.11.3-0 2026-04-28 07:45:43 +03:00
Slavi Pantaleev 4261d30e64 Auto-enable MAS admin API when Ketesa is enabled
Ketesa needs the MAS admin API exposed to perform MAS-specific
operations (registration tokens, sessions, emails, etc.) when MAS
is in use.

The admin still needs to provision an admin token for Ketesa
manually, but at least the listener resource is now ready by default.

Mirrors the existing Synapse admin API auto-enable pattern.

Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5164
2026-04-27 18:42:18 +03:00
renovate[bot] e155ac3f94 Update ghcr.io/element-hq/element-call Docker tag to v0.19.2 2026-04-27 13:26:22 +03:00
renovate[bot] 2ddbc58ecd Update dependency etherpad to v2.7.2-0 2026-04-26 20:38:20 +03:00
renovate[bot] efd9f216b2 Update ghcr.io/etkecc/postmoogle Docker tag to v0.9.31 2026-04-26 08:10:55 +03:00
renovate[bot] 6b69e321fd Update ghcr.io/etkecc/ketesa Docker tag to v1.2.1 2026-04-26 08:10:22 +03:00
Slavi Pantaleev 2d44a0884b Sync Continuwuity v0.5.8 LDAP StartTLS reference options
Adds the new `use_starttls` and `disable_tls_verification` keys to
the commented-out `[global.ldap]` reference block, matching upstream.
2026-04-25 22:31:40 +03:00
renovate[bot] d48b175a84 Update ghcr.io/etkecc/postmoogle Docker tag to v0.9.30 2026-04-25 22:16:26 +03:00
renovate[bot] 4a506f86e7 Update dependency packaging to v26.2 2026-04-25 22:16:00 +03:00
renovate[bot] ad44ec49c6 Update forgejo.ellis.link/continuwuation/continuwuity Docker tag to v0.5.8 2026-04-25 22:14:56 +03:00
renovate[bot] bfabb0d456 Update dependency etherpad to v2.7.1-0 2026-04-24 10:59:04 +03:00
Slavi Pantaleev 8e2545a100 Upgrade meshtastic-relay (v1.2.8 -> v1.3.5) and adapt for MMRELAY_HOME
v1.3.0 moved the container's runtime paths to a unified MMRELAY_HOME=/data
model (credentials, database, logs, E2EE store, plugins all live under /data).
Legacy /app paths still work until v1.4.

Adapted the role to the new model: drop the three `/app/*` bind mounts and
the `_logs_path` variable, mount `_config_path` read-only at `/config` and
`_data_path` read-write at `/data`, and invoke the container as
`mmrelay --config /config/config.yaml` so the Ansible-managed config stays
separate from runtime data. Also drop the hardcoded `/app/data/...` database
and e2ee store_path overrides from the default config; MMRELAY_HOME defaults
place them under `_data_path/database/` and `_data_path/matrix/store/` on the
host.
2026-04-24 10:54:18 +03:00
luschmar 243b4d0fd9 Add MatrixMeshtasticRelay (#4840)
* Add Matrix <-> Meshtastic bridge (meshtastic-matrix-relay)

Vendors the meshtastic-matrix-relay (mmrelay) role into roles/custom/
following the conventions used by other bridge roles.

Co-authored-by: luschmar <90399580+luschmar@users.noreply.github.com>

* Add docs and CHANGELOG entry for Matrix <-> Meshtastic bridge

Co-authored-by: luschmar <90399580+luschmar@users.noreply.github.com>

---------

Co-authored-by: Slavi Pantaleev <slavi@devture.com>
2026-04-24 10:31:18 +03:00
github-actions[bot] 2949e0931f Automatic translations update 2026-04-24 09:41:19 +03:00
Slavi Pantaleev 675338fc18 Upgrade livekit_server role (v1.11.0-0 -> v1.11.0-1)
Brings in a new `livekit_server_container_http_listen_interface`
variable, which allows publishing LiveKit's HTTP signaling port (7880)
on a host interface. Useful when a reverse-proxy fronting LiveKit runs
outside the container network.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-24 09:36:39 +03:00
D4GU 2361d5ac5d Add missing matrix_client_commet_container_image_force_pull variable (#5008)
The `matrix-client-commet` role's pull task references
`matrix_client_commet_container_image_force_pull`, but the variable
was never defined in defaults. Users setting
`matrix_client_commet_container_image_self_build: false` would hit an
undefined-variable failure.

Define it using the same pattern as other client roles (force-pull on
moving tags), covering both `:latest` and `:main` since Commet's
default version is `main`.
2026-04-24 09:24:03 +03:00
thigg a753a3b295 Add nginx reverse-proxy example for Matrix RTC (#5086)
When fronting the playbook's integrated Traefik reverse-proxy with
another reverse-proxy (e.g. nginx), WebSocket traffic needs to be
forwarded to LiveKit Server at the `/livekit-server/` path for Matrix
RTC calls to work.

Adds a `/livekit-server/` location block to the nginx reverse-proxy
example, a section to the Matrix RTC docs explaining the requirement,
and cross-links between the two.
2026-04-24 09:14:07 +03:00
Matěj Cepl e0bc2be687 Clean up ansible-lint warnings in defaults/main.yml files (#5148)
Reformat `{{ { ... }[engine] }}` dict-in-Jinja-expressions across
bot/bridge role defaults for consistent indentation (tabs -> spaces).
Also: fix a missing space in a Jinja `+` expression in matrix-static-files,
and fix indentation in the caddy2-in-container example.

The original PR also renamed `galaxy/<role>` role references to just
`<role>` in setup.yml and jitsi_jvb.yml; those were dropped here because
Ansible does not recurse into subdirectories of `roles/` by default and
no `roles_path` is configured in ansible.cfg, so the rename would break
role resolution.

Co-Authored-By: Slavi Pantaleev <slavi@devture.com>
2026-04-24 09:01:47 +03:00
Slavi Pantaleev 5b7a1c2a6c Upgrade mautrix-telegram (v0.15.3 -> v0.2604.0) (bridgev2) and adapt configuration
Matches the earlier Python -> Go rewrites of the other mautrix-* bridges.

Related to:
- https://github.com/mautrix/telegram/releases/tag/v0.2604.0
- https://mau.fi/blog/2026-04-mautrix-release/

The bridge is now a Go binary with upstream-handled automatic database and
config migration on first start, so in-place upgrades on Postgres should
Just Work for users on the defaults. The lottieconverter sidecar container
is gone (bundled upstream), and the public web-based login endpoint is
gone (login happens inside Matrix now).

Upstream v0.2604.0 has a known bug in the legacy SQLite migration that
can corrupt data. The role detects legacy Python-bridge SQLite databases
(via the `telethon_sessions` table signature) and refuses to upgrade,
pointing users to switch to Postgres (playbook-managed pgloader migration)
or wait for the next upstream release. The guard is isolated in its own
`validate_config_sqlite_legacy_migration_bug.yml` so it can be deleted
cleanly once upstream fixes the bug.

Removed variables (all caught by the deprecation check in
`validate_config.yml` with actionable rename/removal hints): the entire
`_hostname` / `_path_prefix` / `_scheme` / `_public_endpoint` /
`_appservice_public_*` / `_container_labels_public_endpoint_*` /
`_container_http_host_bind_port` family (web login endpoint is gone);
`_bot_token` (old-style relaybot is gone, use the common bridgev2 relay
mode); `_filter_mode` (dropped upstream); `_bridge_login_shared_secret_map*`
(use Appservice Double Puppet); `_username_template`, `_alias_template`,
`_displayname_template` (templates moved under `network:`, new Go-template
syntax, exposed via `_network_displayname_template`); all
`_lottieconverter_*` variables; `_appservice_database` (renamed to
`_appservice_database_uri`).

Added playbook-time validation that catches legacy permission values
(`relaybot`, `puppeting`, `full`) in the fully-merged config (so overrides
via `matrix_mautrix_telegram_configuration_extension_yaml` are caught too),
with a mapping hint in the error message.

Other notes:

- The legacy sqlite->postgres relocation of `{base_path}/mautrix-telegram.db`
  to `{data_path}/mautrix-telegram.db` now happens BEFORE the pgloader
  migration step, so users who flip to Postgres as part of this upgrade
  get their data imported correctly.
- The Ketesa managed-user regex for the telegram namespace is updated to
  match both regular IDs and the new `channel-<id>` form used by bridgev2.
- `matrix_playbook_migration_expected_version` bumped to v2026.04.24.0,
  with a new breaking-change entry pointing at the CHANGELOG section.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-24 08:45:04 +03:00
Suguru Hirahara ce0c194cd3 Fix ddclient_container_image_registry_prefix_upstream
Closes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5165

Signed-off-by: Suguru Hirahara <did:key:z6MkvVZk1A3KBApWJXv2Ju4H14ErDfRGxh8zxdXSZ4vACDg5>
2026-04-24 11:04:30 +09:00
renovate[bot] 89f197ceb5 chore(deps): update dependency traefik to v3.6.14-0 2026-04-23 11:35:52 +03:00
renovate[bot] bfeb8fdb54 chore(deps): update dependency idna to v3.13 2026-04-23 10:12:09 +03:00
renovate[bot] 849cecc5d0 chore(deps): update dependency click to v8.3.3 2026-04-23 10:12:01 +03:00
renovate[bot] 052e5a6e3e chore(deps): update dependency certifi to v2026.4.22 2026-04-23 10:11:53 +03:00
renovate[bot] 6fac597733 chore(deps): update dependency ntfy to v2.22.0-0 2026-04-22 12:20:58 +03:00
renovate[bot] 5495f5456f chore(deps): update docker.io/metio/matrix-alertmanager-receiver docker tag to v2026.4.22 2026-04-22 12:20:39 +03:00
renovate[bot] 5913a4c7eb chore(deps): update ghcr.io/element-hq/lk-jwt-service docker tag to v0.4.4 2026-04-20 19:58:37 +03:00
Slavi Pantaleev 0a00adc580 Auto-wire Continuwuity SMTP and well-known defaults
Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/5154
2026-04-18 07:49:49 +03:00
Slavi Pantaleev fcd48e7480 Make matrix_continuwuity_systemd_wanted_services_list actually used in matrix-continuwuity.service 2026-04-18 07:46:24 +03:00
Slavi Pantaleev 53c391f420 Split matrix_continuwuity_systemd_wanted_services_list into _default_, _auto and _custom 2026-04-18 07:46:03 +03:00
ezera 0cb1600eda feat(c10y): add support for global.smtp settings
Adds support for SMTP and email-related settings
added in Continuwuity 0.5.7.
2026-04-18 07:22:59 +03:00
renovate[bot] 3890dce67a chore(deps): update dock.mau.dev/mautrix/whatsapp docker tag to v0.2604.0 2026-04-18 07:08:31 +03:00
renovate[bot] f4d03a580b chore(deps): update dependency livekit_server to v1.11.0-0 2026-04-18 07:07:58 +03:00
Sid Manat cf71cb64c4 feat(synapse): support Postgres database keepalive options 2026-04-17 21:50:44 +03:00
renovate[bot] ad0f425b3a chore(deps): update forgejo.ellis.link/continuwuation/continuwuity docker tag to v0.5.7 2026-04-17 21:47:47 +03:00
renovate[bot] 7d3f289582 chore(deps): update dock.mau.dev/mautrix/twitter docker tag to v0.2604.0 2026-04-17 21:46:57 +03:00
renovate[bot] 0a772cc7fb chore(deps): update ghcr.io/element-hq/lk-jwt-service docker tag to v0.4.3 2026-04-17 21:46:42 +03:00
renovate[bot] b1a84c1428 chore(deps): update dock.mau.dev/mautrix/slack docker tag to v0.2604.0 2026-04-17 21:46:21 +03:00
renovate[bot] 5e0a91962a chore(deps): update dock.mau.dev/mautrix/meta docker tag to v0.2604.0 2026-04-17 21:45:11 +03:00
renovate[bot] 43fb63b6bc chore(deps): update dock.mau.dev/mautrix/gmessages docker tag to v0.2604.0 2026-04-17 21:45:02 +03:00
Aine e031c207cf Ketesa v1.2.0 <https://github.com/etkecc/ketesa/releases/tag/v1.2.0> 2026-04-17 08:41:41 +01:00
renovate[bot] eab5c61ca7 chore(deps): update dependency prometheus to v3.11.2-0 2026-04-16 18:32:17 +03:00
renovate[bot] 122004a03a chore(deps): update dependency packaging to v26.1 2026-04-16 18:32:09 +03:00
renovate[bot] 4fea89a690 chore(deps): update astral-sh/setup-uv action to v8 2026-04-16 18:31:58 +03:00
renovate[bot] b48f833ffd chore(deps): update dependency sable to v1.14.0-0 2026-04-16 18:31:42 +03:00
renovate[bot] 83808b391b chore(deps): update ghcr.io/element-hq/element-call docker tag to v0.19.1 2026-04-16 16:41:19 +03:00
QEDeD 642427a6db Slightly clarify Traefik Dashboard instructions
Updated instructions for enabling the Traefik Dashboard, including username and password generation for basic authentication.
2026-04-15 12:09:57 +03:00
renovate[bot] 05f10831cc chore(deps): update docker.io/metio/matrix-alertmanager-receiver docker tag to v2026.4.15 2026-04-15 12:08:58 +03:00
renovate[bot] d369b288d4 chore(deps): update nginx docker tag to v1.30.0 2026-04-15 09:42:32 +03:00
renovate[bot] 1f3f02f0a7 chore(deps): update ghcr.io/etkecc/baibot docker tag to v1.18.0 2026-04-11 13:35:05 +03:00
renovate[bot] 336c564ed4 chore(deps): update peter-evans/create-pull-request action to v8.1.1 2026-04-11 10:50:22 +03:00
renovate[bot] 1806db008a chore(deps): update dependency ntfy to v2.21.0-1 2026-04-09 09:36:37 +03:00
renovate[bot] 8b06a36ac7 chore(deps): update ghcr.io/element-hq/element-web docker tag to v1.12.15 2026-04-08 21:05:55 +03:00
renovate[bot] f8a820212b chore(deps): update dependency etherpad to v2.6.1-6 2026-04-08 19:26:36 +03:00
renovate[bot] 2f4e76c453 chore(deps): update ghcr.io/element-hq/synapse docker tag to v1.151.0 2026-04-08 19:25:19 +03:00
renovate[bot] 610a0154a9 chore(deps): update dependency traefik to v3.6.13-0 2026-04-08 08:10:44 +03:00
renovate[bot] 1213d57d90 chore(deps): update dependency prometheus to v3.11.1-0 2026-04-08 07:15:24 +03:00
renovate[bot] be8fc7e8ba chore(deps): update nginx docker tag to v1.29.8 2026-04-08 07:15:05 +03:00
renovate[bot] deb4da8db5 chore(deps): update ghcr.io/element-hq/matrix-authentication-service docker tag to v1.15.0 2026-04-08 07:12:50 +03:00
Aine 4e0952d11a borg v1.4.4 2026-04-07 19:00:02 +01:00
renovate[bot] 17eb1615de chore(deps): update ghcr.io/element-hq/element-web docker tag to v1.12.14 2026-04-07 19:53:57 +03:00
Aine b309c28204 Borgmatic v2.1.4 2026-04-07 17:12:02 +01:00
Aine aed02ec75f Ketesa v1.1.0 <https://github.com/etkecc/ketesa/releases/tag/v1.1.0> 2026-04-07 17:11:35 +01:00
renovate[bot] 1eba43043b chore(deps): update ghcr.io/element-hq/element-call docker tag to v0.19.0 2026-04-06 15:56:28 +03:00
renovate[bot] 524a5bcc27 chore(deps): update dependency click to v8.3.2 2026-04-05 16:43:54 +03:00
renovate[bot] 359d271259 chore(deps): update extractions/setup-just action to v4 2026-04-05 12:35:06 +03:00
renovate[bot] 707222755f chore(deps): update dependency hydrogen to v0.5.1-3 2026-04-04 21:28:45 +03:00
Aine 9049a82945 Synapse Admin is Ketesa now! (#5113)
* Synapse Admin is Ketesa now!

* i18n changes

* add automatic migration

* fix migration version in vars

* add a note about routing for OIDC Auth

* mention v1.0.0 announcement blog post

* Update docs/container-images.md

Co-authored-by: Suguru Hirahara <luixxiul@users.noreply.github.com>

* Update CHANGELOG.md

Co-authored-by: Suguru Hirahara <luixxiul@users.noreply.github.com>

---------

Co-authored-by: Suguru Hirahara <luixxiul@users.noreply.github.com>
2026-04-03 15:26:18 +01:00
Catalan Lover 3d40026f93 Update c10y default room version to match specification.
The official project rooms are on v12 and support has been stable enough for quite some releases now. Its also just plain old bad security practice to run v11 outside of closed federations.

The upstream docs are simply out of date on this one.
2026-04-03 09:54:00 +03:00
ezera 2429fea517 feat(c10y): allow configuring default room version 2026-04-03 07:39:32 +03:00
renovate[bot] 7a90eab08b chore(deps): update dependency charset-normalizer to v3.4.7 2026-04-02 22:41:40 +03:00
Catalan Lover 09bf24ade8 Update Draupnir from v2.9.0 to v3.0.0 (#5110) 2026-04-02 22:30:13 +03:00
Slavi Pantaleev 0e4a4b0bf8 Update Traefik dashboard auth docs 2026-04-02 22:06:01 +03:00
Slavi Pantaleev c8636ed9f6 Upgrade Traefik (v3.6.12-0 -> v3.6.12-1) 2026-04-02 22:06:01 +03:00
renovate[bot] 2468bc040f chore(deps): update dependency requests to v2.33.1 2026-04-01 23:31:59 +03:00
DrKnees 6c7944494b Update Continuwuity config and add options 2026-04-01 23:26:40 +03:00
renovate[bot] 7a1cf643bc chore(deps): update dependency etherpad to v2.6.1-5 2026-04-01 20:34:50 +03:00
renovate[bot] ae6aa35028 chore(deps): update pre-commit hook ansible/ansible-lint to v26.4.0 2026-04-01 20:34:42 +03:00
renovate[bot] 361939f17d chore(deps): update docker.io/metio/matrix-alertmanager-receiver docker tag to v2026.4.1 2026-04-01 15:41:23 +03:00
renovate[bot] cf0332aa09 chore(deps): update dependency etherpad to v2.6.1-4 2026-04-01 09:01:36 +03:00
renovate[bot] 8145a6e492 chore(deps): update dependency sable to v1.13.1-0 2026-03-31 18:23:40 +03:00
renovate[bot] 3a120f5c25 chore(deps): update ghcr.io/element-hq/lk-jwt-service docker tag to v0.4.2 2026-03-31 18:23:20 +03:00
renovate[bot] 539136dce6 chore(deps): update dependency ntfy to v2.21.0-0 2026-03-31 08:49:16 +03:00
Slavi Pantaleev 94a0a6c6ec fix(mas): keep Synapse stopped after syn2mas migration
Avoid reopening a transition window where Synapse can accept new registrations or other auth changes
after syn2mas completes but before the MAS cutover is finalized.

Inspired by and continuing the work done in: https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/5097
2026-03-31 08:49:03 +03:00
renovate[bot] 060db8f428 chore(deps): update dependency jitsi to v10888 2026-03-31 01:39:18 +03:00
Jean-Benoît Grimaldi e5804c4203 fix(mas): Don't fail if OpenID connect is setup in synapse while upgrading to MAS 2026-03-30 20:54:51 +03:00
renovate[bot] 8a3adae240 chore(deps): update dependency livekit_server to v1.10.1-0 2026-03-30 20:45:44 +03:00
renovate[bot] c897c8f5de chore(deps): update dependency pygments to v2.20.0 2026-03-29 21:05:18 +03:00
anya hope 720a1b1a31 feat(c10y): add url_preview_check_root_domain 2026-03-29 09:59:54 +03:00
anya hope 3f0326855d feat(c10y): add url_preview_domain_explicit_allowlist 2026-03-29 09:59:54 +03:00
renovate[bot] a4bc3facb4 chore(deps): update dependency ntfy to v2.20.1-0 2026-03-28 14:24:46 +02:00
renovate[bot] de6d18834d chore(deps): update joseluisq/static-web-server docker tag to v2.42.0 2026-03-28 14:17:16 +02:00
renovate[bot] 4c336f7e22 chore(deps): update ghcr.io/etkecc/fluffychat-web docker tag to v2.5.1 2026-03-27 18:08:25 +02:00
Slavi Pantaleev 3593c952af Update playbook_help (8630e4f1749bcb659c412820f754473f09055052 -> ea8c5cc750c4e23d004c9a836dfd9eda82d45ff4)
Ref: https://github.com/devture/com.devture.ansible.role.playbook_help/pull/4
2026-03-27 11:37:11 +02:00
renovate[bot] 5480ce8129 chore(deps): update dependency traefik to v3.6.12-0 2026-03-27 11:33:41 +02:00
renovate[bot] d82394188b chore(deps): update dependency ntfy to v2.20.0-0 2026-03-27 11:33:33 +02:00
Slavi Pantaleev 8deaf6dd43 Upgrade exim-relay (v4.99.1-r0-1-0 -> v4.99.1-r0-2-0) 2026-03-27 11:28:25 +02:00
renovate[bot] 0a03679230 chore(deps): update dependency requests to v2.33.0 2026-03-26 01:38:46 +02:00
renovate[bot] 8483683b28 chore(deps): update ghcr.io/etkecc/baibot docker tag to v1.17.0 2026-03-26 01:38:32 +02:00
renovate[bot] e4c62da332 chore(deps): update dependency postgres to v18.3-4 2026-03-25 11:15:07 +02:00
renovate[bot] ae78862f7a chore(deps): update docker.io/metio/matrix-alertmanager-receiver docker tag to v2026.3.25 2026-03-25 10:45:52 +02:00
Slavi Pantaleev 5879959151 Revert livekit_server to v1.9.12-1
This backs out the LiveKit v1.10.0 role bump while we investigate MatrixRTC call failures reported in #5076.
The symptoms appear consistent with livekit/livekit#4384, and the upstream fix in livekit/livekit#4389 has not reached a release yet.
2026-03-25 10:07:32 +02:00
renovate[bot] 3400769336 chore(deps): update nginx docker tag to v1.29.7 2026-03-25 09:40:14 +02:00
renovate[bot] e5dbd51b46 chore(deps): update ghcr.io/element-hq/synapse docker tag to v1.150.0 2026-03-24 23:55:29 +02:00
renovate[bot] 68eeb9e303 chore(deps): update ghcr.io/element-hq/matrix-authentication-service docker tag to v1.14.0 2026-03-24 23:54:32 +02:00
renovate[bot] e39b7f89a7 chore(deps): update dependency livekit_server to v1.10.0-0 2026-03-24 18:36:06 +02:00
renovate[bot] bea22b97fa chore(deps): update ghcr.io/etkecc/baibot docker tag to v1.16.1 2026-03-24 18:35:55 +02:00
renovate[bot] 7c5a729c18 chore(deps): update ghcr.io/element-hq/element-web docker tag to v1.12.13 2026-03-24 15:50:45 +02:00
renovate[bot] 38bdf5b181 chore(deps): update dependency traefik to v3.6.11-3 2026-03-24 15:50:09 +02:00
renovate[bot] ad5d783a3c chore(deps): update dependency exim_relay to v4.99.1-r0-1-0 2026-03-24 00:24:23 +02:00
renovate[bot] 5c80913739 chore(deps): update dependency sable to v1.6.0-3 2026-03-23 21:45:36 +02:00
Slavi Pantaleev df44c8d4b3 Enable MSC4143 for MatrixRTC deployments
Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5066
2026-03-23 21:45:13 +02:00
Slavi Pantaleev 63c4fffe65 Add Synapse support for MSC4143 2026-03-23 21:45:13 +02:00
Slavi Pantaleev 9f109f81ee Add pre-commit check for migration version sync between defaults and examples/vars.yml
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-23 09:10:01 +02:00
Slavi Pantaleev 9a9392d24a Add migration validation system to catch breaking changes early
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-23 09:10:01 +02:00
376 changed files with 26027 additions and 18365 deletions
+3 -3
View File
@@ -32,15 +32,15 @@ jobs:
# Setting up recommended prerequisites
# See: i18n/README.md
- uses: astral-sh/setup-uv@v7
- uses: extractions/setup-just@v3
- uses: astral-sh/setup-uv@v8.1.0
- uses: extractions/setup-just@v4
# TODO: optimize when we start publishing translations and integrate a Weblate instance
- name: Update translation catalog templates (POT) files
run: just --justfile i18n/justfile extract-translation-templates
- name: Create Pull Request
uses: peter-evans/create-pull-request@v8.1.0
uses: peter-evans/create-pull-request@v8.1.1
with:
author: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> # Same as committer
body: This is an automatic pull request to update translation files.
+9 -1
View File
@@ -24,9 +24,17 @@ repos:
hooks:
- id: reuse
- repo: https://github.com/ansible/ansible-lint
rev: v26.3.0
rev: v26.4.0
hooks:
- id: ansible-lint
files: '^roles/custom/'
args: ['roles/custom']
pass_filenames: false
- repo: local
hooks:
- id: check-examples-vars-migration-version
name: Check examples/vars.yml migration version matches expected
entry: bin/check-examples-vars-migration-version.sh
language: script
files: '(examples/vars\.yml|roles/custom/matrix_playbook_migration/defaults/main\.yml)'
pass_filenames: false
+108
View File
@@ -1,3 +1,111 @@
# 2026-05-07
## Tuwunel support
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.
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.
Existing installations do **not** need to be updated. **Synapse is still the default homeserver implementation** installed by the playbook.
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.
**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.
# 2026-04-24
## Support for bridging to Meshtastic via meshtastic-matrix-relay
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).
To learn more, see our [Setting up a Matrix <-> Meshtastic bridge](./docs/configuring-playbook-bridge-meshtastic-relay.md) documentation page.
## (BC Break) mautrix-telegram has been rewritten in Go (bridgev2)
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.).
**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.
⚠️ **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.
Playbook-specific things to know. The playbook will fail loudly if you're affected:
- 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.
- **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`.
- **Shared-Secret-Auth double-puppeting users**: switch to [Appservice Double Puppet](./docs/configuring-playbook-appservice-double-puppet.md); the playbook wires it up automatically.
- **Custom `matrix_mautrix_telegram_bridge_permissions`**: map `relaybot` to `relay`, `puppeting` to `user`, `full` to `user`. Validated at playbook time.
# 2026-04-03
## (BC Break) Synapse Admin (fork by etke.cc) is now Ketesa
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/).
Ketesa is a zero-configuration drop-in replacement for Synapse Admin: no server-side changes required, just update the role variables.
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`.
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.
The playbook will automatically detect leftover `matrix_synapse_admin_*` variables and fail with a helpful message listing what needs to be renamed.
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).
See the [Ketesa documentation](docs/configuring-playbook-ketesa.md) for details.
# 2026-04-02
## (BC Break) Draupnir for all Self Service Provisioning is now disabled by default
💡 If you don't use [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md), then this breaking change does not concern you..
[Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) now ships with `allowSelfServiceProvisioning: false` as default upstream and in this playbook.
This means users can no longer provision Draupnir instances by inviting the appservice bot unless you explicitly opt in.
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.
If you want to enable Self Service Provisioning, add the following to your `vars.yml`:
```yaml
matrix_appservice_draupnir_for_all_configuration_extension_yaml: |
allowSelfServiceProvisioning: true
```
# 2026-03-23
## Migration validation system introduced
Previously, when updating your setup, you had to remember to read the [CHANGELOG](CHANGELOG.md) file or risk breakage.
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).
A new `matrix_playbook_migration_validated_version` variable has been introduced.
**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.
**Existing users** will need to add the following to their `vars.yml` file after reviewing all changelog entries up to now:
```yml
matrix_playbook_migration_validated_version: v2026.03.23.0
```
Going forward, whenever a breaking change is introduced the playbook will:
- bump its expected version value (`matrix_playbook_migration_expected_version`), causing a discrepancy with what you validated (`matrix_playbook_migration_validated_version`)
- fail when you run it with a helpful message listing what changed and linking to the relevant changelog entries
After reviewing and adapting your setup, you simply update the variable to the new version.
If you'd like to live dangerously and skip these checks (not recommended), you can set this once and be done with it:
```yml
matrix_playbook_migration_validated_version: "{{ matrix_playbook_migration_expected_version }}"
```
# 2026-03-19
## Matrix Authentication Service now prefers UNIX sockets for playbook-managed Postgres
+3 -1
View File
@@ -53,6 +53,7 @@ The homeserver is the backbone of your Matrix system. Choose one from the follow
| [Synapse](https://github.com/element-hq/synapse) | ✅ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network | [Link](docs/configuring-playbook-synapse.md) |
| [Conduit](https://conduit.rs) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements | [Link](docs/configuring-playbook-conduit.md) |
| [continuwuity](https://continuwuity.org) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. | [Link](docs/configuring-playbook-continuwuity.md) |
| [Tuwunel](https://matrix-construct.github.io/tuwunel/) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Tuwunel is the official successor to conduwuit. | [Link](docs/configuring-playbook-tuwunel.md) |
| [Dendrite](https://github.com/element-hq/dendrite) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse. | [Link](docs/configuring-playbook-dendrite.md) |
### Clients
@@ -132,6 +133,7 @@ Bridges can be used to connect your Matrix installation with third-party communi
| [matrix-steam-bridge](https://github.com/jasonlaguidice/matrix-steam-bridge) | ❌ | Bridge to [Steam](https://steampowered.com/) | [Link](docs/configuring-playbook-bridge-steam.md) |
| [matrix-wechat](https://github.com/duo/matrix-wechat) | ❌ | Bridge to [WeChat](https://www.wechat.com/) | [Link](docs/configuring-playbook-bridge-wechat.md) |
| [Heisenbridge](https://github.com/hifi/heisenbridge) | ❌ | Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat) | [Link](docs/configuring-playbook-bridge-heisenbridge.md) |
| [meshtastic-matrix-relay](https://github.com/jeremiah-k/meshtastic-matrix-relay) | ❌ | Bridge to [Meshtastic](https://meshtastic.org/) mesh networks | [Link](docs/configuring-playbook-bridge-meshtastic-relay.md) |
| [mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) | ❌ | Bridge to [GroupMe](https://groupme.com/) | [Link](docs/configuring-playbook-bridge-mx-puppet-groupme.md) |
| [mx-puppet-steam](https://codeberg.org/icewind/mx-puppet-steam) | ❌ | Bridge to [Steam](https://steamapp.com/) | [Link](docs/configuring-playbook-bridge-mx-puppet-steam.md) |
| [Postmoogle](https://github.com/etkecc/postmoogle) | ❌ | Email to Matrix bridge | [Link](docs/configuring-playbook-bridge-postmoogle.md) |
@@ -159,7 +161,7 @@ Services that help you in administrating and monitoring your Matrix installation
| ---- | -------- | ----------- | ------------- |
| [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver) | ❌ | Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client | [Link](docs/configuring-playbook-alertmanager-receiver.md) |
| [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) | ❌ | OAuth 2.0 and OpenID Provider server | [Link](docs/configuring-playbook-matrix-authentication-service.md) |
| [synapse-admin](https://github.com/etkecc/synapse-admin) | ❌ | Web UI tool for administrating users and rooms on your Matrix server | [Link](docs/configuring-playbook-synapse-admin.md) |
| [Ketesa](https://github.com/etkecc/ketesa) | ❌ | Fully-featured web UI for administrating your Matrix homeserver — users, rooms, media, sessions, and more | [Link](docs/configuring-playbook-ketesa.md) |
| Metrics and Graphs | ❌ | Consists of the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI, with [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) being available too | [Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-nginx-logs-optional)) |
| [Borg](https://borgbackup.org) | ❌ | Backups | [Link](docs/configuring-playbook-backup-borg.md) |
| [rageshake](https://github.com/matrix-org/rageshake) | ❌ | Bug report server | [Link](docs/configuring-playbook-rageshake.md) |
+35
View File
@@ -0,0 +1,35 @@
#!/bin/bash
# SPDX-FileCopyrightText: 2026 Slavi Pantaleev
#
# SPDX-License-Identifier: AGPL-3.0-or-later
# Ensures that the migration validated version in examples/vars.yml
# matches the expected version in the matrix_playbook_migration role defaults.
set -euo pipefail
defaults_file="roles/custom/matrix_playbook_migration/defaults/main.yml"
examples_file="examples/vars.yml"
expected_version=$(grep -oP '^matrix_playbook_migration_expected_version:\s*"?\K[^"]+' "$defaults_file")
examples_version=$(grep -oP '^matrix_playbook_migration_validated_version:\s*"?\K[^"]+' "$examples_file")
if [ -z "$expected_version" ]; then
echo "ERROR: Could not extract matrix_playbook_migration_expected_version from $defaults_file"
exit 1
fi
if [ -z "$examples_version" ]; then
echo "ERROR: Could not extract matrix_playbook_migration_validated_version from $examples_file"
exit 1
fi
if [ "$expected_version" != "$examples_version" ]; then
echo "ERROR: Migration version mismatch!"
echo " $defaults_file has expected version: $expected_version"
echo " $examples_file has validated version: $examples_version"
echo ""
echo "Please update $examples_file to match."
exit 1
fi
+21
View File
@@ -1,4 +1,25 @@
---
# This file is not used by the playbook's standard CLI installation flow.
# Roles are pulled via `make roles` / `just roles`, which call
# `ansible-galaxy install -r requirements.yml -p roles/galaxy/`.
# Collections are not installed by that command, and the playbook relies
# on whatever `community.*` collections ship with the user's `ansible`
# package (which has been recent enough for years).
#
# This file exists for AWX / Ansible Automation Platform users, which
# auto-detect `collections/requirements.yml` during project sync and
# install the listed collections. See:
# https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/87a2240dc
#
# CLI users do not need to install anything from this file. If you are
# using AWX and a collection version below the floor declared here is
# present, AWX will upgrade it.
collections:
- name: community.general
- name: community.docker
# `community.docker.docker_image_pull` and `community.docker.docker_image_build`
# are used by some roles (e.g. matrix-bot-draupnir,
# matrix-appservice-draupnir-for-all) and are first available in
# community.docker 3.6.0 (Jan 2024 / Ansible 9.2.0).
version: ">=3.6.0"
@@ -1,4 +1,5 @@
<!--
SPDX-FileCopyrightText: 2024 - 2026 Catalan Lover <catalanlover@protonmail.com>
SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara
SPDX-FileCopyrightText: 2024 MDAD project contributors
@@ -13,34 +14,54 @@ Appservice mode can be used together with the regular [Draupnir bot](configuring
## Draupnir Appservice mode compared to Draupnir bot mode
The administrative functions for managing the appservice are alpha quality and very limited. However, the experience of using an appservice-provisioned Draupnir is on par with the experience of using Draupnir from bot mode except in the case of avatar customisation as described later on in this document.
The administrative functions for managing the appservice are alpha quality and very limited. However, the experience of using an appservice-provisioned Draupnir is on par with the experience of using Draupnir from bot mode.
Draupnir for all is the way to go if you need more than 1 Draupnir instance, but you don't need access to Synapse Admin features as they are not accessible through Draupnir for All (Even though the commands do show up in help).
Draupnir for all is the way to go if you need more than 1 Draupnir instance, but you don't need access to Synapse Admin features as they are not accessible through Draupnir for All.
Draupnir for all in the playbook is rate-limit-exempt automatically as its appservice configuration file does not specify any rate limits.
Normal Draupnir does come with the benefit of access to Synapse Admin features. You are also able to more easily customise your normal Draupnir than D4A as D4A even on the branch with the Avatar command (To be Upstreamed to Mainline Draupnir) that command is clunky as it requires the use of things like Element Web devtools. In normal Draupnir this is a quick operation where you login to Draupnir with a normal client and set Avatar and Display name normally.
Normal Draupnir does come with the benefit of access to Synapse Admin features. You are also able to more easily customise your normal Draupnir than D4A as the avatar command is clunky as it requires the use of things like Element Web devtools. In normal Draupnir this can be done while logged in to the Draupnir account with a normal client and set Avatar and Display name normally.
Draupnir for all does not support external tooling like [MRU](https://mru.rory.gay) as it can't access Draupnir's user account.
Draupnir for all only has limited support for external tooling like [MRU](https://mru.rory.gay) as it can't access Draupnir's user account.
## Prerequisites
### Create a main management room
### Prerequisites for Zero Touch Deployment (recommended)
The playbook does not create a management room for your Main Draupnir. You **need to create the room manually** before setting up the bot.
As of Draupnir 3.1.0, Zero Touch Deployment of Draupnir Appservice Mode (Draupnir for all) requires you to supply the following:
- MXID of the first person who gets invited to the admin room that the bot creates for you.
That is all. The appservice manages everything on its own after you provide it with an MXID to invite.
If proceeding with Zero Touch Deployment, skip ahead to [Adjusting the playbook configuration](#adjusting-the-playbook-configuration).
### Create an admin room (optional)
The playbook does not create an admin room for your Draupnir, but the appservice itself can do this for you. Alternatively, you **can create the room manually** before setting up the bot.
Note that the room must be unencrypted.
The management room has to be given an alias, and your bot has to be invited to the room.
The admin room has to be given an alias, and your bot has to be invited to the room.
This management room is used to control who has access to your D4A deployment. The room stores this data inside of the control room state so your bot must have sufficient powerlevel to send custom state events. This is default 50 or moderator as Element clients call this powerlevel.
This admin room is used to control who has access to your D4A deployment. The room stores this data in the control room state, so your bot must have sufficient power level to send custom state events. This is `50` by default (moderator, as Element clients call this power level).
> [!WARNING]
> Anyone in this room can control the bot so it is important that you only invite trusted users to this room.
## Adjusting the playbook configuration
Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ALIAS_HERE`.
When using Zero Touch Deployment, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `INITIAL_MANAGER_MXID_HERE` with the MXID of the user who should be invited to the admin room first.
```yaml
matrix_appservice_draupnir_for_all_enabled: true
matrix_appservice_draupnir_for_all_zero_touch_deploy: true
matrix_appservice_draupnir_for_all_config_initialManager: "INITIAL_MANAGER_MXID_HERE"
```
If opting out of Zero Touch Deployment, use the following configuration block instead. Make sure to replace `MANAGEMENT_ROOM_ALIAS_HERE` with the alias of the admin room you have created earlier.
```yaml
matrix_appservice_draupnir_for_all_enabled: true
@@ -48,6 +69,14 @@ matrix_appservice_draupnir_for_all_enabled: true
matrix_appservice_draupnir_for_all_config_adminRoom: "MANAGEMENT_ROOM_ALIAS_HERE"
```
### Running both bot mode and appservice mode
When running both [bot mode](./configuring-playbook-bot-draupnir.md) and appservice mode, 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.
Conditional restarts work correctly for all tags when running only one of these two operating modes.
### Extending the configuration
There are some additional things you may wish to configure about the component.
@@ -95,20 +124,26 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
## Usage
If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com` you have successfully installed Draupnir for All and can now start using it.
If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com`, you have successfully installed Draupnir for All and can now start using it.
The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot mode.
If using Zero Touch Deployment, the flow is reversed and the success signal is the initial manager account being invited to the admin room.
Draupnir for all installation via this playbook is very much Alpha quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot mode, except that protections requiring homeserver admin access are not available, and the config file is shared between all bots so legacy protections like wordlist share a single global config.
### Granting Users the ability to use D4A
Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recommendation. Using the chat is recommended.
The bot requires a powerlevel of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297))
The bot requires a power level of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297).) This issue is largely mitigated by the Zero Touch Deployment workflows introduced in Draupnir 3.1.0.
To allow users or whole homeservers you type /plain !admin allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially.
To allow users or whole homeservers you type /plain !admin allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to provision a bot. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially.
### How to provision a D4A once you are allowed to
To provision a D4A, you need to start a chat with `@draupnir-main:example.com`. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience.
Once someone is allowed to provision a bot, simply provision them one with `!admin provision MXID`.
Congratulations if you made it all the way here because you now have a fully working Draupnir for all deployment.
Self-service provisioning is disabled as a security measure because it is currently bugged. Force-provisioning (with `!admin provision`) bypasses this disabled status.
Note that you should always make sure there is an allow entry matching whoever is provisioned, because once self-service is fixed, the bot of anyone who is not allowed to provision a bot will refuse to start.
Congratulations if you made it all the way here, because you now have a fully working Draupnir for all deployment.
+1 -1
View File
@@ -414,7 +414,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed.
- If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password. (This note applies to password authentication mode.)
- If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password. (This note applies to password authentication mode.)
## Usage
+1 -1
View File
@@ -89,7 +89,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed.
- If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password.
- If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password.
## Usage
+58 -11
View File
@@ -1,4 +1,5 @@
<!--
SPDX-FileCopyrightText: 2023 - 2026 Catalan Lover <catalanlover@protonmail.com>
SPDX-FileCopyrightText: 2023 - 2025 MDAD project contributors
SPDX-FileCopyrightText: 2023 Kim Brose
SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev
@@ -19,7 +20,17 @@ If your migrating from [Mjolnir](configuring-playbook-bot-mjolnir.md), skip to [
## Prerequisites
### Create a management room
### Prerequisites for Zero Touch Deployment (recommended)
As of Draupnir 3.1.0, Zero Touch Deployment of Draupnir bot mode requires you to supply the following:
- MXID of the first person who gets invited to the management room that the bot creates for you.
- 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).
- A user account for Draupnir.
Zero Touch Deployment is the officially preferred installation method for new deployments of Draupnir as of 3.1.0.
### Create a management room (optional)
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.
@@ -28,6 +39,8 @@ Using your own account, create a new invite only room that you will use to manag
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)).
E2EE support for the management room is mutually exclusive with Zero Touch Deployment of Draupnir.
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`.
## End-to-End Encryption support
@@ -63,7 +76,25 @@ matrix_bot_draupnir_config_accessToken: "CLEAN_ACCESS_TOKEN_HERE"
## Adjusting the playbook configuration
To enable the bot, add the following configuration to your `vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE` with the one of the room which you have created earlier.
### Configuration for Zero Touch Deployment (recommended)
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.
```yaml
# Enable Draupnir
matrix_bot_draupnir_enabled: true
matrix_bot_draupnir_zero_touch_deploy: true
matrix_bot_draupnir_config_initialManager: "INITIAL_MANAGER_MXID_HERE"
# Access token which the bot will use for logging in.
matrix_bot_draupnir_config_accessToken: "CLEAN_ACCESS_TOKEN_HERE"
```
### Configuration without Zero Touch Deployment
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.
```yaml
# Enable Draupnir
@@ -82,7 +113,15 @@ matrix_bot_draupnir_login_native: true
matrix_bot_draupnir_config_managementRoom: "MANAGEMENT_ROOM_ID_HERE"
```
### Create and invite the bot to the management room
### Running both bot mode and appservice mode
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.
Conditional restarts work correctly for all tags when running only one of these two operating modes.
### Create and invite the bot to the management room (only when using native login without Zero Touch Deployment)
Before proceeding to the next step, run the playbook with the following command to create the bot user.
@@ -94,6 +133,12 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
Then, invite the bot (`@bot.draupnir:example.com`) to its management room which you have created earlier.
### Creating a user account for the bot (when using Zero Touch Deployment)
Since Zero Touch Deployment is not validated with native login, you will need to create the user account manually.
Refer to [registering users](registering-users.md) for documentation on how to configure the user account.
### Make sure the account is free from rate limiting (optional, recommended)
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.**
@@ -102,11 +147,11 @@ This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synap
**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).
The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md).
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).
#### Add the configuration
To expose the APIs publicly, add the following configuration to your `vars.yml` file:
This is automatically done if Ketesa is enabled. Otherwise, to expose the APIs publicly, add the following configuration to your `vars.yml` file:
```yaml
matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true
@@ -132,6 +177,7 @@ curl --header "Authorization: Bearer ADMIN_ACCESS_TOKEN_HERE" -X POST https://ma
```
**Notes**:
- This does not work on outdated Windows 10 as curl is not available there.
- Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally.
@@ -157,13 +203,14 @@ matrix_bot_draupnir_config_web_synapseHTTPAntispam_enabled: true
matrix_bot_draupnir_admin_api_enabled: true
```
These protections need to be manually activated and consulting the [enabling protections](#enabling-built-in-protections) guide can be helpful or consulting upstream documentation.
These protections need to be manually activated. Consulting the [enabling protections](#enabling-built-in-protections) guide and/or upstream documentation can be helpful.
<!--
NOTE: this is unsupported by the playbook due to the admin API being inaccessible from containers currently.
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:
The other method polls an Synapse Admin API endpoint, hence it is available only if using Synapse and if the Draupnir user is an admin (see [above](#register-the-bot-account)). To enable it, set `pollReports: true` on `vars.yml` file as below.
-->
```yaml
matrix_bot_draupnir_configuration_extension_yaml: |
pollReports: true
```
### Extending the configuration
@@ -212,7 +259,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed.
- If you change the bot password (`matrix_bot_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_password` to let the bot know its new password.
- 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.
## Usage
+1 -1
View File
@@ -78,7 +78,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed.
- If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password.
- If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password.
## Usage
@@ -71,7 +71,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed.
- If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password.
- If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password.
## Usage
@@ -57,7 +57,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed.
- If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password.
- If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password.
## Usage
+1 -1
View File
@@ -103,7 +103,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed.
- If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password.
- If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password.
## Usage
+2 -2
View File
@@ -46,7 +46,7 @@ This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synap
**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).
The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md).
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).
#### Add the configuration
@@ -198,7 +198,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed.
- If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password.
- 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.
## Usage
@@ -1,5 +1,5 @@
<!--
SPDX-FileCopyrightText: 2018 - 2024 Slavi Pantaleev
SPDX-FileCopyrightText: 2018 - 2026 Slavi Pantaleev
SPDX-FileCopyrightText: 2018 Hugues Morisset
SPDX-FileCopyrightText: 2019 - 2022 MDAD project contributors
SPDX-FileCopyrightText: 2021 Panagiotis Georgiadis
@@ -17,7 +17,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later
The playbook can install and configure [mautrix-telegram](https://github.com/mautrix/telegram) for you.
See the project's [documentation](https://docs.mau.fi/bridges/python/telegram/index.html) to learn what it does and why it might be useful to you.
See the project's [documentation](https://docs.mau.fi/bridges/go/telegram/index.html) to learn what it does and why it might be useful to you.
## Prerequisites
@@ -25,18 +25,12 @@ See the project's [documentation](https://docs.mau.fi/bridges/python/telegram/in
To use the bridge, you'd need to obtain an API key from [https://my.telegram.org/apps](https://my.telegram.org/apps).
### Enable Appservice Double Puppet or Shared Secret Auth (optional)
### Enable Appservice Double Puppet (optional)
If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook.
If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook.
See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting.
**Notes**:
- Double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future.
- If you decided to enable Double Puppeting manually, send `login-matrix` to the bot in order to receive an instruction about how to send an access token to it.
## Adjusting the playbook configuration
To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `YOUR_TELEGRAM_APP_ID` and `YOUR_TELEGRAM_API_HASH`.
@@ -49,37 +43,16 @@ matrix_mautrix_telegram_api_hash: YOUR_TELEGRAM_API_HASH
### Relaying
### Enable relay-bot (optional)
If you want to use the relay-bot feature ([relay bot documentation](https://docs.mau.fi/bridges/python/telegram/relay-bot.html)), which allows anonymous user to chat with telegram users, add the following configuration to your `vars.yml` file:
```yaml
matrix_mautrix_telegram_bot_token: YOUR_TELEGRAM_BOT_TOKEN
matrix_mautrix_telegram_configuration_extension_yaml: |
bridge:
permissions:
'*': relaybot
```
This bridge supports the common [mautrix bridge relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional). Once enabled, any authenticated user can be turned into a relaybot for a chat by sending `!tg set-relay` in that chat.
### Configure a user as an administrator of the bridge (optional)
You might also want to give permissions to a user to administrate the bot. See [this section](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional) on the common guide for details about it.
More details about permissions in this example: https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-config.yaml#L410
### Use the bridge for direct chats only (optional)
If you want to exclude all groups from syncing and use the Telegram-Bridge only for direct chats, add the following configuration to your `vars.yml` file:
```yaml
matrix_mautrix_telegram_filter_mode: whitelist
```
### Extending the configuration
There are some additional things you may wish to configure about the bridge.
<!-- NOTE: common relay mode is not supported for this bridge -->
See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc.
## Installing
@@ -99,9 +72,9 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju
To use the bridge, you need to start a chat with `@telegrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/telegram/authentication.html).
You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/telegram/authentication.html).
After logging in, the bridge will create portal rooms for all of your Telegram groups and invite you to them. Note that the bridge won't automatically create rooms for private chats.
After logging in, the bridge will create portal rooms for all of your Telegram groups and invite you to them.
## Troubleshooting
@@ -109,8 +82,9 @@ As with all other services, you can find the logs in [systemd-journald](https://
### Increase logging verbosity
The default logging level for this component is `WARNING`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:
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:
```yaml
matrix_mautrix_telegram_logging_level: DEBUG
# Valid values: fatal, error, warn, info, debug, trace
matrix_mautrix_telegram_logging_level: debug
```
@@ -0,0 +1,95 @@
<!--
SPDX-FileCopyrightText: 2025 - 2026 luschmar
SPDX-FileCopyrightText: 2026 Slavi Pantaleev
SPDX-License-Identifier: AGPL-3.0-or-later
-->
# Setting up a Matrix <-> Meshtastic bridge (optional)
The playbook can install and configure [meshtastic-matrix-relay](https://github.com/jeremiah-k/meshtastic-matrix-relay) (sometimes referred to as `mmrelay`) for you — a bridge between [Matrix](https://matrix.org/) and [Meshtastic](https://meshtastic.org/) mesh networks.
See the [project's documentation](https://github.com/jeremiah-k/meshtastic-matrix-relay) to learn what it does and why it might be useful to you.
## Prerequisites
You need a Matrix account for the bot. You can either [register the bot account manually](registering-users.md) or let the playbook create it when running `ansible-playbook … --tags=ensure-matrix-users-created`. Either way, you'll need the account's **password** to configure the bridge — unlike most other bridges in this playbook, `mmrelay` authenticates with a password and creates its own session (optionally with End-to-End Encryption material).
You also need access to a Meshtastic device, connected to the server via one of:
- **TCP**: the device is reachable on the network (e.g. a Meshtastic node running the TCP API),
- **Serial**: the device is plugged in via USB and available on the host (e.g. `/dev/ttyUSB0`),
- **BLE**: the device is reachable via Bluetooth Low Energy from the host.
## Adjusting the playbook configuration
To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
```yaml
matrix_meshtastic_relay_enabled: true
# Password for the bot's Matrix account.
# On first startup, the bridge uses this to log in and persist credentials
# (including End-to-End Encryption material) under its data directory.
# After that, the password can be removed from this variable.
matrix_meshtastic_relay_matrix_bot_password: "PASSWORD_FOR_THE_BOT"
# How the bridge connects to your Meshtastic device.
# One of: tcp, serial, ble
matrix_meshtastic_relay_connection_type: tcp
# For connection_type: tcp
matrix_meshtastic_relay_tcp_host: "meshtastic.local"
# For connection_type: serial
# matrix_meshtastic_relay_serial_port: "/dev/ttyUSB0"
# For connection_type: ble
# matrix_meshtastic_relay_ble_address: "AA:BB:CC:DD:EE:FF"
# Matrix rooms to bridge to Meshtastic channels.
matrix_meshtastic_relay_matrix_rooms_list:
- id: "#meshtastic:{{ matrix_domain }}"
meshtastic_channel: "0"
```
By default, the bot's Matrix ID is `@meshtasticbot:{{ matrix_domain }}`. To change it, adjust `matrix_meshtastic_relay_matrix_bot_user_id`.
### Bluetooth (BLE) connections
When `matrix_meshtastic_relay_connection_type` is `ble`, the container runs with `--network=host` and bind-mounts the host's DBus socket — both are required for Bluetooth pairing/communication. Only use this connection type if you trust the playbook-managed host and are comfortable with these privileges.
### Serial connections
When `matrix_meshtastic_relay_connection_type` is `serial`, the host device referenced by `matrix_meshtastic_relay_serial_port` is passed through to the container. Make sure that `matrix_user_uid` / `matrix_user_gid` have read/write access to that device (e.g. by adding the matrix user to the `dialout` group, or adjusting udev rules).
### Extending the configuration
There are some additional things you may wish to configure about the bridge.
Take a look at:
- `roles/custom/matrix-bridge-meshtastic-relay/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override individual `matrix_meshtastic_relay_*` variables, or make finer-grained adjustments via `matrix_meshtastic_relay_configuration_extension_yaml`.
## Installing
After configuring the playbook, run the playbook with [playbook tags](playbook-tags.md) as below:
<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
```sh
ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
```
The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`.
`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too.
## Usage
Invite the bot to the Matrix rooms listed in `matrix_meshtastic_relay_matrix_rooms_list` and it will relay between Matrix and the corresponding Meshtastic channel. Messages sent on Meshtastic will appear in Matrix and vice versa.
See the [project's wiki](https://github.com/jeremiah-k/meshtastic-matrix-relay/wiki) for details about commands, plugins and advanced usage.
## Troubleshooting
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-meshtastic-relay`.
@@ -87,7 +87,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed.
- If you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password.
- If you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password.
## Usage
+6 -2
View File
@@ -1,6 +1,6 @@
<!--
SPDX-FileCopyrightText: 2019 Eduardo Beltrame
SPDX-FileCopyrightText: 2019-2025 Slavi Pantaleev
SPDX-FileCopyrightText: 2019-2026 Slavi Pantaleev
SPDX-FileCopyrightText: 2020 Tulir Asokan
SPDX-FileCopyrightText: 2021, 2024 MDAD project contributors
SPDX-FileCopyrightText: 2022 Dennis Ciba
@@ -29,13 +29,17 @@ To uninstall the service, run the command below on the server:
systemctl disable --now matrix-conduwuit.service
```
## Migrating to Tuwunel
[Tuwunel](configuring-playbook-tuwunel.md) is a fork of conduwuit, [endorsed as conduwuit's successor](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/5200#issuecomment-4396211185) by the former conduwuit maintainer. It reads conduwuit's database directly, so migration is possible. Please refer to [this section](./configuring-playbook-tuwunel.md#migrating-from-conduwuit) for details.
## Migrating to Continuwuity
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.
## Removing data manually
If you are not going to migrate to [Continuwuity](configuring-playbook-continuwuity.md), you can remove data by running the command on the server:
If you are not going to migrate to [Tuwunel](configuring-playbook-tuwunel.md) or [Continuwuity](configuring-playbook-continuwuity.md), you can remove data by running the command on the server:
```sh
rm -rf /matrix/conduwuit
@@ -46,6 +46,13 @@ Take a look at:
There are various Ansible variables that control settings in the `continuwuity.toml` file.
💡 By default, the playbook wires Continuwuity into a few playbook-wide settings:
- if `exim_relay_enabled: true` (the default), Continuwuity SMTP is automatically enabled and pointed at the [local Exim relay](configuring-playbook-email.md) service
- `matrix_continuwuity_config_well_known_client` is automatically set to the public homeserver URL in the usual SSL-enabled setup, which helps email verification and password-reset links work in delegated-domain setups
You can override any of these defaults in your `vars.yml` file if you want Continuwuity to use a different SMTP server or a different well-known client URL.
If a specific setting you'd like to change does not have a dedicated Ansible variable, you can either submit a PR to us to add it, or you can [override the setting using an environment variable](https://continuwuity.org/configuration#environment-variables) using `matrix_continuwuity_environment_variables_extension`. For example:
```yaml
+1 -1
View File
@@ -13,7 +13,7 @@ Element Admin is a web-based administration panel for Synapse and [Matrix Authen
See the project's [documentation](https://github.com/element-hq/element-admin) to learn more.
💡 **Note**: This project is still very young and doesn't have many features. For now, it's recommended to use [Synapse Admin](./configuring-playbook-synapse-admin.md) instead. Deployments that use [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) can use Element Admin for user-management (something that Synapse Admin can't do), while continuing to use Synapse Admin for all other purposes.
💡 **Note**: This project is still very young and doesn't have many features. [Ketesa](./configuring-playbook-ketesa.md) is the fully-featured alternative — it covers all Synapse and MAS Admin APIs, including complete user management, session management, and MAS policy data. Element Admin remains a valid choice if you prefer its interface.
## Prerequisites
+1 -1
View File
@@ -23,7 +23,7 @@ The [Ansible role for exim-relay](https://github.com/mother-of-all-self-hosting/
1. **Final delivery capability**: Can deliver emails directly if you don't have an SMTP server
2. **Centralized configuration**: Configure your upstream SMTP server once in exim-relay, then point all services ([Synapse](configuring-playbook-synapse.md), [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), etc.) thereno need to configure SMTP in each component
2. **Centralized configuration**: Configure your upstream SMTP server once in exim-relay, then point all services ([Synapse](configuring-playbook-synapse.md), [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), [Continuwuity](configuring-playbook-continuwuity.md), etc.) there, with no need to configure SMTP in each component
3. **Local spooling**: Stores messages locally and retries delivery if your upstream SMTP server is temporarily unavailable
+4 -4
View File
@@ -24,14 +24,14 @@ matrix_synapse_federation_domain_whitelist:
If you wish to disable federation, you can do that with an empty list (`[]`), or better yet by completely disabling federation (see below).
## Exposing the room directory over federation
## Controlling exposure of the room directory over federation
By default, your server's public rooms directory is not exposed to other servers via federation.
By default, your server's public rooms directory is exposed to other servers via federation, so that public rooms hosted on your server can be discovered by users on other servers. This goes against the Synapse upstream default (which is `false`); see the [2023-10-23 changelog entry](../CHANGELOG.md#enabling-allow_public_rooms_over_federation-by-default-for-synapse) for the reasoning behind this choice.
To expose it, add the following configuration to your `vars.yml` file:
To prevent your public rooms directory from being exposed over federation (restoring the Synapse upstream default), add the following configuration to your `vars.yml` file:
```yaml
matrix_synapse_allow_public_rooms_over_federation: true
matrix_synapse_allow_public_rooms_over_federation: false
```
## Disabling federation
+100
View File
@@ -0,0 +1,100 @@
<!--
SPDX-FileCopyrightText: 2020-2024 MDAD project contributors
SPDX-FileCopyrightText: 2020-2024 Slavi Pantaleev
SPDX-FileCopyrightText: 2021 Aaron Raimist
SPDX-FileCopyrightText: 2023 Christian González
SPDX-FileCopyrightText: 2024 Nikita Chernyi
SPDX-FileCopyrightText: 2024 Uğur İLTER
SPDX-FileCopyrightText: 2024-2026 Suguru Hirahara
SPDX-FileCopyrightText: 2026 Nikita Chernyi
SPDX-License-Identifier: AGPL-3.0-or-later
-->
# Setting up Ketesa (optional)
The playbook can install and configure [Ketesa](https://github.com/etkecc/ketesa) for you.
Ketesa is a fully-featured admin interface for Matrix homeservers — manage users, rooms, media, sessions, and more from one clean, responsive web UI. It is the evolution of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin): what began as a fork has grown into its own independent project with a redesigned interface, comprehensive Synapse and MAS API coverage, and multi-language support. See the [Ketesa v1.0.0 announcement](https://etke.cc/blog/introducing-ketesa/) for a full overview of what's new.
>[!NOTE]
>
> - Ketesa does not work with other homeserver implementations than Synapse due to API's incompatibility.
> - The latest version of Ketesa is hosted by [etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). If you only need this service occasionally and trust giving your admin credentials to a 3rd party Single Page Application, you can consider using it from there and avoiding the (small) overhead of self-hosting.
> - This playbook also supports an alternative management UI in the shape of [Element Admin](./configuring-playbook-element-admin.md). Please note that it's currently less feature-rich than Ketesa and requires [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md).
## Adjusting DNS records (optional)
By default, this playbook installs Ketesa on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin) — the legacy path is kept for backward compatibility. This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section.
If you wish to adjust it, see the section [below](#adjusting-the-ketesa-url-optional) for details about DNS configuration.
## Adjusting the playbook configuration
To enable Ketesa, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
```yaml
matrix_ketesa_enabled: true
```
**Note**: Ketesa requires Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to function. Access to them is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, for additional security, we normally leave them unexposed, following [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). Because Ketesa needs these APIs to function, when installing Ketesa, the playbook **automatically** exposes the Synapse Admin API publicly for you. Depending on the homeserver implementation you're using (Synapse, Dendrite), this is equivalent to:
- for [Synapse](./configuring-playbook-synapse.md) (our default homeserver implementation): `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true`
- for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true`
By default, Ketesa installation will be [restricted to only work with one homeserver](https://github.com/etkecc/ketesa/blob/main/README.md#restricting-available-homeserver) — the one managed by the playbook. To adjust these restrictions, tweak the `matrix_ketesa_config_restrictBaseUrl` variable.
### Adjusting the Ketesa URL (optional)
By tweaking the `matrix_ketesa_hostname` and `matrix_ketesa_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
We recommend updating the path prefix to `/ketesa` to align with the new branding, while the default `/synapse-admin` is kept for backward compatibility:
```yaml
matrix_ketesa_path_prefix: /ketesa
```
Or to change the hostname entirely:
```yaml
# Change the default hostname and path prefix
matrix_ketesa_hostname: admin.example.com
matrix_ketesa_path_prefix: /
```
If you've changed the default hostname, you may need to create a CNAME record for the Ketesa domain (`admin.example.com`), which targets `matrix.example.com`.
When setting, replace `example.com` with your own.
### Extending the configuration
There are some additional things you may wish to configure about the component.
Take a look at:
- `roles/custom/matrix-ketesa/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_ketesa_configuration_extension_json` variable
## Installing
After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
```sh
ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
```
The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too.
## Usage
After installation, Ketesa will be accessible at: `https://matrix.example.com/synapse-admin/` (or `/ketesa/` if you updated the path prefix as recommended)
To use Ketesa, you need to have [registered at least one administrator account](registering-users.md) on your server.
## Troubleshooting
As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-ketesa`.
If you have questions, you can join this community room and feel free to ask: [#ketesa:etke.cc](https://matrix.to/#/#ketesa:etke.cc)
@@ -51,7 +51,7 @@ This section details what you can expect when switching to the Matrix Authentica
-**Synapse password providers will need to be disabled**. You can no longer use [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc. When the authentication flow is handled by MAS (not by Synapse anymore), it doesn't make sense to extend the Synapse authentication flow with additional modules. Many bridges used to rely on shared-secret-auth for doing double-puppeting (impersonating other users), but most (at least the mautrix bridges) nowadays use [Appservice Double Puppet](./configuring-playbook-appservice-double-puppet.md) as a better alternative. Older/maintained bridges may still rely on shared-secret-auth, as do other services like [matrix-corporal](./configuring-playbook-matrix-corporal.md).
- ❌ Certain **tools like [Synapse Admin](./configuring-playbook-synapse-admin.md) do not have full compatibility with MAS yet**. Synapse Admin already supports OIDC auth, browsing users (which Synapse will internally fetch from MAS) and updating user avatars. However, editing users (passwords, etc.) now needs to happen directly against MAS using the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html), which Synapse Admin cannot interact with yet. You may be interested in using [Element Admin](./configuring-playbook-element-admin.md) for these purposes.
- **[Ketesa](./configuring-playbook-ketesa.md) has full MAS integration**. Ketesa supports OIDC auth, user management, all session types (browser, OAuth2, compatibility), linked email addresses, upstream OAuth provider links, MAS policy data, and user creation through MAS. It is the recommended tool for managing homeservers running MAS.
-**Some services experience issues when authenticating via MAS**:
@@ -398,6 +398,8 @@ To perform a real migration, run the `matrix-authentication-service-mas-cli-syn2
just run-tags matrix-authentication-service-mas-cli-syn2mas
```
After `syn2mas` completes, Synapse will intentionally remain stopped to avoid new registrations or other authentication changes from being accepted before the migration is completed. Continue with the next steps in this guide before re-running the installation.
Having performed a `syn2mas` migration once, trying to do it again will report errors (e.g. "Error: The MAS database is not empty: rows found in at least `users`. Please drop and recreate the database, then try again.").
## Verify that Matrix Authentication Service is installed correctly
+6
View File
@@ -38,6 +38,12 @@ matrix_rtc_enabled: true
In addition to the HTTP/HTTPS ports (which you've already exposed as per the [prerequisites](prerequisites.md) document), you'll also need to open ports required by [LiveKit Server](configuring-playbook-livekit-server.md) as described in its own [Adjusting firewall rules](configuring-playbook-livekit-server.md#adjusting-firewall-rules) section.
## Fronting the integrated reverse-proxy with another reverse-proxy
If you're [fronting the integrated reverse-proxy webserver with another reverse-proxy](configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) (e.g. nginx), it needs to forward WebSocket traffic for [LiveKit Server](configuring-playbook-livekit-server.md) at the `/livekit-server/` path. Without that, Matrix RTC calls will not work.
See [`examples/reverse-proxies/nginx/matrix.conf`](../examples/reverse-proxies/nginx/matrix.conf) for an nginx example.
## Installing
After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records) and [adjusting firewall rules](#adjusting-firewall-rules), run the playbook with [playbook tags](playbook-tags.md) as below:
@@ -1,93 +0,0 @@
<!--
SPDX-FileCopyrightText: 2020-2024 MDAD project contributors
SPDX-FileCopyrightText: 2020-2024 Slavi Pantaleev
SPDX-FileCopyrightText: 2021 Aaron Raimist
SPDX-FileCopyrightText: 2023 Christian González
SPDX-FileCopyrightText: 2024 Nikita Chernyi
SPDX-FileCopyrightText: 2024 Uğur İLTER
SPDX-FileCopyrightText: 2024-2026 Suguru Hirahara
SPDX-License-Identifier: AGPL-3.0-or-later
-->
# Setting up Synapse Admin (optional)
The playbook can install and configure Synapse Admin for you.
Synapse Admin is a web UI tool you can use to **administrate users, rooms, media, etc. on your Matrix homeserver**. This playbook is configured to install [etkecc/synapse-admin](https://github.com/etkecc/synapse-admin), which is a [feature-rich](https://github.com/etkecc/synapse-admin#fork-differences) fork of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin).
>[!NOTE]
>
> - Synapse Admin does not work with other homeserver implementations than Synapse due to API's incompatibility.
> - The latest version of Synapse Admin is hosted by [etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). If you only need this service occasionally and trust giving your admin credentials to a 3rd party Single Page Application, you can consider using it from there and avoiding the (small) overhead of self-hosting.
> - This playbook also supports an alternative management UI in the shape of [Element Admin](./configuring-playbook-element-admin.md). Please note that it's currently less feature-rich than Synapse Admin and requires [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md).
## Adjusting DNS records (optional)
By default, this playbook installs Synapse Admin on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section.
If you wish to adjust it, see the section [below](#adjusting-the-synapse-admin-url-optional) for details about DNS configuration.
## Adjusting the playbook configuration
To enable Synapse Admin, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
```yaml
matrix_synapse_admin_enabled: true
```
**Note**: Synapse Admin requires Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to function. Access to them is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, for additional security, we normally leave them unexposed, following [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). Because Synapse Admin needs these APIs to function, when installing Synapse Admin, the playbook **automatically** exposes the Synapse Admin API publicly for you. Depending on the homeserver implementation you're using (Synapse, Dendrite), this is equivalent to:
- for [Synapse](./configuring-playbook-synapse.md) (our default homeserver implementation): `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true`
- for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true`
By default, synapse-admin installation will be [restricted to only work with one homeserver](https://github.com/etkecc/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) — the one managed by the playbook. To adjust these restrictions, tweak the `matrix_synapse_admin_config_restrictBaseUrl` variable.
### Adjusting the Synapse Admin URL (optional)
By tweaking the `matrix_synapse_admin_hostname` and `matrix_synapse_admin_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
Example additional configuration for your `vars.yml` file:
```yaml
# Change the default hostname and path prefix
matrix_synapse_admin_hostname: admin.example.com
matrix_synapse_admin_path_prefix: /
```
If you've changed the default hostname, you may need to create a CNAME record for the Synapse Admin domain (`admin.example.com`), which targets `matrix.example.com`.
When setting, replace `example.com` with your own.
### Extending the configuration
There are some additional things you may wish to configure about the component.
Take a look at:
- `roles/custom/matrix-synapse-admin/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_synapse_admin_configuration_extension_json` variable
## Installing
After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
```sh
ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
```
The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too.
## Usage
After installation, Synapse Admin will be accessible at: `https://matrix.example.com/synapse-admin/`
To use Synapse Admin, you need to have [registered at least one administrator account](registering-users.md) on your server.
## Troubleshooting
As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-synapse-admin`.
If you have questions, you can join this community room and feel free to ask: [#synapse-admin:etke.cc](https://matrix.to/#/#synapse-admin:etke.cc)
+3 -3
View File
@@ -196,11 +196,11 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju
## Usage
### Synapse Admin
### Ketesa
With [Synapse Admin](configuring-playbook-synapse-admin.md), certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace.
[Ketesa](configuring-playbook-ketesa.md) is a fully-featured web UI for administrating your homeserver — managing users, rooms, media, sessions, and more.
The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md).
The playbook can install and configure Ketesa for you. For details about it, see [this page](configuring-playbook-ketesa.md).
### Monitoring Synapse Metrics with Prometheus and Grafana
+18 -3
View File
@@ -25,16 +25,31 @@ traefik_config_accessLog_enabled: false
### Enable Traefik Dashboard
To enable a Traefik [Dashboard](https://doc.traefik.io/traefik/operations/dashboard/) UI at `https://matrix.example.com/dashboard/` (note the trailing `/`), add the following configuration to your `vars.yml` file:
To enable the Traefik [Dashboard](https://doc.traefik.io/traefik/operations/dashboard/) UI at `https://matrix.example.com/dashboard/` (note the trailing `/`), add the following configuration to your `vars.yml` file:
```yaml
traefik_dashboard_enabled: true
traefik_dashboard_hostname: "{{ matrix_server_fqn_matrix }}"
traefik_dashboard_basicauth_enabled: true
traefik_dashboard_basicauth_user: YOUR_USERNAME_HERE
traefik_dashboard_basicauth_password: YOUR_PASSWORD_HERE
traefik_dashboard_basicauth_htpasswd: "YOUR_USERNAME_HERE:$apr1$..."
```
Choose a username and password for the dashboard, then generate the corresponding `htpasswd` entry with:
```sh
htpasswd -nb YOUR_USERNAME_HERE YOUR_PASSWORD_HERE
```
The command outputs the exact value to use for `traefik_dashboard_basicauth_htpasswd` — your username, a colon, and a hash of your chosen password:
```text
YOUR_USERNAME_HERE:$apr1$...
```
Copy the full output line into `traefik_dashboard_basicauth_htpasswd`. After deploying, log in to the dashboard using the same username and password that you chose earlier.
The role also supports the legacy `traefik_dashboard_basicauth_user` / `traefik_dashboard_basicauth_password` convenience variables, but that path depends on the `passlib` Python library on the Ansible controller, may be affected by passlib/bcrypt compatibility issues, and generates non-deterministic hashes which can lead to unnecessary changes.
> [!WARNING]
> Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts.
+234
View File
@@ -0,0 +1,234 @@
<!--
SPDX-FileCopyrightText: 2026 MDAD project contributors
SPDX-FileCopyrightText: 2026 Jason Volk
SPDX-License-Identifier: AGPL-3.0-or-later
-->
# Configuring Tuwunel (optional)
The playbook can install and configure the [Tuwunel](https://matrix-construct.github.io/tuwunel/) Matrix homeserver for you.
Tuwunel is a featureful homeserver written entirely in Rust, intended as a scalable, low-cost, enterprise-ready alternative to Synapse that fully implements the [Matrix specification](https://spec.matrix.org/latest/) for all but the most niche uses. It is the official successor to [conduwuit](configuring-playbook-conduwuit.md), is now sponsored by the government of Switzerland 🇨🇭 (where it is currently deployed for citizens), and is used by a number of organisations with a vested interest in its continued development. See the project's [documentation](https://matrix-construct.github.io/tuwunel/) for further background.
By default, the playbook installs [Synapse](https://github.com/element-hq/synapse) as it's the only full-featured Matrix server at the moment. If that's okay, you can skip this document.
> [!WARNING]
> - **You can't switch an existing Matrix server's implementation** (e.g. Synapse → Tuwunel). Proceed below only if you're OK with starting over, or you're dealing with a server on a new domain name which hasn't participated in the Matrix federation yet. The one exception is migrating from conduwuit; see [Migrating from conduwuit](#migrating-from-conduwuit).
> - **Homeserver implementations other than Synapse may not be fully functional** with every part of this playbook. Make yourself familiar with the trade-offs before proceeding.
## Adjusting the playbook configuration
To use Tuwunel, set the following on `inventory/host_vars/matrix.example.com/vars.yml`:
```yaml
matrix_homeserver_implementation: tuwunel
# Open the registration endpoint long enough to create your first user.
# After signing up, set this back to false.
matrix_tuwunel_config_allow_registration: true
# A registration token to protect the endpoint from abuse.
# Generate one with `pwgen -s 64 1` or similar.
matrix_tuwunel_config_registration_token: ''
```
The first user account that registers becomes a server admin and is automatically invited to the admin room. See [Creating the first user account](#creating-the-first-user-account) below for the bootstrap procedure.
## Wiring done for you
When `matrix_homeserver_implementation: tuwunel` is set, the playbook automatically integrates Tuwunel with the rest of your stack:
- **Federation.** Toggled by `matrix_homeserver_federation_enabled`. The federation virtual host (port 8448 in the default setup) is wired up via Traefik labels.
- **Well-known.** `matrix_tuwunel_config_well_known_client` is set to your public homeserver URL whenever SSL is enabled. Matrix clients use this for delegated-domain server discovery; identity-provider entries below can also omit their `callback_url`, since Tuwunel derives `<well-known>/_matrix/client/unstable/login/sso/callback/<client_id>` automatically.
- **Element Call / MatrixRTC.** When the [LiveKit JWT service](configuring-playbook-matrix-rtc.md) is enabled, Tuwunel publishes its public URL through `.well-known/matrix/client` per [MSC4143](https://github.com/matrix-org/matrix-spec-proposals/pull/4143).
- **Legacy calls (TURN).** When [Coturn](configuring-playbook-turn.md) is enabled, its URIs and shared secret (or username/password, depending on `coturn_authentication_method`) are wired automatically.
## Extending the configuration
Tuwunel exposes a large configuration surface. The role surfaces commonly used options as Ansible variables under `matrix_tuwunel_config_*`. See [`roles/custom/matrix-tuwunel/defaults/main.yml`](../roles/custom/matrix-tuwunel/defaults/main.yml) for the complete list, and [`roles/custom/matrix-tuwunel/templates/tuwunel.toml.j2`](../roles/custom/matrix-tuwunel/templates/tuwunel.toml.j2) for the rendered configuration.
For options that aren't surfaced as a dedicated variable, [environment variables](https://matrix-construct.github.io/tuwunel/configuration.html#environment-variables) are the recommended override mechanism. They take priority over the rendered TOML, are scoped to the running container, and require no template patching:
```yaml
matrix_tuwunel_environment_variables_extension: |
TUWUNEL_REQUEST_TIMEOUT=60
TUWUNEL_DNS_CACHE_SIZE=131072
```
Keys nested under a TOML section use `__` (double underscore) to descend, e.g. `TUWUNEL_WELL_KNOWN__SERVER`. User-named sections become path segments too: `TUWUNEL_STORAGE_PROVIDER__ARCHIVE__S3__URL` overrides the `url` field of the `archive` storage provider in the example below.
If you need wholesale control of the configuration file, copy [`roles/custom/matrix-tuwunel/templates/tuwunel.toml.j2`](../roles/custom/matrix-tuwunel/templates/tuwunel.toml.j2) into your inventory and point `matrix_tuwunel_template_tuwunel_config` at your copy.
The container image published as `:latest` is built with `io_uring`, `jemalloc`, LDAP, blurhashing, URL preview, sentry telemetry, and zstd compression all enabled, so most opt-in features are simply a configuration toggle away.
### Identity providers (OAuth2 / OIDC)
Configure one or more `[[global.identity_provider]]` entries via a list. Each entry maps directly to Tuwunel's [identity-provider fields](https://matrix-construct.github.io/tuwunel/authentication/providers.html); only the fields you set are emitted. GitHub, GitLab, and Google have built-in `issuer_url` defaults so a `client_id` plus `client_secret` is enough; for any other `brand` (Apple, Facebook, Keycloak, MAS, Twitter, etc.) you must supply `issuer_url` explicitly:
```yaml
matrix_tuwunel_config_identity_providers:
- brand: keycloak
client_id: matrix
client_secret: '<provider secret>'
issuer_url: https://sso.example.com/realms/matrix
callback_url: https://matrix.example.com/_matrix/client/unstable/login/sso/callback/matrix
trusted: true
- brand: github
client_id: '<github oauth app id>'
client_secret: '<github oauth app secret>'
```
Self-hosted providers must supply both `client_id` and `issuer_url`. Set `trusted: true` only on providers you operate yourself; trusting a public provider (GitHub, Google, etc.) is an account-takeover risk.
### LDAP
Tuwunel can authenticate `m.login.password` requests against an LDAP directory and, in search-then-bind mode, keep admin status in sync with directory membership. The shipped image already includes the `ldap` build feature.
```yaml
matrix_tuwunel_config_ldap_enabled: true
matrix_tuwunel_config_ldap_uri: ldaps://ldap.example.com:636
matrix_tuwunel_config_ldap_base_dn: ou=users,dc=example,dc=org
matrix_tuwunel_config_ldap_bind_dn: cn=ldap-reader,dc=example,dc=org
matrix_tuwunel_config_ldap_bind_password_file: /etc/tuwunel/ldap.pw
matrix_tuwunel_config_ldap_filter: '(&(objectClass=person)(memberOf=cn=matrix,ou=groups,dc=example,dc=org))'
```
> [!NOTE]
> `bind_password_file` is read **inside the container**. The role bind-mounts `/matrix/tuwunel/config` to `/etc/tuwunel` (read-only) and `/matrix/tuwunel/data` to `/var/lib/tuwunel`. To make the file available at the path above, drop it on the host at `/matrix/tuwunel/config/ldap.pw` (owned by `matrix:matrix`) before running the playbook; the role does not template secret files for you.
For direct-bind, anonymous-search, and admin-sync details, see [LDAP authentication](https://matrix-construct.github.io/tuwunel/authentication/ldap.html).
### JWT login
Tuwunel can accept signed JSON Web Tokens both as a login flow and as a User-Interactive Authentication step:
```yaml
matrix_tuwunel_config_jwt_enabled: true
matrix_tuwunel_config_jwt_key: '<shared secret>'
matrix_tuwunel_config_jwt_format: HMAC # one of HMAC, B64HMAC, ECDSA, EDDSA
matrix_tuwunel_config_jwt_algorithm: HS256
matrix_tuwunel_config_jwt_audience: ['matrix']
matrix_tuwunel_config_jwt_issuer: ['https://issuer.example.com']
```
The defaults match Synapse's `experimental_features.jwt_config` semantics, so a key + algorithm port should authenticate the same set of tokens. See [Enterprise JWT](https://matrix-construct.github.io/tuwunel/authentication/jwt.html) for the full reference, including the asymmetric (ECDSA / EdDSA) formats and the operator-controlled UIAA override flow.
### Media storage providers
Each entry becomes a `[global.storage_provider.<id>.<kind>]` block. `kind` is `local` or `s3`; the remaining keys map directly to the fields documented in [Storage providers](https://matrix-construct.github.io/tuwunel/media/storage.html):
```yaml
matrix_tuwunel_config_storage_providers:
- id: primary
kind: local
base_path: /var/lib/tuwunel/media
- id: archive
kind: s3
url: s3://my-bucket/media
region: us-east-1
key: AKIA...
secret: '<aws secret>'
multipart_threshold: 100 MiB
```
The S3 backend ships with native multipart upload, so no goofys/rclone sidecar is required. MinIO, Cloudflare R2, and DigitalOcean Spaces all work; set `endpoint` and `use_vhost_request: false` as appropriate.
> [!NOTE]
> Local provider paths must live under `/var/lib/tuwunel` (the container's data mount, persisted on the host at `/matrix/tuwunel/data`), or you must mount the target directory into the container yourself via `matrix_tuwunel_container_extra_arguments`. The container otherwise runs read-only.
### RocksDB and cache tuning
Tuwunel embeds RocksDB. The defaults (`rocksdb_compression_algo: zstd`) suit most deployments. For high-throughput servers you may want to enable direct I/O, raise parallelism, and bump the cache modifier:
```yaml
matrix_tuwunel_config_rocksdb_direct_io: true
matrix_tuwunel_config_rocksdb_parallelism_threads: 8
matrix_tuwunel_config_cache_capacity_modifier: 2.0
matrix_tuwunel_config_database_backup_path: /var/lib/tuwunel/backups
```
If you run on ZFS, the [Tuwunel maintenance guide](https://matrix-construct.github.io/tuwunel/maintenance.html#zfs) lists the dataset properties (`recordsize`, `primarycache`, `compression`, `atime`, `logbias`) and config flags (`rocksdb_direct_io`, `rocksdb_allow_fallocate`) you need to adjust to avoid severe write amplification.
To enable Sentry crash reporting, set `matrix_tuwunel_config_sentry_enabled: true`.
### Federation gating
Tuwunel accepts regular-expression patterns at every level of remote-server filtering:
```yaml
matrix_tuwunel_config_forbidden_remote_server_names:
- 'bad\.example\.com$'
matrix_tuwunel_config_forbidden_remote_room_directory_server_names:
- 'spam\.example\.com$'
matrix_tuwunel_config_prevent_media_downloads_from:
- 'heavy\.example\.com$'
```
Tuwunel additionally implements [MSC4284 policy servers](https://github.com/matrix-org/matrix-spec-proposals/pull/4284) for room-level federation gating; that lives in room state and needs no playbook configuration.
### Default room version
The role sets `default_room_version: '12'`, so newly created rooms default to Matrix [room version 12](https://github.com/matrix-org/matrix-spec-proposals/pull/4289) ("Hydra"). Override `matrix_tuwunel_config_default_room_version` if you need an earlier version for client compatibility.
## Creating the first user account
Unlike Synapse and Dendrite, Tuwunel does not register users from the command line or via the playbook. On first startup it logs a one-time-use registration token to its journal:
```sh
# Adjust the duration if necessary or remove the --since argument.
journalctl -u matrix-tuwunel.service --since="10 minutes ago"
```
Use the token to create your first account from any client that supports token-gated registration (e.g. [Element Web](configuring-playbook-client-element-web.md)). The account is auto-promoted to admin and invited to the admin room together with the `@conduit:<server_name>` server bot. The bot keeps the legacy `conduit` localpart due to the project's lineage from Conduit.
## Configuring bridges and appservices
The playbook does not auto-register appservices for Tuwunel. After your bridge has produced its `registration.yaml` (e.g. `/matrix/mautrix-signal/bridge/registration.yaml`), register it manually by sending the contents to the admin room, prefixed with `!admin appservices register` and wrapped in a fenced code block:
!admin appservices register
```
id: signal
url: http://matrix-mautrix-signal:29328
as_token: <token>
hs_token: <token>
sender_localpart: _bot_signalbot
rate_limited: false
namespaces:
users:
- exclusive: true
regex: '^@signal_.+:example\.org$'
- exclusive: true
regex: '^@signalbot:example\.org$'
aliases:
- exclusive: true
regex: '^#signal_.+:example\.org$'
```
Registrations stored this way are persisted in the database and survive restarts. Re-running the command with the same `id` replaces the existing entry. See [Application services](https://matrix-construct.github.io/tuwunel/appservices.html) for the full reference and admin commands.
## Migrating from conduwuit
Tuwunel is a "binary swap" for conduwuit; it reads conduwuit's RocksDB layout directly, so migration is a data move, not an export/import.
1. Set `matrix_homeserver_implementation: tuwunel` on `vars.yml` and remove any `matrix_conduwuit_*` overrides.
2. Run a full installation so that the new service is created and the old one removed (e.g. `just setup-all`).
3. Run `just run-tags tuwunel-migrate-from-conduwuit`.
The migration stops `matrix-conduwuit.service`, copies `/matrix/conduwuit` into `/matrix/tuwunel`, renames the config file, and starts `matrix-tuwunel.service`. The freshly generated tuwunel data directory is preserved alongside as `/matrix/tuwunel_old` until you remove it manually.
> [!CAUTION]
> Migrating from any other Conduit derivative (Conduit itself, Continuwuity, or any other fork) is **not supported** and will corrupt your database. All Conduit forks share the same linear database version with no awareness of each other; switching between them produces unrecoverable damage. See the [upstream migration table](https://matrix-construct.github.io/tuwunel/#migrating-to-tuwunel).
## Troubleshooting
As with all other services, the logs are available via [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html):
```sh
journalctl -fu matrix-tuwunel
```
Logging verbosity is controlled by `matrix_tuwunel_config_log` in [`tracing-subscriber` env-filter syntax](https://docs.rs/tracing-subscriber/latest/tracing_subscriber/filter/struct.EnvFilter.html). The default (`info,state_res=warn`) is reasonable for production; for debugging, try `debug` or scope it tighter, e.g. `info,tuwunel_service::sending=debug`.
For RocksDB-level issues, online backups, and offline backup procedures, see the [Tuwunel maintenance guide](https://matrix-construct.github.io/tuwunel/maintenance.html). For protocol-compliance state across MSCs, the spec, and Complement, the project's [compliance dashboard](https://matrix-construct.github.io/tuwunel/development/compliance.html) is the authoritative tracker.
+5 -1
View File
@@ -53,6 +53,8 @@ For a more custom setup, see the [Other configuration options](#other-configurat
- [Configuring continuwuity](configuring-playbook-continuwuity.md), if you've switched to the [continuwuity](https://continuwuity.org) homeserver implementation
- [Configuring Tuwunel](configuring-playbook-tuwunel.md), if you've switched to the [Tuwunel](https://matrix-construct.github.io/tuwunel/) homeserver implementation
- [Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation
- Server components:
@@ -102,7 +104,7 @@ Extend and modify how users are authenticated on your homeserver.
- [Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)
- [Setting up Synapse Admin](configuring-playbook-synapse-admin.md)
- [Setting up Ketesa](configuring-playbook-ketesa.md)
- [Setting up matrix-registration](configuring-playbook-matrix-registration.md)
@@ -182,6 +184,8 @@ Bridges can be used to connect your Matrix installation with third-party communi
- [Setting up Heisenbridge bouncer-style IRC bridging](configuring-playbook-bridge-heisenbridge.md)
- [Setting up a Matrix <-> Meshtastic bridge](configuring-playbook-bridge-meshtastic-relay.md)
- [Setting up WeChat bridging](configuring-playbook-bridge-wechat.md)
### Bots
+2 -1
View File
@@ -28,6 +28,7 @@ We try to stick to official images (provided by their respective projects) as mu
| [Synapse](configuring-playbook-synapse.md) | [element-hq/synapse](https://ghcr.io/element-hq/synapse) | ✅ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network |
| [Conduit](configuring-playbook-conduit.md) | [matrixconduit/matrix-conduit](https://hub.docker.com/r/matrixconduit/matrix-conduit) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements |
| [continuwuity](configuring-playbook-continuwuity.md) | [continuwuation/continuwuity](https://forgejo.ellis.link/continuwuation/continuwuity) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. continuwuity is a continuation of conduwuit. |
| [Tuwunel](configuring-playbook-tuwunel.md) | [matrix-construct/tuwunel](https://ghcr.io/matrix-construct/tuwunel) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Tuwunel is the official successor to conduwuit. |
| [Dendrite](configuring-playbook-dendrite.md) | [matrixdotorg/dendrite-monolith](https://hub.docker.com/r/matrixdotorg/dendrite-monolith/) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse. |
## Clients
@@ -134,7 +135,7 @@ Services that help you in administrating and monitoring your Matrix installation
| ------- | --------------- | -------- | ----------- |
| [matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md) | [metio/matrix-alertmanager-receiver](https://hub.docker.com/r/metio/matrix-alertmanager-receiver) | ❌ | Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client |
| [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) | [element-hq/matrix-authentication-service](https://ghcr.io/element-hq/matrix-authentication-service) | ❌ | OAuth 2.0 and OpenID Provider server |
| [synapse-admin](configuring-playbook-synapse-admin.md) | [etke.cc/synapse-admin](https://ghcr.io/etkecc/synapse-admin) | ❌ | Web UI tool for administrating users and rooms on your Matrix server |
| [Ketesa](configuring-playbook-ketesa.md) | [etkecc/ketesa](https://ghcr.io/etkecc/ketesa) | ❌ | Fully-featured web UI for administrating your Matrix homeserver — users, rooms, media, sessions, and more |
| [Metrics and Graphs](configuring-playbook-prometheus-grafana.md) | [prom/prometheus](https://hub.docker.com/r/prom/prometheus/) | ❌ | [Prometheus](https://prometheus.io) time-series database server |
| [Metrics and Graphs](configuring-playbook-prometheus-grafana.md) | [prom/node-exporter](https://hub.docker.com/r/prom/node-exporter/) | ❌ | Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter |
| [Metrics and Graphs](configuring-playbook-prometheus-grafana.md) | [grafana/grafana](https://hub.docker.com/r/grafana/grafana/) | ❌ | Graphing tool that works well with the above two images. Our playbook also adds two dashboards for [Synapse](https://github.com/element-hq/synapse/tree/master/contrib/grafana) and [Node Exporter](https://github.com/rfrail3/grafana-dashboards) |
+1 -1
View File
@@ -26,7 +26,7 @@ The up-to-date list can be accessed on [traefik's documentation](https://doc.tra
**Note**: the changes below instruct you how to do this for a basic Synapse installation. You will need to adapt the variable name and the content of the labels:
- if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md), [continuwuity](./configuring-playbook-continuwuity.md) or [Dendrite](./configuring-playbook-dendrite.md))
- if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md), [continuwuity](./configuring-playbook-continuwuity.md), [Tuwunel](./configuring-playbook-tuwunel.md) or [Dendrite](./configuring-playbook-dendrite.md))
- if you're using [Synapse with workers enabled](./configuring-playbook-synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled: true`). In that case, it's actually the `matrix-synapse-reverse-proxy-companion` service which has Traefik labels attached
Also, all instructions below are from an older version of the playbook and may not work anymore.
+1 -1
View File
@@ -27,7 +27,7 @@ To update your playbook directory and all upstream Ansible roles (defined in the
- either: `just update`
- or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)
If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`
If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly after updating the playbook: `git pull; rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`
For details about `just` commands, take a look at: [Running `just` commands](just.md).
+16 -4
View File
@@ -1,10 +1,10 @@
<!--
SPDX-FileCopyrightText: 2018 - 2023 Slavi Pantaleev
SPDX-FileCopyrightText: 2018 Aaron Raimist
SPDX-FileCopyrightText: 2018-2026 Slavi Pantaleev
SPDX-FileCopyrightText: 2024 Felix Stupp
SPDX-FileCopyrightText: 2024 MDAD project contributors
SPDX-FileCopyrightText: 2024 Nikita Chernyi
SPDX-FileCopyrightText: 2024 Suguru Hirahara
SPDX-FileCopyrightText: 2024-2026 Suguru Hirahara
SPDX-License-Identifier: AGPL-3.0-or-later
-->
@@ -36,13 +36,25 @@ If it looks good to you, go to the `matrix-docker-ansible-deploy` directory, upd
- either: `just update`
- or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)
If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`
If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly after updating the playbook: `git pull; rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`
**Note**: for details about `just` commands, take a look at: [Running `just` commands](just.md).
### Acknowledge breaking changes if any
The playbook uses a migration validation system that ensures you are aware of breaking changes before they'll affect your deployment. If there is one, you are required to acknowledge each breaking change.
Whenever a breaking change is introduced, the playbook will:
- bump its expected version value (`matrix_playbook_migration_expected_version`), causing a discrepancy with what you validated (`matrix_playbook_migration_validated_version`)
- fail when you run it with a helpful message listing what changed and linking to the relevant changelog entries
After reviewing and adapting your setup, update the variable to the new version.
### Re-run the playbook setup
After updating the Ansible roles, then re-run the [playbook setup](installing.md#maintaining-your-setup-in-the-future) and restart all services:
After updating the Ansible roles and the variable for the validation system when necessary, re-run the [playbook setup](installing.md#maintaining-your-setup-in-the-future) and restart all services:
```sh
ansible-playbook -i inventory/hosts setup.yml --tags=install-all,start
+1 -1
View File
@@ -119,7 +119,7 @@ To update your playbook directory and all upstream Ansible roles, run:
- either: `just update`
- or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)
If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`
If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly after updating the playbook: `git pull; rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`
### Run installation command
+1 -4
View File
@@ -95,10 +95,7 @@ This `register-user` script actually invokes the `mas-cli manage register-user`
## Managing users via a Web UI
To manage users more easily (via a web user-interace), you can install [Synapse Admin](configuring-playbook-synapse-admin.md).
> [!WARNING]
> If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information.
To manage users and your homeserver more easily (via a web interface), you can install [Ketesa](configuring-playbook-ketesa.md) — a fully-featured admin UI covering users, rooms, media, sessions, and MAS management.
## Letting certain users register on your private server
+1 -1
View File
@@ -26,7 +26,7 @@ Note that **not all components support self-building yet**.
Possibly outdated list of roles where self-building the Docker image is currently possible:
- `matrix-synapse`
- `matrix-synapse-admin`
- `matrix-ketesa`
- `matrix-client-element`
- `hydrogen`
- `cinny`
@@ -19,7 +19,7 @@ services:
volumes:
- ./Caddyfile:/etc/caddy/Caddyfile
# - ./site:/var/www
# Other configurations …
# Other configurations …
networks:
# add this as well
@@ -22,6 +22,27 @@ server {
# if you use e.g. Etherpad on etherpad.example.com, add etherpad.example.com to the server_name list
server_name example.com matrix.example.com element.example.com;
# Required for Matrix RTC (WebSocket proxying to LiveKit Server).
# See: ../../../docs/configuring-playbook-matrix-rtc.md#fronting-the-integrated-reverse-proxy-with-another-reverse-proxy
location /livekit-server/ {
proxy_pass http://localhost:81/livekit-server/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
# Long timeouts for persistent WebSocket connections
proxy_read_timeout 86400s;
proxy_send_timeout 86400s;
proxy_buffering off;
access_log /var/log/nginx/matrix.access.log;
error_log /var/log/nginx/matrix.error.log;
}
location / {
# note: do not add a path (even a single /) after the port in `proxy_pass`,
# otherwise, nginx will canonicalise the URI and cause signature verification
+5
View File
@@ -1,4 +1,9 @@
---
# This variable acknowledges that you've reviewed breaking changes up to this version.
# The playbook will fail if this is outdated, guiding you through what changed.
# See the changelog: https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/CHANGELOG.md
matrix_playbook_migration_validated_version: v2026.04.24.0
# The bare domain name which represents your Matrix identity.
# Matrix user IDs for your server will be of the form (`@alice:example.com`).
#
+156 -46
View File
@@ -429,6 +429,13 @@ devture_systemd_service_manager_services_list_auto: |
'groups': ['matrix', 'bridges', 'hookshot', 'bridge-hookshot'],
}] if matrix_hookshot_enabled else [])
+
([{
'name': 'matrix-meshtastic-relay.service',
'priority': 2000,
'restart_necessary': (matrix_meshtastic_relay_restart_necessary | bool),
'groups': ['matrix', 'bridges', 'meshtastic-relay'],
}] if matrix_meshtastic_relay_enabled else [])
+
([{
'name': 'matrix-mautrix-bluesky.service',
'priority': 2000,
@@ -624,6 +631,7 @@ devture_systemd_service_manager_services_list_auto: |
'restart_necessary': (
(matrix_conduit_restart_necessary | bool) if matrix_homeserver_implementation == 'conduit'
else (matrix_continuwuity_restart_necessary | bool) if matrix_homeserver_implementation == 'continuwuity'
else (matrix_tuwunel_restart_necessary | bool) if matrix_homeserver_implementation == 'tuwunel'
else (matrix_dendrite_restart_necessary | bool) if matrix_homeserver_implementation == 'dendrite'
else true
),
@@ -862,11 +870,11 @@ devture_systemd_service_manager_services_list_auto: |
}] if matrix_synapse_auto_compressor_enabled else [])
+
([{
'name': 'matrix-synapse-admin.service',
'name': 'matrix-ketesa.service',
'priority': 4000,
'restart_necessary': (matrix_synapse_admin_restart_necessary | bool),
'groups': ['matrix', 'synapse-admin'],
}] if matrix_synapse_admin_enabled else [])
'restart_necessary': (matrix_ketesa_restart_necessary | bool),
'groups': ['matrix', 'ketesa'],
}] if matrix_ketesa_enabled else [])
+
([{
'name': (matrix_synapse_usage_exporter_identifier + '.service'),
@@ -1001,6 +1009,7 @@ matrix_homeserver_container_client_api_endpoint: |-
'dendrite': ('matrix-dendrite:' + matrix_dendrite_http_bind_port | default('8008') | string),
'conduit': ('matrix-conduit:' + matrix_conduit_port_number | default('8008') | string),
'continuwuity': ('matrix-continuwuity:' + matrix_continuwuity_config_port_number | default('8008') | string),
'tuwunel': ('matrix-tuwunel:' + matrix_tuwunel_config_port_number | default('8008') | string),
}[matrix_homeserver_implementation]
}}
@@ -1011,6 +1020,7 @@ matrix_homeserver_container_federation_api_endpoint: |-
'dendrite': ('matrix-dendrite:' + matrix_dendrite_http_bind_port | default('8008') | string),
'conduit': ('matrix-conduit:' + matrix_conduit_port_number | default('8008') | string),
'continuwuity': ('matrix-continuwuity:' + matrix_continuwuity_config_port_number | default('8008') | string),
'tuwunel': ('matrix-tuwunel:' + matrix_tuwunel_config_port_number | default('8008') | string),
}[matrix_homeserver_implementation]
}}
@@ -1117,7 +1127,7 @@ matrix_authentication_service_config_email_port: "{{ 8025 if exim_relay_enabled
matrix_authentication_service_config_email_mode: "{{ 'plain' if exim_relay_enabled else 'starttls' }}"
matrix_authentication_service_config_email_from_address: "{{ exim_relay_sender_address }}"
matrix_authentication_service_admin_api_enabled: "{{ matrix_element_admin_enabled }}"
matrix_authentication_service_admin_api_enabled: "{{ matrix_element_admin_enabled or matrix_ketesa_enabled }}"
matrix_authentication_service_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_authentication_service_container_image_registry_prefix_upstream_default }}"
@@ -1936,9 +1946,6 @@ matrix_mautrix_meta_instagram_database_password: "{{ ((matrix_homeserver_generic
# We don't enable bridges by default.
matrix_mautrix_telegram_enabled: false
matrix_mautrix_telegram_hostname: "{{ matrix_server_fqn_matrix }}"
matrix_mautrix_telegram_path_prefix: "/{{ (matrix_homeserver_generic_secret_key + ':telegram') | hash('sha512') | to_uuid }}"
matrix_mautrix_telegram_systemd_required_services_list_auto: |
{{
matrix_addons_homeserver_systemd_services_list
@@ -1946,16 +1953,9 @@ matrix_mautrix_telegram_systemd_required_services_list_auto: |
([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mautrix_telegram_database_hostname == postgres_connection_hostname) else [])
}}
matrix_mautrix_telegram_lottieconverter_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_telegram_lottieconverter_container_image_registry_prefix_upstream_default }}"
matrix_mautrix_telegram_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_telegram_container_image_registry_prefix_upstream_default }}"
# Images are multi-arch (amd64 and arm64, but not arm32).
matrix_mautrix_telegram_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}"
matrix_mautrix_telegram_lottieconverter_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}"
matrix_mautrix_telegram_lottieconverter_container_image_self_build_mask_arch: "{{ matrix_architecture != 'amd64' }}"
matrix_mautrix_telegram_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '9006') if matrix_playbook_service_host_bind_interface_prefix else '' }}"
matrix_mautrix_telegram_container_network: "{{ matrix_addons_container_network }}"
@@ -1986,17 +1986,15 @@ matrix_mautrix_telegram_homeserver_token: "{{ (matrix_homeserver_generic_secret_
matrix_mautrix_telegram_homeserver_async_media: "{{ matrix_homeserver_implementation in ['synapse'] }}"
matrix_mautrix_telegram_bridge_login_shared_secret_map_auto: |-
matrix_mautrix_telegram_provisioning_shared_secret: "{{ (matrix_homeserver_generic_secret_key + ':mau.telegram.prov') | hash('sha512') | to_uuid }}"
matrix_mautrix_telegram_double_puppet_secrets_auto: |-
{{
({
{
matrix_mautrix_telegram_homeserver_domain: ("as_token:" + matrix_appservice_double_puppet_registration_as_token)
})
}
if matrix_appservice_double_puppet_enabled
else (
{matrix_mautrix_telegram_homeserver_domain: matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret}
if matrix_synapse_ext_password_provider_shared_secret_auth_enabled
else {}
)
else {}
}}
matrix_mautrix_telegram_metrics_enabled: "{{ prometheus_enabled or matrix_metrics_exposure_enabled }}"
@@ -2501,6 +2499,39 @@ matrix_hookshot_public_hostname: "{{ matrix_server_fqn_matrix }}"
#
######################################################################
######################################################################
#
# matrix-bridge-meshtastic-relay
#
######################################################################
# We don't enable bridges by default.
matrix_meshtastic_relay_enabled: false
matrix_meshtastic_relay_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_meshtastic_relay_container_image_registry_prefix_upstream_default }}"
matrix_meshtastic_relay_matrix_host: "{{ matrix_domain }}"
matrix_meshtastic_relay_matrix_homeserver_url: "{{ matrix_addons_homeserver_client_api_url }}"
matrix_meshtastic_relay_container_network: "{{ matrix_addons_container_network }}"
matrix_meshtastic_relay_systemd_required_services_list_auto: |
{{
matrix_addons_homeserver_systemd_services_list
}}
matrix_meshtastic_relay_container_additional_networks_auto: |
{{
([] if matrix_addons_homeserver_container_network == '' or matrix_addons_homeserver_container_network == matrix_meshtastic_relay_container_network else [matrix_addons_homeserver_container_network])
}}
######################################################################
#
# /matrix-bridge-meshtastic-relay
#
######################################################################
######################################################################
#
# matrix-bridge-mx-puppet-steam
@@ -3681,7 +3712,7 @@ ddclient_uid: "{{ matrix_user_uid }}"
ddclient_gid: "{{ matrix_user_gid }}"
ddclient_container_image_registry_prefix: "{{ 'localhost/' if ddclient_container_image_self_build else ddclient_container_image_registry_prefix_upstream }}"
ddclient_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else ddclient_docker_image_registry_prefix_upstream_default }}"
ddclient_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else ddclient_container_image_registry_prefix_upstream_default }}"
ddclient_web: "https://cloudflare.com/cdn-cgi/trace"
@@ -4789,7 +4820,7 @@ matrix_synapse_container_labels_matrix_labels_enabled: "{{ not matrix_synapse_wo
matrix_synapse_container_labels_public_client_root_redirection_enabled: "{{ matrix_synapse_container_labels_public_client_root_redirection_url != '' }}"
matrix_synapse_container_labels_public_client_root_redirection_url: "{{ (('https://' if matrix_playbook_ssl_enabled else 'http://') + matrix_server_fqn_element) if matrix_client_element_enabled else '' }}"
matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: "{{ matrix_synapse_admin_enabled or matrix_element_admin_enabled }}"
matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: "{{ matrix_ketesa_enabled or matrix_element_admin_enabled }}"
matrix_synapse_container_labels_internal_client_synapse_admin_api_enabled: "{{ (matrix_bot_draupnir_enabled and matrix_bot_draupnir_admin_api_enabled) }}"
matrix_synapse_container_labels_internal_client_synapse_admin_api_traefik_entrypoints: "{{ matrix_playbook_internal_matrix_client_api_traefik_entrypoint_name }}"
@@ -4909,6 +4940,8 @@ matrix_synapse_experimental_features_msc4108_enabled: "{{ matrix_authentication_
matrix_synapse_experimental_features_msc4140_enabled: "{{ matrix_rtc_enabled }}"
matrix_synapse_experimental_features_msc4143_enabled: "{{ matrix_rtc_enabled }}"
matrix_synapse_experimental_features_msc4222_enabled: "{{ matrix_rtc_enabled }}"
# Disable password authentication when delegating authentication to Matrix Authentication Service.
@@ -4998,33 +5031,33 @@ matrix_synapse_auto_compressor_systemd_required_services_list_auto: |
######################################################################
#
# matrix-synapse-admin
# matrix-ketesa
#
######################################################################
matrix_synapse_admin_enabled: false
matrix_ketesa_enabled: false
matrix_synapse_admin_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_synapse_admin_container_image_registry_prefix_upstream_default }}"
matrix_ketesa_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_ketesa_container_image_registry_prefix_upstream_default }}"
matrix_synapse_admin_container_uid: "{{ matrix_user_uid }}"
matrix_synapse_admin_container_gid: "{{ matrix_user_gid }}"
matrix_ketesa_container_uid: "{{ matrix_user_uid }}"
matrix_ketesa_container_gid: "{{ matrix_user_gid }}"
matrix_synapse_admin_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '8766') if matrix_playbook_service_host_bind_interface_prefix else '' }}"
matrix_ketesa_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '8766') if matrix_playbook_service_host_bind_interface_prefix else '' }}"
matrix_synapse_admin_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}"
matrix_ketesa_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}"
matrix_synapse_admin_container_network: "{{ matrix_addons_container_network }}"
matrix_ketesa_container_network: "{{ matrix_addons_container_network }}"
matrix_synapse_admin_container_additional_networks: "{{ [matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else [] }}"
matrix_ketesa_container_additional_networks: "{{ [matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else [] }}"
matrix_synapse_admin_container_labels_traefik_enabled: "{{ matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] }}"
matrix_synapse_admin_container_labels_traefik_docker_network: "{{ matrix_playbook_reverse_proxyable_services_additional_network }}"
matrix_synapse_admin_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_primary }}"
matrix_synapse_admin_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}"
matrix_ketesa_container_labels_traefik_enabled: "{{ matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] }}"
matrix_ketesa_container_labels_traefik_docker_network: "{{ matrix_playbook_reverse_proxyable_services_additional_network }}"
matrix_ketesa_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_primary }}"
matrix_ketesa_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}"
matrix_synapse_admin_config_externalAuthProvider: "{{ matrix_authentication_service_enabled | default(false) or matrix_synapse_ext_password_provider_ldap_enabled | default(false) }}"
matrix_ketesa_config_externalAuthProvider: "{{ matrix_authentication_service_enabled | default(false) or matrix_synapse_ext_password_provider_ldap_enabled | default(false) }}"
matrix_synapse_admin_config_asManagedUsers_auto: |
matrix_ketesa_config_asManagedUsers_auto: |
{{
([
'^@'+(matrix_alertmanager_receiver_config_matrix_user_id_localpart | default('') | regex_escape) +':'+(matrix_domain | regex_escape)+'$',
@@ -5130,7 +5163,7 @@ matrix_synapse_admin_config_asManagedUsers_auto: |
+
([
'^@'+(matrix_mautrix_telegram_appservice_bot_username | default('') | regex_escape)+':'+(matrix_domain | regex_escape)+'$',
'^@'+(matrix_mautrix_telegram_username_template | regex_escape | replace('{userid}', '.+'))+':'+(matrix_domain | regex_escape)+'$',
'^@telegram_(channel-)?[0-9]+:'+(matrix_domain | regex_escape)+'$',
] if matrix_mautrix_telegram_enabled else [])
+
([
@@ -5174,7 +5207,7 @@ matrix_synapse_admin_config_asManagedUsers_auto: |
######################################################################
#
# /matrix-synapse-admin
# /matrix-ketesa
#
######################################################################
@@ -5528,6 +5561,7 @@ grafana_default_home_dashboard_path: |-
'dendrite': ('/etc/grafana/dashboards/node-exporter-full.json' if prometheus_node_exporter_enabled else ''),
'conduit': ('/etc/grafana/dashboards/node-exporter-full.json' if prometheus_node_exporter_enabled else ''),
'continuwuity': ('/etc/grafana/dashboards/node-exporter-full.json' if prometheus_node_exporter_enabled else ''),
'tuwunel': ('/etc/grafana/dashboards/node-exporter-full.json' if prometheus_node_exporter_enabled else ''),
}[matrix_homeserver_implementation]
}}
@@ -5588,6 +5622,7 @@ matrix_registration_shared_secret: |-
'dendrite': matrix_dendrite_client_api_registration_shared_secret | default (''),
'conduit': '',
'continuwuity': '',
'tuwunel': '',
}[matrix_homeserver_implementation]
}}
@@ -5639,7 +5674,7 @@ matrix_dendrite_container_labels_traefik_docker_network: "{{ matrix_playbook_rev
matrix_dendrite_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_primary }}"
matrix_dendrite_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}"
matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: "{{ matrix_synapse_admin_enabled }}"
matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: "{{ matrix_ketesa_enabled }}"
matrix_dendrite_container_labels_public_client_root_redirection_enabled: "{{ matrix_dendrite_container_labels_public_client_root_redirection_url != '' }}"
matrix_dendrite_container_labels_public_client_root_redirection_url: "{{ (('https://' if matrix_playbook_ssl_enabled else 'http://') + matrix_server_fqn_element) if matrix_client_element_enabled else '' }}"
@@ -5758,6 +5793,12 @@ matrix_continuwuity_hostname: "{{ matrix_server_fqn_matrix }}"
matrix_continuwuity_config_allow_federation: "{{ matrix_homeserver_federation_enabled }}"
matrix_continuwuity_config_well_known_client: "{{ matrix_homeserver_url if matrix_playbook_ssl_enabled else '' }}"
matrix_continuwuity_config_smtp_enabled: "{{ exim_relay_enabled }}"
matrix_continuwuity_config_smtp_connection_uri: "{{ ('smtp://' ~ exim_relay_identifier ~ ':8025') if exim_relay_enabled else '' }}"
matrix_continuwuity_config_smtp_sender: "{{ exim_relay_sender_address if exim_relay_enabled else '' }}"
matrix_continuwuity_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_continuwuity_container_image_registry_prefix_upstream_default }}"
matrix_continuwuity_container_network: "{{ matrix_homeserver_container_network }}"
@@ -5766,6 +5807,8 @@ matrix_continuwuity_container_additional_networks_auto: |
{{
(
([matrix_playbook_reverse_proxyable_services_additional_network] if matrix_continuwuity_container_labels_traefik_enabled and matrix_playbook_reverse_proxyable_services_additional_network else [])
+
([exim_relay_container_network] if (exim_relay_enabled and matrix_continuwuity_config_smtp_enabled and matrix_continuwuity_config_smtp_connection_uri == ('smtp://' ~ exim_relay_identifier ~ ':8025') and matrix_continuwuity_container_network != exim_relay_container_network) else [])
) | unique
}}
@@ -5784,6 +5827,8 @@ matrix_continuwuity_container_labels_public_federation_api_traefik_tls: "{{ matr
matrix_continuwuity_container_labels_internal_client_api_enabled: "{{ matrix_playbook_internal_matrix_client_api_traefik_entrypoint_enabled }}"
matrix_continuwuity_container_labels_internal_client_api_traefik_entrypoints: "{{ matrix_playbook_internal_matrix_client_api_traefik_entrypoint_name }}"
matrix_continuwuity_config_rtc_foci_livekit_url: "{{ matrix_livekit_jwt_service_public_url if matrix_livekit_jwt_service_enabled else '' }}"
matrix_continuwuity_config_turn_uris: "{{ coturn_turn_uris if coturn_enabled else [] }}"
matrix_continuwuity_config_turn_secret: "{{ coturn_turn_static_auth_secret if (coturn_enabled and coturn_authentication_method == 'auth-secret') else '' }}"
matrix_continuwuity_config_turn_username: "{{ coturn_lt_cred_mech_username if (coturn_enabled and coturn_authentication_method == 'lt-cred-mech') else '' }}"
@@ -5791,6 +5836,11 @@ matrix_continuwuity_config_turn_password: "{{ coturn_lt_cred_mech_password if (c
matrix_continuwuity_self_check_validate_certificates: "{{ matrix_playbook_ssl_enabled }}"
matrix_continuwuity_systemd_wanted_services_list_auto: |
{{
([exim_relay_identifier ~ '.service'] if (exim_relay_enabled and matrix_continuwuity_config_smtp_enabled and matrix_continuwuity_config_smtp_connection_uri == ('smtp://' ~ exim_relay_identifier ~ ':8025')) else [])
}}
######################################################################
#
# /matrix-continuwuity
@@ -5798,6 +5848,67 @@ matrix_continuwuity_self_check_validate_certificates: "{{ matrix_playbook_ssl_en
######################################################################
######################################################################
#
# matrix-tuwunel
#
######################################################################
matrix_tuwunel_enabled: "{{ matrix_homeserver_implementation == 'tuwunel' }}"
matrix_tuwunel_hostname: "{{ matrix_server_fqn_matrix }}"
matrix_tuwunel_config_allow_federation: "{{ matrix_homeserver_federation_enabled }}"
matrix_tuwunel_config_well_known_client: "{{ matrix_homeserver_url if matrix_playbook_ssl_enabled else '' }}"
matrix_tuwunel_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_tuwunel_container_image_registry_prefix_upstream_default }}"
matrix_tuwunel_container_network: "{{ matrix_homeserver_container_network }}"
matrix_tuwunel_container_additional_networks_auto: |
{{
(
([matrix_playbook_reverse_proxyable_services_additional_network] if matrix_tuwunel_container_labels_traefik_enabled and matrix_playbook_reverse_proxyable_services_additional_network else [])
) | unique
}}
matrix_tuwunel_container_labels_traefik_enabled: "{{ matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] and not matrix_synapse_workers_enabled }}"
matrix_tuwunel_container_labels_traefik_docker_network: "{{ matrix_playbook_reverse_proxyable_services_additional_network }}"
matrix_tuwunel_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_primary }}"
matrix_tuwunel_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}"
matrix_tuwunel_container_labels_public_client_root_redirection_enabled: "{{ matrix_tuwunel_container_labels_public_client_root_redirection_url != '' }}"
matrix_tuwunel_container_labels_public_client_root_redirection_url: "{{ (('https://' if matrix_playbook_ssl_enabled else 'http://') + matrix_server_fqn_element) if matrix_client_element_enabled else '' }}"
matrix_tuwunel_container_labels_public_federation_api_traefik_hostname: "{{ matrix_server_fqn_matrix_federation }}"
matrix_tuwunel_container_labels_public_federation_api_traefik_entrypoints: "{{ matrix_federation_traefik_entrypoint_name }}"
matrix_tuwunel_container_labels_public_federation_api_traefik_tls: "{{ matrix_federation_traefik_entrypoint_tls }}"
matrix_tuwunel_container_labels_internal_client_api_enabled: "{{ matrix_playbook_internal_matrix_client_api_traefik_entrypoint_enabled }}"
matrix_tuwunel_container_labels_internal_client_api_traefik_entrypoints: "{{ matrix_playbook_internal_matrix_client_api_traefik_entrypoint_name }}"
matrix_tuwunel_config_well_known_livekit_url: "{{ matrix_livekit_jwt_service_public_url if matrix_livekit_jwt_service_enabled else '' }}"
matrix_tuwunel_config_turn_uris: "{{ coturn_turn_uris if coturn_enabled else [] }}"
matrix_tuwunel_config_turn_secret: "{{ coturn_turn_static_auth_secret if (coturn_enabled and coturn_authentication_method == 'auth-secret') else '' }}"
matrix_tuwunel_config_turn_username: "{{ coturn_lt_cred_mech_username if (coturn_enabled and coturn_authentication_method == 'lt-cred-mech') else '' }}"
matrix_tuwunel_config_turn_password: "{{ coturn_lt_cred_mech_password if (coturn_enabled and coturn_authentication_method == 'lt-cred-mech') else '' }}"
matrix_tuwunel_self_check_validate_certificates: "{{ matrix_playbook_ssl_enabled }}"
matrix_tuwunel_systemd_wanted_services_list_auto: |
{{
([coturn_identifier ~ '.service'] if coturn_enabled else [])
}}
######################################################################
#
# /matrix-tuwunel
#
######################################################################
######################################################################
#
# matrix-user-creator
@@ -5952,9 +6063,8 @@ matrix_static_files_file_matrix_client_property_org_matrix_msc2965_authenticatio
matrix_static_files_file_matrix_client_property_m_tile_server_entries_enabled: "{{ matrix_client_element_location_sharing_enabled }}"
matrix_static_files_file_matrix_client_property_m_tile_server_map_style_url: "{{ ('https://' if matrix_playbook_ssl_enabled else 'http://') + matrix_server_fqn_element }}/map_style.json"
# We set this regardless of whether synapse-admin is enabled, because people may wish to use a hosted (externally) synapse-admin installation and still have it auto-configured.
# See: https://github.com/etkecc/synapse-admin/pull/126
matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_auto: "{{ matrix_synapse_admin_configuration if matrix_homeserver_implementation == 'synapse' else {} }}"
# We set this regardless of whether Ketesa is enabled, because people may wish to use a hosted (externally) Ketesa installation and still have it auto-configured.
matrix_static_files_file_matrix_client_property_cc_etke_ketesa_auto: "{{ matrix_ketesa_configuration if matrix_homeserver_implementation == 'synapse' else {} }}"
matrix_static_files_file_matrix_client_property_org_matrix_msc4143_rtc_foci_enabled: "{{ matrix_livekit_jwt_service_enabled }}"
matrix_static_files_file_matrix_client_property_org_matrix_msc4143_rtc_foci_auto: |-
File diff suppressed because it is too large Load Diff
+154 -158
View File
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:59+0100\n"
"PO-Revision-Date: 2024-12-20 14:56+0200\n"
"Last-Translator: \n"
"Language: bg\n"
@@ -19,10 +19,11 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../README.md:1
msgid "[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)"
#, fuzzy
msgid "[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com&fetchMode=summary)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate) [![REUSE status](https://api.reuse.software/badge/github.com/spantaleev/matrix-docker-ansible-deploy)](https://api.reuse.software/info/github.com/spantaleev/matrix-docker-ansible-deploy)"
msgstr "[![Matrix стая за поддържка](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)"
#: ../../../README.md:1
@@ -33,6 +34,10 @@ msgstr "Matrix стая за поддръжка"
msgid "donate"
msgstr "дарения"
#: ../../../README.md:1
msgid "REUSE status"
msgstr ""
#: ../../../README.md:3
msgid "Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker"
msgstr "Настройка на Matrix (отворена мрежа за сигурна децентрализирана комуникация) чрез Ansible и Docker"
@@ -179,16 +184,16 @@ msgstr "[Връзка](docs/configuring-playbook-conduit.md)"
#: ../../../README.md
#, fuzzy
msgid "[conduwuit](https://conduwuit.puppyirl.gay/)"
msgid "[continuwuity](https://continuwuity.org)"
msgstr "[Conduit](https://conduit.rs)"
#: ../../../README.md
msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit is a fork of Conduit."
msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network."
msgstr ""
#: ../../../README.md
#, fuzzy
msgid "[Link](docs/configuring-playbook-conduwuit.md)"
msgid "[Link](docs/configuring-playbook-continuwuity.md)"
msgstr "[Връзка](docs/configuring-playbook-conduit.md)"
#: ../../../README.md
@@ -247,6 +252,15 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-client-cinny.md)"
msgstr ""
#: ../../../README.md
msgid "[Sable](https://github.com/7w1/sable)"
msgstr ""
#: ../../../README.md
#, fuzzy
msgid "[Link](docs/configuring-playbook-client-sable.md)"
msgstr "[Връзка](docs/configuring-playbook-synapse.md)"
#: ../../../README.md
msgid "[SchildiChat Web](https://schildi.chat/)"
msgstr ""
@@ -259,11 +273,24 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-client-schildichat-web.md)"
msgstr ""
#: ../../../README.md:69
#: ../../../README.md
msgid "[FluffyChat Web](https://fluffychat.im/)"
msgstr ""
#: ../../../README.md
msgid "The cutest messenger in Matrix"
msgstr ""
#: ../../../README.md
#, fuzzy
msgid "[Link](docs/configuring-playbook-client-fluffychat-web.md)"
msgstr "[Връзка](docs/configuring-playbook-conduit.md)"
#: ../../../README.md:71
msgid "Server Components"
msgstr ""
#: ../../../README.md:71
#: ../../../README.md:73
msgid "Services that run on the server to make the various parts of your installation work."
msgstr ""
@@ -279,24 +306,12 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-external-postgres.md)"
msgstr ""
#: ../../../README.md
msgid "[coturn](https://github.com/coturn/coturn)"
msgstr ""
#: ../../../README.md
msgid "STUN/TURN server for WebRTC audio/video calls"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-turn.md)"
msgstr ""
#: ../../../README.md
msgid "[Traefik](https://doc.traefik.io/traefik/)"
msgstr ""
#: ../../../README.md
msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](docs/configuring-playbook-own-webserver.md)"
msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. [Using your own webserver](docs/configuring-playbook-own-webserver.md) is also possible."
msgstr ""
#: ../../../README.md
@@ -328,15 +343,15 @@ msgid "[Link](docs/configuring-playbook-email.md)"
msgstr ""
#: ../../../README.md
msgid "[ma1sd](https://github.com/ma1uta/ma1sd)"
msgid "[coturn](https://github.com/coturn/coturn)"
msgstr ""
#: ../../../README.md
msgid "Matrix Identity Server"
msgid "STUN/TURN server for WebRTC audio/video calls"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-ma1sd.md)"
msgid "[Link](docs/configuring-playbook-turn.md)"
msgstr ""
#: ../../../README.md
@@ -351,11 +366,24 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-dynamic-dns.md)"
msgstr "[Връзка](docs/configuring-playbook-dynamic-dns.md)"
#: ../../../README.md:83
#: ../../../README.md
msgid "Matrix RTC stack"
msgstr ""
#: ../../../README.md
msgid "Supporting components ([LiveKit Server](docs/configuring-playbook-livekit-server.md) and [LiveKit JWT Service](docs/configuring-playbook-livekit-jwt-service.md)) for in-app audio/video calls for Matrix clients"
msgstr ""
#: ../../../README.md
#, fuzzy
msgid "[Link](docs/configuring-playbook-matrix-rtc.md)"
msgstr "[Връзка](docs/configuring-playbook-dynamic-dns.md)"
#: ../../../README.md:85
msgid "Authentication"
msgstr ""
#: ../../../README.md:85
#: ../../../README.md:87
msgid "Extend and modify how users are authenticated on your homeserver."
msgstr ""
@@ -400,7 +428,7 @@ msgid "[matrix-ldap-registration-proxy](https://gitlab.com/activism.internationa
msgstr ""
#: ../../../README.md
msgid "A proxy that handles Matrix registration requests and forwards them to LDAP."
msgid "Proxy that handles Matrix registration requests and forwards them to LDAP"
msgstr ""
#: ../../../README.md
@@ -412,7 +440,7 @@ msgid "[matrix-registration](https://github.com/ZerataX/matrix-registration)"
msgstr ""
#: ../../../README.md
msgid "A simple python application to have a token based Matrix registration"
msgid "Simple python application to have a token based Matrix registration"
msgstr ""
#: ../../../README.md
@@ -420,7 +448,7 @@ msgid "[Link](docs/configuring-playbook-matrix-registration.md)"
msgstr ""
#: ../../../README.md
msgid "[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (UVS)"
msgid "[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service)"
msgstr ""
#: ../../../README.md
@@ -436,18 +464,18 @@ msgid "[synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispa
msgstr ""
#: ../../../README.md
msgid "A spam checker module"
msgid "Spam checker module"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-synapse-simple-antispam.md)"
msgstr ""
#: ../../../README.md:97
#: ../../../README.md:99
msgid "File Storage"
msgstr ""
#: ../../../README.md:99
#: ../../../README.md:101
msgid "Use alternative file storage to the default `media_store` folder."
msgstr ""
@@ -476,18 +504,18 @@ msgid "[matrix-media-repo](https://github.com/turt2live/matrix-media-repo)"
msgstr ""
#: ../../../README.md
msgid "matrix-media-repo is a highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
msgid "Highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-matrix-media-repo.md)"
msgstr ""
#: ../../../README.md:107
#: ../../../README.md:109
msgid "Bridges"
msgstr ""
#: ../../../README.md:109
#: ../../../README.md:111
msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
msgstr ""
@@ -563,6 +591,19 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-bridge-mautrix-wsproxy.md)"
msgstr ""
#: ../../../README.md
msgid "[mautrix-bluesky](https://github.com/mautrix/bluesky)"
msgstr ""
#: ../../../README.md
msgid "Bridge to [Bluesky](https://bsky.social/)"
msgstr ""
#: ../../../README.md
#, fuzzy
msgid "[Link](docs/configuring-playbook-bridge-mautrix-bluesky.md)"
msgstr "[Връзка](docs/configuring-playbook-conduit.md)"
#: ../../../README.md
msgid "[mautrix-twitter](https://github.com/mautrix/twitter)"
msgstr ""
@@ -659,14 +700,6 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-bridge-appservice-discord.md)"
msgstr ""
#: ../../../README.md
msgid "[matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack)"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-bridge-appservice-slack.md)"
msgstr ""
#: ../../../README.md
msgid "[matrix-hookshot](https://github.com/matrix-org/matrix-hookshot)"
msgstr ""
@@ -691,6 +724,19 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-bridge-matrix-bridge-sms.md)"
msgstr ""
#: ../../../README.md
msgid "[matrix-steam-bridge](https://github.com/jasonlaguidice/matrix-steam-bridge)"
msgstr ""
#: ../../../README.md
msgid "Bridge to [Steam](https://steampowered.com/)"
msgstr ""
#: ../../../README.md
#, fuzzy
msgid "[Link](docs/configuring-playbook-bridge-steam.md)"
msgstr "[Връзка](docs/configuring-playbook-synapse.md)"
#: ../../../README.md
msgid "[matrix-wechat](https://github.com/duo/matrix-wechat)"
msgstr ""
@@ -715,62 +761,6 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-bridge-heisenbridge.md)"
msgstr ""
#: ../../../README.md
msgid "[go-skype-bridge](https://github.com/kelaresg/go-skype-bridge)"
msgstr ""
#: ../../../README.md
msgid "Bridge to [Skype](https://www.skype.com)"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-bridge-go-skype-bridge.md)"
msgstr ""
#: ../../../README.md
msgid "[mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack)"
msgstr ""
#: ../../../README.md
msgid "Bridge to [Slack](https://slack.com)"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-slack.md)"
msgstr ""
#: ../../../README.md
msgid "[mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram)"
msgstr ""
#: ../../../README.md
msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-instagram.md)"
msgstr ""
#: ../../../README.md
msgid "[mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter)"
msgstr ""
#: ../../../README.md
msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-twitter.md)"
msgstr ""
#: ../../../README.md
msgid "[mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord)"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-discord.md)"
msgstr ""
#: ../../../README.md
msgid "[mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme)"
msgstr ""
@@ -784,7 +774,7 @@ msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-groupme.md)"
msgstr ""
#: ../../../README.md
msgid "[mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam)"
msgid "[mx-puppet-steam](https://codeberg.org/icewind/mx-puppet-steam)"
msgstr ""
#: ../../../README.md
@@ -807,11 +797,11 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-bridge-postmoogle.md)"
msgstr ""
#: ../../../README.md:141
#: ../../../README.md:139
msgid "Bots"
msgstr ""
#: ../../../README.md:143
#: ../../../README.md:141
msgid "Bots provide various additional functionality to your installation."
msgstr ""
@@ -820,7 +810,7 @@ msgid "[baibot](https://github.com/etkecc/baibot)"
msgstr ""
#: ../../../README.md
msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
msgid "Bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
msgstr ""
#: ../../../README.md
@@ -856,7 +846,7 @@ msgid "[maubot](https://github.com/maubot/maubot)"
msgstr ""
#: ../../../README.md
msgid "A plugin-based Matrix bot system"
msgid "Plugin-based Matrix bot system"
msgstr ""
#: ../../../README.md
@@ -868,7 +858,7 @@ msgid "[Honoroit](https://github.com/etkecc/honoroit)"
msgstr ""
#: ../../../README.md
msgid "A helpdesk bot"
msgid "Helpdesk bot"
msgstr ""
#: ../../../README.md
@@ -880,7 +870,7 @@ msgid "[Mjolnir](https://github.com/matrix-org/mjolnir)"
msgstr ""
#: ../../../README.md
msgid "A moderation tool for Matrix"
msgid "Moderation tool for Matrix"
msgstr ""
#: ../../../README.md
@@ -892,7 +882,7 @@ msgid "[Draupnir](https://github.com/the-draupnir-project/Draupnir)"
msgstr ""
#: ../../../README.md
msgid "A moderation tool for Matrix (Fork of Mjolnir)"
msgid "Moderation tool for Matrix (Fork of Mjolnir)"
msgstr ""
#: ../../../README.md
@@ -911,11 +901,11 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-bot-buscarron.md)"
msgstr ""
#: ../../../README.md:156
#: ../../../README.md:154
msgid "Administration"
msgstr ""
#: ../../../README.md:158
#: ../../../README.md:156
msgid "Services that help you in administrating and monitoring your Matrix installation."
msgstr ""
@@ -944,16 +934,17 @@ msgid "[Link](docs/configuring-playbook-matrix-authentication-service.md)"
msgstr ""
#: ../../../README.md
msgid "[synapse-admin](https://github.com/etkecc/synapse-admin)"
msgid "[Ketesa](https://github.com/etkecc/ketesa)"
msgstr ""
#: ../../../README.md
msgid "A web UI tool for administrating users and rooms on your Matrix server"
msgid "Fully-featured web UI for administrating your Matrix homeserver — users, rooms, media, sessions, and more"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-synapse-admin.md)"
msgstr ""
#, fuzzy
msgid "[Link](docs/configuring-playbook-ketesa.md)"
msgstr "[Връзка](docs/configuring-playbook-synapse.md)"
#: ../../../README.md
msgid "Metrics and Graphs"
@@ -964,7 +955,7 @@ msgid "Consists of the [Prometheus](https://prometheus.io) time-series database
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-nginxlog.md))"
msgid "[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-nginx-logs-optional))"
msgstr ""
#: ../../../README.md
@@ -1003,44 +994,20 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-synapse-usage-exporter.md)"
msgstr ""
#: ../../../README.md:170
#: ../../../README.md:168
msgid "Misc"
msgstr ""
#: ../../../README.md:172
#: ../../../README.md:170
msgid "Various services that don't fit any other categories."
msgstr ""
#: ../../../README.md
msgid "[sliding-sync](https://github.com/matrix-org/sliding-sync)"
msgstr ""
#: ../../../README.md
msgid "(Superseded by Simplified Sliding Sync integrated into Synapse > `1.114` and Conduit > `0.6.0`) Sliding Sync support for clients which require it (e.g. old Element X versions before Simplified Sliding Sync was developed)"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-sliding-sync-proxy.md)"
msgstr ""
#: ../../../README.md
msgid "[synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-accept-invite)"
msgstr ""
#: ../../../README.md
msgid "A Synapse module to automatically accept invites."
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-synapse-auto-accept-invite.md)"
msgstr ""
#: ../../../README.md
msgid "[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor)"
msgstr ""
#: ../../../README.md
msgid "A cli tool that automatically compresses `state_groups` database table in background."
msgid "Cli tool that automatically compresses `state_groups` database table in background"
msgstr ""
#: ../../../README.md
@@ -1059,12 +1026,25 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-matrix-corporal.md)"
msgstr ""
#: ../../../README.md
msgid "[Matrix.to](https://github.com/matrix-org/matrix.to)"
msgstr ""
#: ../../../README.md
msgid "Simple URL redirection service for the Matrix ecosystem"
msgstr ""
#: ../../../README.md
#, fuzzy
msgid "[Link](docs/configuring-playbook-matrixto.md)"
msgstr "[Връзка](docs/configuring-playbook-synapse.md)"
#: ../../../README.md
msgid "[Etherpad](https://etherpad.org)"
msgstr ""
#: ../../../README.md
msgid "An open source collaborative text editor"
msgid "Open source collaborative text editor"
msgstr ""
#: ../../../README.md
@@ -1076,7 +1056,7 @@ msgid "[Jitsi](https://jitsi.org/)"
msgstr ""
#: ../../../README.md
msgid "An open source video-conferencing platform"
msgid "Open source video-conferencing platform"
msgstr ""
#: ../../../README.md
@@ -1088,7 +1068,7 @@ msgid "[Cactus Comments](https://cactus.chat)"
msgstr ""
#: ../../../README.md
msgid "A federated comment system built on Matrix"
msgid "Federated comment system built on Matrix"
msgstr ""
#: ../../../README.md
@@ -1100,7 +1080,7 @@ msgid "[Pantalaimon](https://github.com/matrix-org/pantalaimon)"
msgstr ""
#: ../../../README.md
msgid "An E2EE aware proxy daemon"
msgid "E2EE aware proxy daemon"
msgstr ""
#: ../../../README.md
@@ -1131,54 +1111,70 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-ntfy.md)"
msgstr ""
#: ../../../README.md:187
#: ../../../README.md
msgid "[Element Call](https://github.com/element-hq/element-call)"
msgstr ""
#: ../../../README.md
msgid "A native Matrix video conferencing application"
msgstr ""
#: ../../../README.md
#, fuzzy
msgid "[Link](docs/configuring-playbook-element-call.md)"
msgstr "[Връзка](docs/configuring-playbook-synapse.md)"
#: ../../../README.md:185
msgid "🆕 Changes"
msgstr ""
#: ../../../README.md:189
#: ../../../README.md:187
msgid "This playbook evolves over time, sometimes with backward-incompatible changes."
msgstr "Този плейбук се развива във времето и понякога съдържа обратно-несъвместими промени."
#: ../../../README.md:191
#: ../../../README.md:189
msgid "When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up with what's new."
msgstr ""
#: ../../../README.md:193
#: ../../../README.md:191
msgid "🆘 Support"
msgstr ""
#: ../../../README.md:195
#: ../../../README.md:193
msgid "Matrix room: [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)"
msgstr ""
#: ../../../README.md:197
#: ../../../README.md:195
msgid "IRC channel: `#matrix-docker-ansible-deploy` on the [Libera Chat](https://libera.chat/) IRC network (irc.libera.chat:6697)"
msgstr ""
#: ../../../README.md:199
#: ../../../README.md:197
msgid "GitHub issues: [spantaleev/matrix-docker-ansible-deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues)"
msgstr ""
#: ../../../README.md:201
#: ../../../README.md:199
msgid "🌐 Translation"
msgstr ""
#: ../../../README.md:203
#: ../../../README.md:201
msgid "See the [i18n/README.md](i18n/README.md) file for more information about translation."
msgstr "Вижте файла [i18n/README.md](i18n/README.md) за повече информация относно превода."
#: ../../../README.md:205
#: ../../../README.md:203
msgid "Translations are still work in progress."
msgstr "Все още се работи по преводите."
#: ../../../README.md:207
#: ../../../README.md:205
msgid "🤝 Related"
msgstr ""
#: ../../../README.md:209
#: ../../../README.md:207
msgid "You may also be interested in [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) - another Ansible playbook for self-hosting non-Matrix services (see its [List of supported services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md))."
msgstr ""
#: ../../../README.md:211
#: ../../../README.md:209
msgid "mash-playbook also makes use of [Traefik](./docs/configuring-playbook-traefik.md) as its reverse-proxy, so with minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md), you can make matrix-docker-ansible-deploy and mash-playbook co-exist and host Matrix and non-Matrix services on the same server."
msgstr ""
#~ msgid "[conduwuit](https://conduwuit.puppyirl.gay/)"
#~ msgstr "[Conduit](https://conduit.rs)"
+45 -45
View File
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
@@ -19,156 +19,156 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/README.md:1
#: ../../../docs/README.md:10
msgid "Table of Contents"
msgstr ""
#: ../../../docs/README.md:3
msgid "⬇️ Installaton guides <!-- NOTE: the 🚀 emoji is used by \"Getting started\" on README.md -->"
#: ../../../docs/README.md:12
msgid "⬇️ Installation guides <!-- NOTE: the 🚀 emoji is used by \"Getting started\" on README.md -->"
msgstr ""
#: ../../../docs/README.md:5
#: ../../../docs/README.md:14
msgid "There are two installation guides available for beginners and advanced users."
msgstr ""
#: ../../../docs/README.md:7
#: ../../../docs/README.md:16
msgid "⚡ **[Quick start](quick-start.md) (for beginners)**: this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"."
msgstr ""
#: ../../../docs/README.md:9
#: ../../../docs/README.md:18
msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide."
msgstr ""
#: ../../../docs/README.md:11
#: ../../../docs/README.md:20
msgid "[Prerequisites](prerequisites.md)"
msgstr ""
#: ../../../docs/README.md:13
msgid "[Configuring your DNS settings](configuring-dns.md)"
#: ../../../docs/README.md:22
msgid "[Configuring DNS settings](configuring-dns.md)"
msgstr ""
#: ../../../docs/README.md:15
#: ../../../docs/README.md:24
msgid "[Getting the playbook](getting-the-playbook.md)"
msgstr ""
#: ../../../docs/README.md:17
#: ../../../docs/README.md:26
msgid "[Configuring the playbook](configuring-playbook.md)"
msgstr ""
#: ../../../docs/README.md:19
#: ../../../docs/README.md:28
msgid "[Installing](installing.md)"
msgstr ""
#: ../../../docs/README.md:21
#: ../../../docs/README.md:30
msgid "🛠️ Configuration options"
msgstr ""
#: ../../../docs/README.md:28
#: ../../../docs/README.md:37
msgid "You can check useful documentation for configuring components here: [Configuring the playbook](configuring-playbook.md)"
msgstr ""
#: ../../../docs/README.md:30
#: ../../../docs/README.md:39
msgid "[Administration](configuring-playbook.md#administration) — services that help you in administrating and monitoring your Matrix installation"
msgstr ""
#: ../../../docs/README.md:32
#: ../../../docs/README.md:41
msgid "[Authentication and user-related](configuring-playbook.md#authentication-and-user-related) — extend and modify how users are authenticated on your homeserver"
msgstr ""
#: ../../../docs/README.md:34
#: ../../../docs/README.md:43
msgid "[Bots](configuring-playbook.md#bots) — bots provide various additional functionality to your installation"
msgstr ""
#: ../../../docs/README.md:36
#: ../../../docs/README.md:45
msgid "[Bridges](configuring-playbook.md#bridging-other-networks) — bridges can be used to connect your Matrix installation with third-party communication networks"
msgstr ""
#: ../../../docs/README.md:38
#: ../../../docs/README.md:47
msgid "[Clients](configuring-playbook.md#clients) — web clients for Matrix that you can host on your own domains"
msgstr ""
#: ../../../docs/README.md:40
#: ../../../docs/README.md:49
msgid "[Core service adjustments](configuring-playbook.md#core-service-adjustments) — backbone of your Matrix system"
msgstr ""
#: ../../../docs/README.md:42
#: ../../../docs/README.md:51
msgid "[File Storage](configuring-playbook.md#file-storage) — use alternative file storage to the default `media_store` folder"
msgstr ""
#: ../../../docs/README.md:46
#: ../../../docs/README.md:55
msgid "[Other specialized services](configuring-playbook.md#other-specialized-services) — various services that don't fit any other categories"
msgstr ""
#: ../../../docs/README.md:48
#: ../../../docs/README.md:57
msgid "👨‍🔧 Maintenance"
msgstr ""
#: ../../../docs/README.md:50
#: ../../../docs/README.md:59
msgid "If your server and services experience issues, feel free to come to [our support room](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) and ask for help."
msgstr ""
#: ../../../docs/README.md:54
msgid "[Checking if services work](maintenance-checking-services.md)"
msgstr ""
#: ../../../docs/README.md:56
#: ../../../docs/README.md:63
msgid "[Maintenance and Troubleshooting](maintenance-and-troubleshooting.md)"
msgstr ""
#: ../../../docs/README.md:58
#: ../../../docs/README.md:65
msgid "[PostgreSQL maintenance](maintenance-postgres.md)"
msgstr ""
#: ../../../docs/README.md:60
#: ../../../docs/README.md:67
msgid "[Synapse maintenance](maintenance-synapse.md)"
msgstr ""
#: ../../../docs/README.md:62
#: ../../../docs/README.md:69
msgid "[Upgrading services](maintenance-upgrading-services.md)"
msgstr ""
#: ../../../docs/README.md:64
#: ../../../docs/README.md:71
msgid "Other documentation pages <!-- NOTE: this header's title and the section below need optimization -->"
msgstr ""
#: ../../../docs/README.md:66
#: ../../../docs/README.md:73
msgid "️ **[FAQ](faq.md)** — various Frequently Asked Questions about Matrix, with a focus on this Ansible playbook"
msgstr ""
#: ../../../docs/README.md:70
#: ../../../docs/README.md:77
msgid "[Alternative architectures](alternative-architectures.md)"
msgstr ""
#: ../../../docs/README.md:72
#: ../../../docs/README.md:79
msgid "[Container images used by the playbook](container-images.md)"
msgstr ""
#: ../../../docs/README.md:74
#: ../../../docs/README.md:81
msgid "[Obtaining an Access Token](obtaining-access-tokens.md)"
msgstr ""
#: ../../../docs/README.md:76
#: ../../../docs/README.md:83
msgid "[Playbook tags](playbook-tags.md)"
msgstr ""
#: ../../../docs/README.md:78
#: ../../../docs/README.md:85
msgid "[Registering users](registering-users.md)"
msgstr ""
#: ../../../docs/README.md:80
#: ../../../docs/README.md:87
msgid "[Running `just` commands](just.md)"
msgstr ""
#: ../../../docs/README.md:82
#: ../../../docs/README.md:89
msgid "[Self-building](self-building.md)"
msgstr ""
#: ../../../docs/README.md:84
#: ../../../docs/README.md:91
msgid "[Uninstalling](uninstalling.md)"
msgstr ""
#: ../../../docs/README.md:86
#: ../../../docs/README.md:93
msgid "[Updating users passwords](updating-users-passwords.md)"
msgstr ""
#: ../../../docs/README.md:95
msgid "[Using Ansible for the playbook](ansible.md)"
msgstr ""
@@ -163,7 +163,7 @@ msgid "Granting Users the ability to use D4A"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:97
msgid "Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recomendation. Using the chat is recomended."
msgid "Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recomendation. Using the chat is recommended."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:99
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
@@ -19,431 +19,459 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bot-baibot.md:1
#: ../../../docs/configuring-playbook-bot-baibot.md:8
msgid "Setting up baibot (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:8
#: ../../../docs/configuring-playbook-bot-baibot.md:15
msgid "🤖 [baibot](https://github.com/etkecc/baibot) (pronounced bye-bot) is a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:10
#: ../../../docs/configuring-playbook-bot-baibot.md:17
msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as many well as other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:12
#: ../../../docs/configuring-playbook-bot-baibot.md:19
msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to [matrix-chatgpt-bot](./configuring-playbook-bot-chatgpt.md). See the [baibot](https://github.com/etkecc/baibot) project and its documentation for more information."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:14
#: ../../../docs/configuring-playbook-bot-baibot.md:21
msgid "Prerequisites"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:16
#: ../../../docs/configuring-playbook-bot-baibot.md:23
msgid "API access to one or more LLM [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:18
#: ../../../docs/configuring-playbook-bot-baibot.md:25
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:20
#: ../../../docs/configuring-playbook-bot-baibot.md:27
msgid "There are **a lot of configuration options** (some required, some possibly required, some optional), so they're **split into multiple sections below**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:23
#: ../../../docs/configuring-playbook-bot-baibot.md:30
msgid "[Base configuration](#base-configuration)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:24
#: ../../../docs/configuring-playbook-bot-baibot.md:31
msgid "[👮‍♂️ Administrator configuration](#-administrator-configuration)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:25
#: ../../../docs/configuring-playbook-bot-baibot.md:32
msgid "[👥 Initial users configuration](#-initial-users-configuration)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:26
#: ../../../docs/configuring-playbook-bot-baibot.md:33
msgid "[🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:27
#: ../../../docs/configuring-playbook-bot-baibot.md:34
msgid "[🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:29
#: ../../../docs/configuring-playbook-bot-baibot.md:36
msgid "Depending on your current `vars.yml` file and desired configuration, **you may require more than just the [base configuration](#base-configuration)**."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:31
#: ../../../docs/configuring-playbook-bot-baibot.md:38
msgid "Base configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:33
#: ../../../docs/configuring-playbook-bot-baibot.md:40
msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:71
msgid "As mentioned above, **this may not be enough**. Continue with the configuration sections below."
#: ../../../docs/configuring-playbook-bot-baibot.md:42
msgid "Authentication can be configured in one of two mutually-exclusive ways:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:73
msgid "👮‍♂️ Administrator configuration"
#: ../../../docs/configuring-playbook-bot-baibot.md:44
msgid "**Password authentication** (`matrix_bot_baibot_config_user_password`) - recommended for most playbook-managed setups, because it integrates with automatic user creation flow used by the playbook, and auto-creates the bot account"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:75
#: ../../../docs/configuring-playbook-bot-baibot.md:99
msgid "This is an addition to the [base configuration](#base-configuration)."
#: ../../../docs/configuring-playbook-bot-baibot.md:45
msgid "**Access-token authentication** (`matrix_bot_baibot_config_user_access_token` + `matrix_bot_baibot_config_user_device_id`) - useful for specific [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md)/OIDC setups where password authentication is not available or not desired"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:77
msgid "To specify who is considered a bot [👮‍♂️ Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators), you either need to specify `matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The latter is a single variable which affects all bridges and bots."
#: ../../../docs/configuring-playbook-bot-baibot.md:47
msgid "Even when [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) is enabled, password authentication is still typically the best fit for baibot if you're using a playbook-managed bot account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:79
msgid "If `matrix_admin` is already configured in your `vars.yml` configuration, you can skip this section."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:81
#: ../../../docs/configuring-playbook-bot-baibot.md:110
msgid "**If necessary**, add the following configuration to your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:95
msgid "👥 Initial users configuration"
#: ../../../docs/configuring-playbook-bot-baibot.md:49
msgid "For upstream details, see baibot's [🔐 Authentication](https://github.com/etkecc/baibot/blob/main/docs/configuration/authentication.md) documentation."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:97
msgid "By default, **all users on your homeserver are considered allowed users**. If that's OK, you can skip this section."
msgid "As mentioned above, **this may not be enough**. Continue with the configuration sections below."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:99
msgid "👮‍♂️ Administrator configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:101
msgid "To specify who is considered a bot [👥 User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), you may:"
#: ../../../docs/configuring-playbook-bot-baibot.md:125
msgid "This is an addition to the [base configuration](#base-configuration)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:103
msgid "To specify who is considered a bot [👮‍♂️ Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators), you either need to specify `matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The latter is a single variable which affects all bridges and bots."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:105
msgid "If `matrix_admin` is already configured in your `vars.yml` configuration, you can skip this section."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:107
#: ../../../docs/configuring-playbook-bot-baibot.md:136
msgid "**If necessary**, add the following configuration to your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:121
msgid "👥 Initial users configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:123
msgid "By default, **all users on your homeserver are considered allowed users**. If that's OK, you can skip this section."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:127
msgid "To specify who is considered a bot [👥 User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), you may:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:129
msgid "define an **initial** value for `matrix_bot_baibot_config_initial_global_config_user_patterns` Ansible variable, as shown below"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:104
#: ../../../docs/configuring-playbook-bot-baibot.md:130
msgid "configure the list at runtime via the bot's `!bai access set-users SPACE_SEPARATED_PATTERNS` command"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:106
#: ../../../docs/configuring-playbook-bot-baibot.md:132
msgid "Configuring `matrix_bot_baibot_config_initial_global_config_user_patterns` is optional, but it can be useful to pre-configure the bot with a list of users who should have access to the bot's features."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:108
#: ../../../docs/configuring-playbook-bot-baibot.md:134
msgid "**Note**: Once initially configured, the allowed users list **cannot be managed via Ansible anymore**. It can only be managed subsequently via bot commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:122
#: ../../../docs/configuring-playbook-bot-baibot.md:148
msgid "🤖 Configuring agents via Ansible"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:124
#: ../../../docs/configuring-playbook-bot-baibot.md:150
msgid "You are **not required** to define agents [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration) via Ansible. **To get started quickly**, you can **skip this section and define agents at runtime via chat commands** (following the bot's guidance)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:126
#: ../../../docs/configuring-playbook-bot-baibot.md:152
msgid "Privileged users (like the [👮‍♂️ Administrator](#-administrator-configuration), but potentially others too — see the upstream [🔒 access](https://github.com/etkecc/baibot/blob/main/docs/access.md) documentation) can **define agents dynamically at any time** via chat commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:128
#: ../../../docs/configuring-playbook-bot-baibot.md:154
msgid "The Ansible role includes preset variables for easily enabling some [🤖 agents](https://github.com/etkecc/baibot/blob/main/docs/agents.md) on various [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md) (e.g. OpenAI, etc)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:130
#: ../../../docs/configuring-playbook-bot-baibot.md:156
msgid "Besides the presets, the Ansible role also includes support for configuring additional statically-defined agents via the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:132
#: ../../../docs/configuring-playbook-bot-baibot.md:158
msgid "Agents defined statically and those created dynamically (via chat) are named differently, so **conflict cannot arise**."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:134
#: ../../../docs/configuring-playbook-bot-baibot.md:160
msgid "Depending on your propensity for [GitOps](https://en.wikipedia.org/wiki/DevOps#GitOps), you may prefer to define agents statically via Ansible, or you may wish to do it dynamically via chat."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:136
#: ../../../docs/configuring-playbook-bot-baibot.md:162
msgid "Before proceeding, we recommend reading the upstream documentation on [How to choose a provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#how-to-choose-a-provider). In short, it's probably best to go with [OpenAI](#openai)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:138
#: ../../../docs/configuring-playbook-bot-baibot.md:164
msgid "Anthropic"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:140
#: ../../../docs/configuring-playbook-bot-baibot.md:166
msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Anthropic provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic) with the help of the playbook's preset variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:142
#: ../../../docs/configuring-playbook-bot-baibot.md:166
#: ../../../docs/configuring-playbook-bot-baibot.md:197
#: ../../../docs/configuring-playbook-bot-baibot.md:225
#: ../../../docs/configuring-playbook-bot-baibot.md:168
#: ../../../docs/configuring-playbook-bot-baibot.md:192
#: ../../../docs/configuring-playbook-bot-baibot.md:223
#: ../../../docs/configuring-playbook-bot-baibot.md:251
msgid "Here's an example **addition** to your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:158
#: ../../../docs/configuring-playbook-bot-baibot.md:189
#: ../../../docs/configuring-playbook-bot-baibot.md:184
#: ../../../docs/configuring-playbook-bot-baibot.md:215
#: ../../../docs/configuring-playbook-bot-baibot.md:243
#: ../../../docs/configuring-playbook-bot-baibot.md:241
#: ../../../docs/configuring-playbook-bot-baibot.md:275
msgid "If you'd like to use more than one model, take a look at the [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset) section below."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:160
#: ../../../docs/configuring-playbook-bot-baibot.md:191
#: ../../../docs/configuring-playbook-bot-baibot.md:186
#: ../../../docs/configuring-playbook-bot-baibot.md:217
#: ../../../docs/configuring-playbook-bot-baibot.md:245
#: ../../../docs/configuring-playbook-bot-baibot.md:243
#: ../../../docs/configuring-playbook-bot-baibot.md:277
msgid "💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:162
#: ../../../docs/configuring-playbook-bot-baibot.md:188
msgid "Groq"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:164
#: ../../../docs/configuring-playbook-bot-baibot.md:190
msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Groq provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq) with the help of the playbook's preset variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:187
#: ../../../docs/configuring-playbook-bot-baibot.md:213
msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/groq`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:193
#: ../../../docs/configuring-playbook-bot-baibot.md:219
msgid "Mistral"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:195
#: ../../../docs/configuring-playbook-bot-baibot.md:221
msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [🇫🇷 Mistral provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral) with the help of the playbook's preset variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:213
#: ../../../docs/configuring-playbook-bot-baibot.md:239
msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/mistral`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:219
#: ../../../docs/configuring-playbook-bot-baibot.md:245
msgid "OpenAI"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:221
#: ../../../docs/configuring-playbook-bot-baibot.md:247
msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai) with the help of the playbook's preset variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:223
#: ../../../docs/configuring-playbook-bot-baibot.md:249
msgid "The OpenAI provider is **only meant to be used with OpenAI's official API** and compatibility with other services (which do not fully adhere to the OpenAI API spec completely) is limited. **If you're targeting an OpenAI-compatible service**, use the [OpenAI Compatible](#openai-compatible) provider instead."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:241
#: ../../../docs/configuring-playbook-bot-baibot.md:273
msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/openai`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:247
#: ../../../docs/configuring-playbook-bot-baibot.md:279
msgid "OpenAI Compatible"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:249
#: ../../../docs/configuring-playbook-bot-baibot.md:281
msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI Compatible provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai-compatible) with the help of the playbook's preset variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:251
#: ../../../docs/configuring-playbook-bot-baibot.md:283
msgid "This provider allows you to use OpenAI-compatible API services like [OpenRouter](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openrouter), [Together AI](https://github.com/etkecc/baibot/blob/main/docs/providers.md#together-ai), etc."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:253
#: ../../../docs/configuring-playbook-bot-baibot.md:285
msgid "Some of these popular services already have **shortcut** providers (see [supported providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md#supported-providers) leading to this one behind the scenes — this make it easier to get started."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:255
#: ../../../docs/configuring-playbook-bot-baibot.md:287
msgid "As of this moment, the playbook does not include presets for any of these services, so you'll need to [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:257
#: ../../../docs/configuring-playbook-bot-baibot.md:289
msgid "Configuring additional agents (without a preset)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:259
#: ../../../docs/configuring-playbook-bot-baibot.md:291
msgid "The Ansible role may be lacking preset variables for some [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), or you may wish to statically-define an agent on the same provider twice (or more) with different configuration."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:261
#: ../../../docs/configuring-playbook-bot-baibot.md:293
msgid "It's possible to inject your own agent configuration using the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:263
#: ../../../docs/configuring-playbook-bot-baibot.md:295
msgid "You can also define providers at runtime, by chatting with the bot, so using Ansible is not a requirement."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:265
#: ../../../docs/configuring-playbook-bot-baibot.md:297
msgid "Below is an an **example** demonstrating **statically-defining agents via Ansible without using presets**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:304
#: ../../../docs/configuring-playbook-bot-baibot.md:336
msgid "Because these are [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agents, they will be given a `static/` ID prefix and will be named `static/my-openai-gpt-3.5-turbo-agent` and `static/my-ollama-agent`, respectively."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:306
#: ../../../docs/configuring-playbook-bot-baibot.md:338
msgid "💡 To figure out what to put in the `config` section, refer to the [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md) page, which contains **sample configuration YAML for each provider**."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:308
#: ../../../docs/configuring-playbook-bot-baibot.md:340
msgid "As with any [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), defining them means they exist. To actually make use of them, they need to be configured as handlers globally or in a specific room — see [Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:310
#: ../../../docs/configuring-playbook-bot-baibot.md:342
msgid "💡 You may also wish to use these new agents for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:312
#: ../../../docs/configuring-playbook-bot-baibot.md:344
msgid "🤝 Configuring initial default handlers"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:314
#: ../../../docs/configuring-playbook-bot-baibot.md:346
msgid "This section is only useful if you're [🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible), as it lets you put these agents to use as soon as the bot starts (by adjusting the bot's **initial global configuration**)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:316
#: ../../../docs/configuring-playbook-bot-baibot.md:348
msgid "If you're not configuring agents via Ansible, you can skip this section."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:318
#: ../../../docs/configuring-playbook-bot-baibot.md:350
msgid "This section is only useful the first time around. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:320
#: ../../../docs/configuring-playbook-bot-baibot.md:352
msgid "baibot supports [various purposes](https://github.com/etkecc/baibot/blob/main/docs/features.md):"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:322
#: ../../../docs/configuring-playbook-bot-baibot.md:354
msgid "[💬 text-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-generation): communicating with you via text"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:324
#: ../../../docs/configuring-playbook-bot-baibot.md:356
msgid "[🦻 speech-to-text](https://github.com/etkecc/baibot/blob/main/docs/features.md#-speech-to-text): turning your voice messages into text"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:326
#: ../../../docs/configuring-playbook-bot-baibot.md:358
msgid "[🗣️ text-to-speech](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-to-speech): turning bot or users text messages into voice messages"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:328
#: ../../../docs/configuring-playbook-bot-baibot.md:360
msgid "[🖌️ image-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-image-generation): generating images based on instructions"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:330
#: ../../../docs/configuring-playbook-bot-baibot.md:362
msgid "❓ catch-all: special purposes, indicating use as a fallback (when no specific handler is configured)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:332
#: ../../../docs/configuring-playbook-bot-baibot.md:364
msgid "[Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models) is made possible by the bot's ability to have different [🤝 handlers](https://github.com/etkecc/baibot/blob/main/docs/configuration/handlers.md) configured for different purposes."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:334
#: ../../../docs/configuring-playbook-bot-baibot.md:366
msgid "This configuration can be done as a global fallback, or per-room. Both of these [🛠️ configurations](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md) are managed at runtime (viat chat), but **the global configuration can have some initial defaults configured via Ansible**."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:336
#: ../../../docs/configuring-playbook-bot-baibot.md:368
msgid "You can configure the **initial values** for these via Ansible, via the `matrix_bot_baibot_config_initial_global_config_handler_*` variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:338
#: ../../../docs/configuring-playbook-bot-baibot.md:370
msgid "Example **additional** `vars.yml` configuration:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:355
#: ../../../docs/configuring-playbook-bot-baibot.md:387
msgid "**Note**: these are initial defaults for the bot's global configuration. As such, changing any of these values subsequently has no effect on the bot's behavior. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:357
#: ../../../docs/configuring-playbook-bot-baibot.md:389
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:359
#: ../../../docs/configuring-playbook-bot-baibot.md:391
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:361
#: ../../../docs/configuring-playbook-bot-baibot.md:393
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:363
#: ../../../docs/configuring-playbook-bot-baibot.md:395
msgid "`roles/custom/matrix-bot-baibot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:364
#: ../../../docs/configuring-playbook-bot-baibot.md:396
msgid "`roles/custom/matrix-bot-baibot/templates/config.yaml.j2` for the bot's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_bot_baibot_configuration_extension_yaml` variable"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:366
#: ../../../docs/configuring-playbook-bot-baibot.md:398
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:368
#: ../../../docs/configuring-playbook-bot-baibot.md:400
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:375
#: ../../../docs/configuring-playbook-bot-baibot.md:407
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:377
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
#: ../../../docs/configuring-playbook-bot-baibot.md:409
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account when password authentication is used."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:379
#: ../../../docs/configuring-playbook-bot-baibot.md:411
msgid "If you're using access-token authentication, the bot account must already exist and the configured token + device ID must match that account. This mode is mainly for MAS/OIDC setups where password-based bot login is not suitable."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:413
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:381
#: ../../../docs/configuring-playbook-bot-baibot.md:415
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:383
msgid "If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password."
#: ../../../docs/configuring-playbook-bot-baibot.md:417
msgid "If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password. (This note applies to password authentication mode.)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:385
#: ../../../docs/configuring-playbook-bot-baibot.md:419
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:387
#: ../../../docs/configuring-playbook-bot-baibot.md:421
msgid "To use the bot, invite it to any existing Matrix room (`/invite @baibot:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:389
#: ../../../docs/configuring-playbook-bot-baibot.md:423
msgid "If you're an allowed bot [👥 user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) (see [👥 Initial users configuration](#-initial-users-configuration)), the bot will accept your invitation and join the room."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:391
#: ../../../docs/configuring-playbook-bot-baibot.md:425
msgid "After joining, the bot will introduce itself and show information about the [✨ features](https://github.com/etkecc/baibot/blob/main/docs/features.md) that are enabled for it."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:393
#: ../../../docs/configuring-playbook-bot-baibot.md:427
msgid "If you've [🤖 configured one or more agents via Ansible](#-configuring-agents-via-ansible) and have [🤝 configured initial default handlers](#configuring-initial-default-handlers), the bot will immediately be able to make use of these agents for this new room. Otherwise, you will need to configure agents and/or handlers via chat commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:395
#: ../../../docs/configuring-playbook-bot-baibot.md:429
msgid "Send `!bai help` to the bot in the room to see the available commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:397
#: ../../../docs/configuring-playbook-bot-baibot.md:431
msgid "You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) project's documentation."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:399
#: ../../../docs/configuring-playbook-bot-baibot.md:433
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:401
msgid "As with all other services, you can find service logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-bot-baibot`"
#: ../../../docs/configuring-playbook-bot-baibot.md:435
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-baibot`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:403
msgid "The default logging level for this service is `info`, but you can increase it to `debug` (or even `trace`) with the following additional configuration:"
#: ../../../docs/configuring-playbook-bot-baibot.md:437
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:417
#: ../../../docs/configuring-playbook-bot-baibot.md:439
msgid "The default logging level for this service is `info`. If you want to increase the verbosity to `debug` (or even `trace`), add the following configuration to your `vars.yml` file and re-run the playbook:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:453
msgid "**Alternatively**, you can use a single variable to set the logging level for all of the above (bot + all libraries):"
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
@@ -19,156 +19,156 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bot-buscarron.md:1
#: ../../../docs/configuring-playbook-bot-buscarron.md:9
msgid "Setting up Buscarron (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:3
#: ../../../docs/configuring-playbook-bot-buscarron.md:11
msgid "The playbook can install and configure [Buscarron](https://github.com/etkecc/buscarron) for you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:5
#: ../../../docs/configuring-playbook-bot-buscarron.md:13
msgid "Buscarron is bot that receives HTTP POST submissions of web forms and forwards them to a Matrix room."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:7
#: ../../../docs/configuring-playbook-bot-buscarron.md:15
msgid "See the project's [documentation](https://github.com/etkecc/buscarron/blob/main/README.md) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:9
#: ../../../docs/configuring-playbook-bot-buscarron.md:17
msgid "Adjusting DNS records"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:11
#: ../../../docs/configuring-playbook-bot-buscarron.md:19
msgid "By default, this playbook installs Buscarron on the `buscarron.` subdomain (`buscarron.example.com`) and requires you to create a CNAME record for `buscarron`, which targets `matrix.example.com`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:13
#: ../../../docs/configuring-playbook-bot-buscarron.md:21
msgid "When setting, replace `example.com` with your own."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:15
#: ../../../docs/configuring-playbook-bot-buscarron.md:23
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:17
#: ../../../docs/configuring-playbook-bot-buscarron.md:25
msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:40
#: ../../../docs/configuring-playbook-bot-buscarron.md:48
msgid "Adjusting the Buscarron URL (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:42
#: ../../../docs/configuring-playbook-bot-buscarron.md:50
msgid "By tweaking the `matrix_bot_buscarron_hostname` and `matrix_bot_buscarron_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:44
#: ../../../docs/configuring-playbook-bot-buscarron.md:52
msgid "Example additional configuration for your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:55
#: ../../../docs/configuring-playbook-bot-buscarron.md:63
msgid "After changing the domain, **you may need to adjust your DNS** records to point the Buscarron domain to the Matrix server."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:57
#: ../../../docs/configuring-playbook-bot-buscarron.md:65
msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:59
#: ../../../docs/configuring-playbook-bot-buscarron.md:67
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:61
#: ../../../docs/configuring-playbook-bot-buscarron.md:69
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:63
#: ../../../docs/configuring-playbook-bot-buscarron.md:71
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:65
#: ../../../docs/configuring-playbook-bot-buscarron.md:73
msgid "`roles/custom/matrix-bot-buscarron/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:67
#: ../../../docs/configuring-playbook-bot-buscarron.md:75
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:69
#: ../../../docs/configuring-playbook-bot-buscarron.md:77
msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:76
#: ../../../docs/configuring-playbook-bot-buscarron.md:84
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:78
#: ../../../docs/configuring-playbook-bot-buscarron.md:86
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:80
#: ../../../docs/configuring-playbook-bot-buscarron.md:88
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:82
#: ../../../docs/configuring-playbook-bot-buscarron.md:90
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:84
msgid "If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password."
#: ../../../docs/configuring-playbook-bot-buscarron.md:92
msgid "If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:86
#: ../../../docs/configuring-playbook-bot-buscarron.md:94
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:88
#: ../../../docs/configuring-playbook-bot-buscarron.md:96
msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.buscarron:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:90
#: ../../../docs/configuring-playbook-bot-buscarron.md:98
msgid "After the bot joins the room, anyone can call the web form via HTTP POST method."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:92
#: ../../../docs/configuring-playbook-bot-buscarron.md:100
msgid "Here is an example for the `contact` form:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:100
#: ../../../docs/configuring-playbook-bot-buscarron.md:108
msgid "**Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:102
#: ../../../docs/configuring-playbook-bot-buscarron.md:110
msgid "you hit the homepage (HTTP `GET` request to `/`)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:103
#: ../../../docs/configuring-playbook-bot-buscarron.md:111
msgid "you submit a form to the wrong URL (`POST` request to `/non-existing-form`)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:104
#: ../../../docs/configuring-playbook-bot-buscarron.md:112
msgid "`hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:106
#: ../../../docs/configuring-playbook-bot-buscarron.md:114
msgid "If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:108
#: ../../../docs/configuring-playbook-bot-buscarron.md:116
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:110
#: ../../../docs/configuring-playbook-bot-buscarron.md:118
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-buscarron`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:112
#: ../../../docs/configuring-playbook-bot-buscarron.md:120
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:114
#: ../../../docs/configuring-playbook-bot-buscarron.md:122
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 ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
@@ -19,392 +19,421 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bot-draupnir.md:1
#: ../../../docs/configuring-playbook-bot-draupnir.md:10
msgid "Setting up Draupnir (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:3
#: ../../../docs/configuring-playbook-bot-draupnir.md:12
msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation bot for you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:5
#: ../../../docs/configuring-playbook-bot-draupnir.md:14
msgid "See the project's [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:7
#: ../../../docs/configuring-playbook-bot-draupnir.md:16
msgid "This documentation page is about installing Draupnir in bot mode. As an alternative, you can run a multi-instance Draupnir deployment by installing [Draupnir in appservice mode](./configuring-playbook-appservice-draupnir-for-all.md) (called Draupnir-for-all) instead."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:9
#: ../../../docs/configuring-playbook-bot-draupnir.md:18
msgid "If your 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:11
#: ../../../docs/configuring-playbook-bot-draupnir.md:20
msgid "Prerequisites"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:13
#: ../../../docs/configuring-playbook-bot-draupnir.md:22
msgid "Create a management room"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:15
#: ../../../docs/configuring-playbook-bot-draupnir.md:24
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:17
#: ../../../docs/configuring-playbook-bot-draupnir.md:26
msgid "[!WARNING] 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:20
#: ../../../docs/configuring-playbook-bot-draupnir.md:29
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:22
#: ../../../docs/configuring-playbook-bot-draupnir.md:31
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:24
#: ../../../docs/configuring-playbook-bot-draupnir.md:33
msgid "End-to-End Encryption support"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:26
#: ../../../docs/configuring-playbook-bot-draupnir.md:35
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:28
#: ../../../docs/configuring-playbook-bot-draupnir.md:37
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:30
#: ../../../docs/configuring-playbook-bot-draupnir.md:39
msgid "Disable Pantalaimon for Draupnir (since v2.0.0; optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:32
#: ../../../docs/configuring-playbook-bot-draupnir.md:41
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:34
#: ../../../docs/configuring-playbook-bot-draupnir.md:43
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:36
#: ../../../docs/configuring-playbook-bot-draupnir.md:45
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:38
#: ../../../docs/configuring-playbook-bot-draupnir.md:47
msgid "Native E2EE support"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:40
#: ../../../docs/configuring-playbook-bot-draupnir.md:49
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:42
#: ../../../docs/configuring-playbook-bot-draupnir.md:51
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:44
#: ../../../docs/configuring-playbook-bot-draupnir.md:53
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:55
#: ../../../docs/configuring-playbook-bot-draupnir.md:64
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:57
#: ../../../docs/configuring-playbook-bot-draupnir.md:66
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 earlier."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:76
#: ../../../docs/configuring-playbook-bot-draupnir.md:85
msgid "Create and invite the bot to the management room"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:78
#: ../../../docs/configuring-playbook-bot-draupnir.md:87
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:84
#: ../../../docs/configuring-playbook-bot-draupnir.md:93
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:86
#: ../../../docs/configuring-playbook-bot-draupnir.md:95
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:88
#: ../../../docs/configuring-playbook-bot-draupnir.md:97
msgid "Make sure the account is free from rate limiting (optional, recommended)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:90
#: ../../../docs/configuring-playbook-bot-draupnir.md:99
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:92
#: ../../../docs/configuring-playbook-bot-draupnir.md:101
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:94
#: ../../../docs/configuring-playbook-bot-draupnir.md:103
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:96
msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)."
#: ../../../docs/configuring-playbook-bot-draupnir.md:105
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:98
#: ../../../docs/configuring-playbook-bot-draupnir.md:107
msgid "Add the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:100
#: ../../../docs/configuring-playbook-bot-draupnir.md:109
msgid "To expose the APIs publicly, add the following configuration to your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:106
#: ../../../docs/configuring-playbook-bot-draupnir.md:115
msgid "Obtain an access token for admin account"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:108
#: ../../../docs/configuring-playbook-bot-draupnir.md:117
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:110
#: ../../../docs/configuring-playbook-bot-draupnir.md:119
msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:113
#: ../../../docs/configuring-playbook-bot-draupnir.md:122
msgid "Run the `curl` command"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:115
#: ../../../docs/configuring-playbook-bot-draupnir.md:124
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:117
#: ../../../docs/configuring-playbook-bot-draupnir.md:126
msgid "`ADMIN_ACCESS_TOKEN_HERE` with the access token of the admin account"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:118
#: ../../../docs/configuring-playbook-bot-draupnir.md:127
msgid "`example.com` with your base domain"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:119
#: ../../../docs/configuring-playbook-bot-draupnir.md:128
msgid "`@bot.draupnir:example.com` with the MXID of your Draupnir bot user"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:125
#: ../../../docs/configuring-playbook-bot-draupnir.md:134
#: ../../../docs/configuring-playbook-bot-draupnir.md:207
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:126
#: ../../../docs/configuring-playbook-bot-draupnir.md:135
msgid "This does not work on outdated Windows 10 as curl is not available there."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:127
#: ../../../docs/configuring-playbook-bot-draupnir.md:136
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:129
#: ../../../docs/configuring-playbook-bot-draupnir.md:138
msgid "Abuse Reports"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:131
#: ../../../docs/configuring-playbook-bot-draupnir.md:140
msgid "Draupnir can receive reports in the management room."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:133
#: ../../../docs/configuring-playbook-bot-draupnir.md:142
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:145
#: ../../../docs/configuring-playbook-bot-draupnir.md:148
msgid "Enabling synapse-http-antispam support"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:150
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:160
msgid "These protections need to be manually activated and consulting the [enabling protections](#enabling-built-in-protections) guide can be helpful or consulting upstream documentation."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:168
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:147
#: ../../../docs/configuring-playbook-bot-draupnir.md:170
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:149
#: ../../../docs/configuring-playbook-bot-draupnir.md:172
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:151
#: ../../../docs/configuring-playbook-bot-draupnir.md:174
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:153
#: ../../../docs/configuring-playbook-bot-draupnir.md:176
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:167
#: ../../../docs/configuring-playbook-bot-draupnir.md:190
msgid "Migrating from Mjolnir (Only required if migrating)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:169
#: ../../../docs/configuring-playbook-bot-draupnir.md:192
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:171
#: ../../../docs/configuring-playbook-bot-draupnir.md:194
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:173
#: ../../../docs/configuring-playbook-bot-draupnir.md:196
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:175
#: ../../../docs/configuring-playbook-bot-draupnir.md:198
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:177
#: ../../../docs/configuring-playbook-bot-draupnir.md:200
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:184
#: ../../../docs/configuring-playbook-bot-draupnir.md:209
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:211
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:186
#: ../../../docs/configuring-playbook-bot-draupnir.md:213
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:188
#: ../../../docs/configuring-playbook-bot-draupnir.md:215
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:217
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:190
#: ../../../docs/configuring-playbook-bot-draupnir.md:219
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:192
#: ../../../docs/configuring-playbook-bot-draupnir.md:221
msgid "Below is a **non-exhaustive quick-start guide** for the impatient."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:194
#: ../../../docs/configuring-playbook-bot-draupnir.md:223
msgid "Making Draupnir join and protect a room"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:196
#: ../../../docs/configuring-playbook-bot-draupnir.md:225
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:198
#: ../../../docs/configuring-playbook-bot-draupnir.md:227
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:200
#: ../../../docs/configuring-playbook-bot-draupnir.md:229
msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:202
#: ../../../docs/configuring-playbook-bot-draupnir.md:231
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:204
#: ../../../docs/configuring-playbook-bot-draupnir.md:233
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:206
#: ../../../docs/configuring-playbook-bot-draupnir.md:235
msgid "Giving Draupnir permissions to do its job"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:208
#: ../../../docs/configuring-playbook-bot-draupnir.md:237
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:210
#: ../../../docs/configuring-playbook-bot-draupnir.md:239
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:212
#: ../../../docs/configuring-playbook-bot-draupnir.md:241
msgid "Subscribing to a public policy list"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:214
#: ../../../docs/configuring-playbook-bot-draupnir.md:243
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:216
msgid "Polcy lists are maintained in Matrix rooms. A popular policy list is maintained in the public `#community-moderation-effort-bl:neko.dev` room."
#: ../../../docs/configuring-playbook-bot-draupnir.md:245
msgid "Policy lists are maintained in Matrix rooms. Popular ones maintained in the public are:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:218
msgid "You can tell Draupnir to subscribe to it by sending the following command to the Management Room: `!draupnir watch #community-moderation-effort-bl:neko.dev`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:220
msgid "Creating your own policy lists and rules"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:222
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:224
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:226
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:228
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:230
msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:232
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:233
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:235
msgid "As a result of running these commands, you may observe:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:237
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:238
msgid "applying these rules against all rooms that Draupnir is an Administrator in"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:240
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:242
msgid "Enabling built-in protections"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:244
msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the room to invite-only\")."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:246
msgid "To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room."
#: ../../../docs/configuring-playbook-bot-draupnir.md:247
msgid "`#community-moderation-effort-bl:neko.dev`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:248
msgid "To **see the configuration options for a given protection**, send a `!draupnir protections show PROTECTION_NAME` (e.g. `!draupnir protections show JoinWaveShortCircuit`)."
msgid "`#huginn-muninn-active-threats:feline.support`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:250
msgid "To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)."
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:252
msgid "To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)."
msgid "Creating your own policy lists and rules"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:254
msgid "To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)."
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:256
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:258
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:260
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:262
msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:264
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:265
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:267
msgid "As a result of running these commands, you may observe:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:269
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:270
msgid "applying these rules against all rooms that Draupnir is an Administrator in"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:272
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:274
msgid "Enabling built-in protections"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:276
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:278
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:280
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:282
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:284
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:286
msgid "To **disable a given protection**, send a command like this: `!draupnir protections disable PROTECTION_NAME` (e.g. `!draupnir protections disable JoinWaveShortCircuitProtection`)."
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
@@ -19,108 +19,140 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bot-honoroit.md:1
#: ../../../docs/configuring-playbook-bot-honoroit.md:9
msgid "Setting up Honoroit (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:3
#: ../../../docs/configuring-playbook-bot-honoroit.md:11
msgid "The playbook can install and configure [Honoroit](https://github.com/etkecc/honoroit) for you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:5
#: ../../../docs/configuring-playbook-bot-honoroit.md:13
msgid "It's a bot you can use to setup **your own helpdesk on matrix**"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:7
#: ../../../docs/configuring-playbook-bot-honoroit.md:15
msgid "See the project's [documentation](https://github.com/etkecc/honoroit/blob/main/README.md) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:9
#: ../../../docs/configuring-playbook-bot-honoroit.md:17
msgid "Adjusting DNS records (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:11
#: ../../../docs/configuring-playbook-bot-honoroit.md:19
msgid "By default, this playbook installs Honoroit on the `matrix.` subdomain, at the `/honoroit` path (https://matrix.example.com/honoroit). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:13
#: ../../../docs/configuring-playbook-bot-honoroit.md:21
msgid "If you wish to adjust it, see the section [below](#adjusting-the-honoroit-url-optional) for details about DNS configuration."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:15
#: ../../../docs/configuring-playbook-bot-honoroit.md:23
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:17
#: ../../../docs/configuring-playbook-bot-honoroit.md:25
msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:32
#: ../../../docs/configuring-playbook-bot-honoroit.md:40
msgid "Adjusting the Honoroit URL (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:34
#: ../../../docs/configuring-playbook-bot-honoroit.md:42
msgid "By tweaking the `matrix_bot_honoroit_hostname` and `matrix_bot_honoroit_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:36
#: ../../../docs/configuring-playbook-bot-honoroit.md:44
msgid "Example additional configuration for your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:44
#: ../../../docs/configuring-playbook-bot-honoroit.md:52
msgid "If you've changed the default hostname, you may need to create a CNAME record for the Honoroit domain (`honoroit.example.com`), which targets `matrix.example.com`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:46
#: ../../../docs/configuring-playbook-bot-honoroit.md:54
msgid "When setting, replace `example.com` with your own."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:48
#: ../../../docs/configuring-playbook-bot-honoroit.md:56
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:58
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:60
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:62
msgid "`roles/custom/matrix-bot-honoroit/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:64
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:50
#: ../../../docs/configuring-playbook-bot-honoroit.md:66
msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:57
#: ../../../docs/configuring-playbook-bot-honoroit.md:73
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:59
#: ../../../docs/configuring-playbook-bot-honoroit.md:75
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:61
#: ../../../docs/configuring-playbook-bot-honoroit.md:77
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:63
#: ../../../docs/configuring-playbook-bot-honoroit.md:79
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:65
msgid "If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password."
#: ../../../docs/configuring-playbook-bot-honoroit.md:81
msgid "If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:67
#: ../../../docs/configuring-playbook-bot-honoroit.md:83
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:69
#: ../../../docs/configuring-playbook-bot-honoroit.md:85
msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @honoroit:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:71
#: ../../../docs/configuring-playbook-bot-honoroit.md:87
msgid "After the bot joins the room, any Matrix user can send a message to it to start a new thread in that room."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:73
#: ../../../docs/configuring-playbook-bot-honoroit.md:89
msgid "Send `!ho help` to the bot in the room to see the available commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:75
#: ../../../docs/configuring-playbook-bot-honoroit.md:91
msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/honoroit#features)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:93
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:95
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-honoroit`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:97
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:99
msgid "If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-12-23 13:09+0900\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
@@ -19,84 +19,120 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:1
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:13
msgid "Setting up matrix-registration-bot (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:3
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:15
msgid "The playbook can install and configure [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) for you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:5
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:17
msgid "The bot allows you to easily **create and manage registration tokens** aka. invitation codes. It can be used for an invitation-based server, where you invite someone by sending them a registration token (tokens look like this: `rbalQ0zkaDSRQCOp`). They can register as per normal but have to provide a valid registration token in the final step of the registration process."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:7
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:19
msgid "See the project's [documentation](https://github.com/moan0s/matrix-registration-bot/blob/master/README.md) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:9
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:21
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:11
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:23
msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:30
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:46
msgid "The bot account will be created automatically."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:32
msgid "Installing"
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:48
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:34
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:50
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:41
msgid "**Notes**:"
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:52
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:43
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:45
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:47
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:49
msgid "If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:51
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:53
msgid "To use the bot, start a chat with `@bot.matrix-registration-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:54
msgid "`roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55
msgid "Send `help` to the bot to see the available commands."
msgid "`roles/custom/matrix-bot-matrix-registration-bot/templates/config.yaml.j2` for the bridge's default configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57
msgid "You can also refer to the upstream [Usage documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands)."
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:59
msgid "If you have any questions, or if you need help setting it up, read the [troublshooting guide](https://github.com/moan0s/matrix-registration-bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)."
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:61
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:66
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:68
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:70
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:72
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:74
msgid "If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:76
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:78
msgid "To use the bot, start a chat with `@bot.matrix-registration-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:80
msgid "Send `help` to the bot to see the available commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:82
msgid "You can also refer to the upstream [Usage documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:84
msgid "If you have any questions, or if you need help setting it up, read the [troubleshooting guide](https://github.com/moan0s/matrix-registration-bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:86
msgid "To clean the cache (session & encryption data) after you changed the bot's username, changed the login method from access_token to password etc… you can use:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:92
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:94
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-matrix-registration-bot`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:96
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:98
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 ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-12-23 13:09+0900\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
@@ -19,80 +19,116 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:1
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9
msgid "Setting up matrix-reminder-bot (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:3
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11
msgid "The playbook can install and configure [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot) for you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:5
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:13
msgid "It's a bot you can use to **schedule one-off & recurring reminders and alarms**."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:7
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:15
msgid "See the project's [documentation](https://github.com/anoadragon453/matrix-reminder-bot/blob/master/README.md) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:17
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:19
msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:26
msgid "Installing"
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:34
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:28
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:36
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:35
msgid "**Notes**:"
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:38
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:37
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:39
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:40
msgid "`roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:41
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgid "`roles/custom/matrix-bot-matrix-reminder-bot/templates/config.yaml.j2` for the bot's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_bot_matrix_reminder_bot_configuration_extension_yaml` variable"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:43
msgid "If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password."
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:45
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:52
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:54
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:56
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:58
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:60
msgid "If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:62
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:47
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:64
msgid "To use the bot, start a chat with `@bot.matrix-reminder-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:49
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:66
msgid "You can also add the bot to any existing Matrix room (`/invite @bot.matrix-reminder-bot:example.com`)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:51
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:68
msgid "Basic usage is like this: `!remindme in 2 minutes; This is a test`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:53
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:70
msgid "Send `!help reminders` to the room to see the bot's help menu for additional commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:55
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:72
msgid "You can also refer to the upstream [Usage documentation](https://github.com/anoadragon453/matrix-reminder-bot#usage)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:74
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:76
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-matrix-reminder-bot`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:78
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:80
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 ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
@@ -19,149 +19,185 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bot-maubot.md:1
#: ../../../docs/configuring-playbook-bot-maubot.md:12
msgid "Setting up maubot (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:3
#: ../../../docs/configuring-playbook-bot-maubot.md:14
msgid "The playbook can install and configure [maubot](https://github.com/maubot/maubot) for you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:5
#: ../../../docs/configuring-playbook-bot-maubot.md:16
msgid "After setting up maubot, you can use the web management interface to make it do things. The default location of the management interface is `matrix.example.com/_matrix/maubot/`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:7
#: ../../../docs/configuring-playbook-bot-maubot.md:18
msgid "See the project's [documentation](https://docs.mau.fi/maubot/usage/basic.html) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:9
#: ../../../docs/configuring-playbook-bot-maubot.md:20
msgid "Adjusting DNS records (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:11
#: ../../../docs/configuring-playbook-bot-maubot.md:22
msgid "By default, this playbook installs maubot on the `matrix.` subdomain, at the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:13
#: ../../../docs/configuring-playbook-bot-maubot.md:24
msgid "If you wish to adjust it, see the section [below](#adjusting-the-maubot-url-optional) for details about DNS configuration."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:15
#: ../../../docs/configuring-playbook-bot-maubot.md:26
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:17
#: ../../../docs/configuring-playbook-bot-maubot.md:28
msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:32
#: ../../../docs/configuring-playbook-bot-maubot.md:43
msgid "You can add multiple admins. The admin accounts are only used to access the maubot administration interface."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:34
#: ../../../docs/configuring-playbook-bot-maubot.md:45
msgid "Adjusting the maubot URL (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:36
#: ../../../docs/configuring-playbook-bot-maubot.md:47
msgid "By tweaking the `matrix_bot_maubot_hostname` and `matrix_bot_maubot_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:38
#: ../../../docs/configuring-playbook-bot-maubot.md:56
#: ../../../docs/configuring-playbook-bot-maubot.md:49
#: ../../../docs/configuring-playbook-bot-maubot.md:76
msgid "Example additional configuration for your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:46
#: ../../../docs/configuring-playbook-bot-maubot.md:57
msgid "If you've changed the default hostname, you may need to create a CNAME record for the maubot domain (`maubot.example.com`), which targets `matrix.example.com`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:48
#: ../../../docs/configuring-playbook-bot-maubot.md:59
msgid "When setting, replace `example.com` with your own."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:50
msgid "Customizing the maubot container image"
#: ../../../docs/configuring-playbook-bot-maubot.md:61
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:52
msgid "Certain [maubot plugins](https://plugins.mau.bot/) require additional dependencies to be installed."
#: ../../../docs/configuring-playbook-bot-maubot.md:63
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:54
msgid "You can customize the default maubot container image and install your own dependencies."
#: ../../../docs/configuring-playbook-bot-maubot.md:65
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:67
msgid "`roles/custom/matrix-bot-maubot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:68
msgid "`roles/custom/matrix-bot-maubot/templates/config.yaml.j2` for the bot's default configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:70
msgid "Customizing the maubot container image"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:72
msgid "Certain [maubot plugins](https://plugins.mau.bot/) require additional dependencies to be installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:74
msgid "You can customize the default maubot container image and install your own dependencies."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:87
msgid "Consult the [Dockerfile reference](https://docs.docker.com/reference/dockerfile/) for more information about the syntax."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:69
#: ../../../docs/configuring-playbook-bot-maubot.md:89
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:71
#: ../../../docs/configuring-playbook-bot-maubot.md:91
msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:78
#: ../../../docs/configuring-playbook-bot-maubot.md:98
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:80
#: ../../../docs/configuring-playbook-bot-maubot.md:100
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:82
#: ../../../docs/configuring-playbook-bot-maubot.md:102
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:84
#: ../../../docs/configuring-playbook-bot-maubot.md:104
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:86
msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password."
#: ../../../docs/configuring-playbook-bot-maubot.md:106
msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:88
#: ../../../docs/configuring-playbook-bot-maubot.md:108
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:90
#: ../../../docs/configuring-playbook-bot-maubot.md:110
msgid "By default, you can visit `matrix.example.com/_matrix/maubot/` to manage your available plugins, clients and instances."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:92
#: ../../../docs/configuring-playbook-bot-maubot.md:112
msgid "You should start in the following order"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:93
#: ../../../docs/configuring-playbook-bot-maubot.md:113
msgid "**Create one or more clients**: A client is a Matrix account which the bot will use to message. By default, the playbook creates a `bot.maubot` account (as per the configuration above). You only need to [obtain an access token](#obtaining-an-access-token) for it"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:94
#: ../../../docs/configuring-playbook-bot-maubot.md:114
msgid "**Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:95
#: ../../../docs/configuring-playbook-bot-maubot.md:115
msgid "**Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:97
#: ../../../docs/configuring-playbook-bot-maubot.md:117
msgid "Obtain an access token"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:99
#: ../../../docs/configuring-playbook-bot-maubot.md:119
msgid "This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:101
#: ../../../docs/configuring-playbook-bot-maubot.md:121
msgid "Alternatively, you can refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will causes issues to your bot in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:103
#: ../../../docs/configuring-playbook-bot-maubot.md:123
msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:126
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:128
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-maubot`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:130
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:132
msgid "The default logging level for this component is `WARNING`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
@@ -19,254 +19,266 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bot-mjolnir.md:1
#: ../../../docs/configuring-playbook-bot-mjolnir.md:12
msgid "Setting up Mjolnir (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:3
#: ../../../docs/configuring-playbook-bot-mjolnir.md:14
msgid "The playbook can install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation bot for you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:5
#: ../../../docs/configuring-playbook-bot-mjolnir.md:16
msgid "See the project's [documentation](https://github.com/matrix-org/mjolnir/blob/main/README.md) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:7
#: ../../../docs/configuring-playbook-bot-mjolnir.md:18
msgid "Prerequisites"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:9
#: ../../../docs/configuring-playbook-bot-mjolnir.md:20
msgid "Register the bot account"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:11
#: ../../../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."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:13
#: ../../../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`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:15
#: ../../../docs/configuring-playbook-bot-mjolnir.md:26
msgid "You can use the playbook to [register a new user](registering-users.md):"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:21
#: ../../../docs/configuring-playbook-bot-mjolnir.md:32
msgid "If you would like Mjolnir to be able to deactivate users, move aliases, shutdown rooms, etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:23
#: ../../../docs/configuring-playbook-bot-mjolnir.md:34
msgid "Obtain an access token"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:25
#: ../../../docs/configuring-playbook-bot-mjolnir.md:36
msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:27
#: ../../../docs/configuring-playbook-bot-mjolnir.md:52
#: ../../../docs/configuring-playbook-bot-mjolnir.md:38
#: ../../../docs/configuring-playbook-bot-mjolnir.md:63
msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:30
#: ../../../docs/configuring-playbook-bot-mjolnir.md:41
msgid "Make sure the account is free from rate limiting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:32
#: ../../../docs/configuring-playbook-bot-mjolnir.md:43
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:34
#: ../../../docs/configuring-playbook-bot-mjolnir.md:45
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:36
#: ../../../docs/configuring-playbook-bot-mjolnir.md:47
msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:38
msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)."
#: ../../../docs/configuring-playbook-bot-mjolnir.md:49
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:40
#: ../../../docs/configuring-playbook-bot-mjolnir.md:51
msgid "Add the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:42
#: ../../../docs/configuring-playbook-bot-mjolnir.md:53
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:48
#: ../../../docs/configuring-playbook-bot-mjolnir.md:59
msgid "Obtain an access token for admin account"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:50
#: ../../../docs/configuring-playbook-bot-mjolnir.md:61
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:55
#: ../../../docs/configuring-playbook-bot-mjolnir.md:66
msgid "Run the `curl` command"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:57
#: ../../../docs/configuring-playbook-bot-mjolnir.md:68
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:59
#: ../../../docs/configuring-playbook-bot-mjolnir.md:70
msgid "`ADMIN_ACCESS_TOKEN_HERE` with the access token of the admin account"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:60
#: ../../../docs/configuring-playbook-bot-mjolnir.md:71
msgid "`example.com` with your base domain"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:61
#: ../../../docs/configuring-playbook-bot-mjolnir.md:72
msgid "`@bot.mjolnir:example.com` with the MXID of your Mjolnir bot user"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:67
#: ../../../docs/configuring-playbook-bot-mjolnir.md:184
#: ../../../docs/configuring-playbook-bot-mjolnir.md:78
#: ../../../docs/configuring-playbook-bot-mjolnir.md:195
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:68
#: ../../../docs/configuring-playbook-bot-mjolnir.md:79
msgid "This does not work on outdated Windows 10 as curl is not available there."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:69
#: ../../../docs/configuring-playbook-bot-mjolnir.md:80
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:71
#: ../../../docs/configuring-playbook-bot-mjolnir.md:82
msgid "Create a management room"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:73
#: ../../../docs/configuring-playbook-bot-mjolnir.md:84
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:75
#: ../../../docs/configuring-playbook-bot-mjolnir.md:86
msgid "[!WARNING] 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:78
#: ../../../docs/configuring-playbook-bot-mjolnir.md:89
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:80
#: ../../../docs/configuring-playbook-bot-mjolnir.md:91
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:82
#: ../../../docs/configuring-playbook-bot-mjolnir.md:93
msgid "Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:84
#: ../../../docs/configuring-playbook-bot-mjolnir.md:95
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:86
#: ../../../docs/configuring-playbook-bot-mjolnir.md:97
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:95
#: ../../../docs/configuring-playbook-bot-mjolnir.md:106
msgid "End-to-End Encryption support"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:97
#: ../../../docs/configuring-playbook-bot-mjolnir.md:108
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:99
#: ../../../docs/configuring-playbook-bot-mjolnir.md:110
msgid "To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:101
#: ../../../docs/configuring-playbook-bot-mjolnir.md:112
msgid "Configuration with E2EE support"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:103
#: ../../../docs/configuring-playbook-bot-mjolnir.md:114
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:105
#: ../../../docs/configuring-playbook-bot-mjolnir.md:116
msgid "Add the following configuration to your `vars.yml` file (adapt to your needs):"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:119
#: ../../../docs/configuring-playbook-bot-mjolnir.md:130
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:131
#: ../../../docs/configuring-playbook-bot-mjolnir.md:142
msgid "Configuration without E2EE support"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:133
#: ../../../docs/configuring-playbook-bot-mjolnir.md:144
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:135
#: ../../../docs/configuring-playbook-bot-mjolnir.md:146
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:141
#: ../../../docs/configuring-playbook-bot-mjolnir.md:152
msgid "Adding Mjolnir synapse antispam module (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:143
#: ../../../docs/configuring-playbook-bot-mjolnir.md:154
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:153
#: ../../../docs/configuring-playbook-bot-mjolnir.md:164
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:155
#: ../../../docs/configuring-playbook-bot-mjolnir.md:166
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:157
#: ../../../docs/configuring-playbook-bot-mjolnir.md:168
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:159
#: ../../../docs/configuring-playbook-bot-mjolnir.md:170
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:161
#: ../../../docs/configuring-playbook-bot-mjolnir.md:172
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:175
#: ../../../docs/configuring-playbook-bot-mjolnir.md:186
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:177
#: ../../../docs/configuring-playbook-bot-mjolnir.md:188
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:186
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:188
#: ../../../docs/configuring-playbook-bot-mjolnir.md:197
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:190
#: ../../../docs/configuring-playbook-bot-mjolnir.md:199
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:192
msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password."
#: ../../../docs/configuring-playbook-bot-mjolnir.md:201
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:194
#: ../../../docs/configuring-playbook-bot-mjolnir.md:203
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:196
#: ../../../docs/configuring-playbook-bot-mjolnir.md:205
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
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:209
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
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:213
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 ""
@@ -8,60 +8,60 @@ msgid ""
msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:1
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:10
msgid "Setting up Postmoogle email bridging (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:3
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:12
msgid "The playbook can install and configure [Postmoogle](https://github.com/etkecc/postmoogle) for you."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:5
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:14
msgid "Postmoogle is a bridge you can use to have its bot user forward emails to Matrix rooms. It runs an SMTP email server and allows you to assign mailbox addresses to the rooms."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:7
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:16
msgid "See the project's [documentation](https://github.com/etkecc/postmoogle/blob/master/README.md) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:9
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:18
msgid "Prerequisites"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:11
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:20
msgid "Open the following ports on your server to be able to receive incoming emails:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:13
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:22
msgid "`25/tcp`: SMTP"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:14
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:23
msgid "`587/tcp`: Submission (TLS-encrypted SMTP)"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:16
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:25
msgid "If you don't open these ports, you will still be able to send emails, but not receive any."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:18
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:27
msgid "These port numbers are configurable via the `matrix_postmoogle_smtp_host_bind_port` and `matrix_postmoogle_submission_host_bind_port` variables, but other email servers will try to deliver on these default (standard) ports, so changing them is of little use."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:20
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:29
msgid "Adjusting DNS records"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:22
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:31
msgid "To make Postmoogle enable its email sending features, you need to configure MX and TXT (SPF, DMARC, and DKIM) records. See the table below for values which need to be specified."
msgstr ""
@@ -137,90 +137,94 @@ msgstr ""
msgid "get it from `!pm dkim`"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:31
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:40
msgid "**Note**: the DKIM record can be retrieved after configuring and installing the bridge's bot."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:33
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:42
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:35
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:44
msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:56
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:65
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:58
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:67
msgid "There are some additional things you may wish to configure about the bridge."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:60
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:69
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:62
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:71
msgid "`roles/custom/matrix-bridge-postmoogle/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:64
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:73
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:66
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:75
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:73
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:82
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:75
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:84
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create a user account of the bridge's bot."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:77
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:86
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:79
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:88
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:81
msgid "If you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password."
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:90
msgid "If you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:83
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:92
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:85
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:94
msgid "To use the bridge, invite the `@postmoogle:example.com` bot user into a room you want to use as a mailbox."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:87
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:96
msgid "Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with the email address `NAME@matrix.example.com`. Emails sent to that email address will be forwarded to the room."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:89
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:98
msgid "Send `!pm help` to the bot in the room to see the available commands."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:91
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:100
msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/postmoogle)."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:93
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:102
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:95
msgid "As with all other services, you can find their logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-postmoogle`"
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:104
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-postmoogle`."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:97
msgid "The default logging level for this bridge is `INFO`, but you can increase it to `DEBUG` with the following additional configuration:"
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:106
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:108
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 ""
@@ -0,0 +1,118 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018-2026, Slavi Pantaleev, Aine Etke, MDAD community
# members
# This file is distributed under the same license as the
# matrix-docker-ansible-deploy package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2026.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
"Language-Team: bg <LL@li.org>\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-element-admin.md:8
msgid "Setting up Element Admin (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:10
msgid "The playbook can install and configure [Element Admin](https://github.com/element-hq/element-admin) for you."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:12
msgid "Element Admin is a web-based administration panel for Synapse and [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md)."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:14
msgid "See the project's [documentation](https://github.com/element-hq/element-admin) to learn more."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:16
msgid "💡 **Note**: This project is still very young and doesn't have many features. [Ketesa](./configuring-playbook-ketesa.md) is the fully-featured alternative — it covers all Synapse and MAS Admin APIs, including complete user management, session management, and MAS policy data. Element Admin remains a valid choice if you prefer its interface."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:18
msgid "Prerequisites"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:20
msgid "A [Synapse](configuring-playbook-synapse.md) homeserver with its Admin API enabled (the playbook automatically enables it for you when you enable Element Admin)"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:21
msgid "[Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) with its Admin API enabled (the playbook automatically enables it for you when you enable Element Admin)"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:23
msgid "Decide on a domain and path"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:25
msgid "By default, the Element Admin is configured to be served on the `admin.element.example.com` domain."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:27
msgid "If you'd like to run Element Admin on another hostname, see the [Adjusting the Element Admin URL](#adjusting-the-element-admin-url-optional) section below."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:29
msgid "Adjusting DNS records (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:31
msgid "By default, this playbook installs Element Admin on the `admin.element.` subdomain (`admin.element.example.com`) and requires you to create a `CNAME` record for `admin.element`, which targets `matrix.example.com`."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:33
msgid "When setting these values, replace `example.com` with your own."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:35
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:37
msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:43
msgid "Adjusting the Element Admin URL (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:45
msgid "By tweaking the `matrix_element_admin_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:47
msgid "Example additional configuration for your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:53
msgid "[!WARNING] A `matrix_element_admin_path_prefix` variable is also available and mean to let you configure a path prefix for the Element Admin service, but **Element Admin does not support running under a sub-path yet**."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:56
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:58
msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:65
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:67
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgstr ""
@@ -0,0 +1,166 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018-2026, Slavi Pantaleev, Aine Etke, MDAD community
# members
# This file is distributed under the same license as the
# matrix-docker-ansible-deploy package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2026.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-04-03 12:02+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
"Language-Team: bg <LL@li.org>\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-ketesa.md:14
msgid "Setting up Ketesa (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:16
msgid "The playbook can install and configure [Ketesa](https://github.com/etkecc/ketesa) for you."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:18
msgid "Ketesa is a fully-featured admin interface for Matrix homeservers — manage users, rooms, media, sessions, and more from one clean, responsive web UI. It is the evolution of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin): what began as a fork has grown into its own independent project with a redesigned interface, comprehensive Synapse and MAS API coverage, and multi-language support."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:20
msgid "[!NOTE]"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:22
msgid "Ketesa does not work with other homeserver implementations than Synapse due to API's incompatibility."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:23
msgid "The latest version of Ketesa is hosted by [etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). If you only need this service occasionally and trust giving your admin credentials to a 3rd party Single Page Application, you can consider using it from there and avoiding the (small) overhead of self-hosting."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:24
msgid "This playbook also supports an alternative management UI in the shape of [Element Admin](./configuring-playbook-element-admin.md). Please note that it's currently less feature-rich than Ketesa and requires [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md)."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:26
msgid "Adjusting DNS records (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:28
msgid "By default, this playbook installs Ketesa on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin) — the legacy path is kept for backward compatibility. This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:30
msgid "If you wish to adjust it, see the section [below](#adjusting-the-ketesa-url-optional) for details about DNS configuration."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:32
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:34
msgid "To enable Ketesa, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:40
msgid "**Note**: Ketesa requires Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to function. Access to them is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, for additional security, we normally leave them unexposed, following [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). Because Ketesa needs these APIs to function, when installing Ketesa, the playbook **automatically** exposes the Synapse Admin API publicly for you. Depending on the homeserver implementation you're using (Synapse, Dendrite), this is equivalent to:"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:42
msgid "for [Synapse](./configuring-playbook-synapse.md) (our default homeserver implementation): `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true`"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:43
msgid "for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true`"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:45
msgid "By default, Ketesa installation will be [restricted to only work with one homeserver](https://github.com/etkecc/ketesa/blob/main/README.md#restricting-available-homeserver) — the one managed by the playbook. To adjust these restrictions, tweak the `matrix_ketesa_config_restrictBaseUrl` variable."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:47
msgid "Adjusting the Ketesa URL (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:49
msgid "By tweaking the `matrix_ketesa_hostname` and `matrix_ketesa_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:51
msgid "We recommend updating the path prefix to `/ketesa` to align with the new branding, while the default `/synapse-admin` is kept for backward compatibility:"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:57
msgid "Or to change the hostname entirely:"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:65
msgid "If you've changed the default hostname, you may need to create a CNAME record for the Ketesa domain (`admin.example.com`), which targets `matrix.example.com`."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:67
msgid "When setting, replace `example.com` with your own."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:69
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:71
msgid "There are some additional things you may wish to configure about the component."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:73
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:75
msgid "`roles/custom/matrix-ketesa/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_ketesa_configuration_extension_json` variable"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:77
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:79
msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:86
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:88
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:90
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:92
msgid "After installation, Ketesa will be accessible at: `https://matrix.example.com/synapse-admin/` (or `/ketesa/` if you updated the path prefix as recommended)"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:94
msgid "To use Ketesa, you need to have [registered at least one administrator account](registering-users.md) on your server."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:96
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:98
msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-ketesa`."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:100
msgid "If you have questions, you can join this community room and feel free to ask: [#ketesa:etke.cc](https://matrix.to/#/#ketesa:etke.cc)"
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
@@ -19,150 +19,134 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:1
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:8
msgid "Setting up Matrix Authentication Service (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:3
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:10
msgid "The playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) — a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:5
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:12
msgid "Matrix Authentication Service is an implementation of [MSC3861: Next-generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:7
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:14
msgid "**Before going through with starting to use Matrix Authentication Service**, make sure to read:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:9
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:16
msgid "the [Reasons to use Matrix Authentication Service](#reasons-to-use-matrix-authentication-service) section below"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:10
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:17
msgid "the [Expectations](#expectations) section below"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:11
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:18
msgid "the [FAQ section on areweoidcyet.com](https://areweoidcyet.com/#faqs)"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:13
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:20
msgid "**If you've already been using Synapse** and have user accounts in its database, you can [migrate to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:15
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:22
msgid "Reasons to use Matrix Authentication Service"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:17
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:24
msgid "You may be wondering whether you should make the switch to Matrix Authentication Service (MAS) or keep using your existing authentication flow via Synapse (password-based or [OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)-enabled)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:19
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:26
msgid "Matrix Authentication Service is **still an experimental service** and **not a default** for this Ansible playbook."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:21
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:28
msgid "The [Expectations](#expectations) section contains a list of what works and what doesn't (**some services don't work with MAS yet**), as well as the **relative irreversability** of the migration process."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:23
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:30
msgid "Below, we'll try to **highlight some potential reasons for switching** to Matrix Authentication Service:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:25
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:32
msgid "To use SSO in [Element X](https://element.io/blog/element-x-ignition/). The old [Synapse OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) login flow is only supported in old Element clients and will not be supported in Element X. Element X will only support the new SSO-based login flow provided by MAS, so if you want to use SSO with Element X, you will need to switch to MAS."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:27
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:34
msgid "To help drive adoption of the \"Next-generation auth for Matrix\" by switching to what's ultimately coming anyway"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:29
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:36
msgid "To help discover (and potentially fix) MAS integration issues with this Ansible playbook"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:31
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:38
msgid "To help discover (and potentially fix) MAS integration issues with various other Matrix components (bridges, bots, clients, etc.)"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:33
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:40
msgid "To reap some of the security benefits that Matrix Authentication Service offers, as outlined in the [Better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/) article."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:35
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:42
msgid "Prerequisites"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:37
msgid "⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet."
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:44
msgid "⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating with Matrix Authentication Service yet."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:39
msgid "⚠️ **email sending** configured (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:41
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:46
msgid "❌ **disabling all password providers** for Synapse (things like [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc.) More details about this are available in the [Expectations](#expectations) section below."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:43
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:48
msgid "Expectations"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:45
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:50
msgid "This section details what you can expect when switching to the Matrix Authentication Service (MAS)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:47
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:52
msgid "❌ **Synapse password providers will need to be disabled**. You can no longer use [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc. When the authentication flow is handled by MAS (not by Synapse anymore), it doesn't make sense to extend the Synapse authentication flow with additional modules. Many bridges used to rely on shared-secret-auth for doing double-puppeting (impersonating other users), but most (at least the mautrix bridges) nowadays use [Appservice Double Puppet](./configuring-playbook-appservice-double-puppet.md) as a better alternative. Older/maintained bridges may still rely on shared-secret-auth, as do other services like [matrix-corporal](./configuring-playbook-matrix-corporal.md)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:49
msgid "❌ Certain **tools like [synapse-admin](./configuring-playbook-synapse-admin.md) do not have full compatibility with MAS yet**. synapse-admin already supports [login with access token](https://github.com/etkecc/synapse-admin/pull/58), browsing users (which Synapse will internally fetch from MAS) and updating user avatars. However, editing users (passwords, etc.) now needs to happen directly against MAS using the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html), which synapse-admin cannot interact with yet."
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:54
msgid "✅ **[Ketesa](./configuring-playbook-ketesa.md) has full MAS integration**. Ketesa supports OIDC auth, user management, all session types (browser, OAuth2, compatibility), linked email addresses, upstream OAuth provider links, MAS policy data, and user creation through MAS. It is the recommended tool for managing homeservers running MAS."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:51
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:56
msgid "❌ **Some services experience issues when authenticating via MAS**:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:53
msgid "[Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first time around, but it consistently fails after restarting:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:55
msgid "cannot initialize matrix bot error=\"olm account is marked as shared, keys seem to have disappeared from the server\""
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:57
msgid "[matrix-reminder-bot](./configuring-playbook-bot-matrix-reminder-bot.md) fails to start (see [element-hq/matrix-authentication-service#3439](https://github.com/element-hq/matrix-authentication-service/issues/3439))"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:58
msgid "Other services may be similarly affected. This list is not exhaustive."
msgid "[Reminder bot](configuring-playbook-bot-matrix-reminder-bot.md) seems to be losing some of its state on each restart and may reschedule old reminders once again"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:60
msgid "❌ **Encrypted appservices** do not work yet (related to [MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) and [PR 17705 for Synapse](https://github.com/element-hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will fail to start (see [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3658) for Hookshot). You can use these bridges/bots only if you **keep end-to-bridge encryption disabled** (which is the default setting)."
msgid "[Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first time around, but it consistently fails after restarting:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:62
msgid "⚠️ **You will need to have email sending configured** (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working."
msgid "cannot initialize matrix bot error=\"olm account is marked as shared, keys seem to have disappeared from the server\""
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:64
msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
msgid "❌ **Encrypted appservices** do not work yet (related to [MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) and [PR 17705 for Synapse](https://github.com/element-hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will fail to start (see [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3658) for Hookshot). You can use these bridges/bots only if you **keep end-to-bridge encryption disabled** (which is the default setting)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:66
msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) does not currently seem to preserve the \"admin\" flag for users (as found in the Synapse database). All users are imported as non-admin — see [element-hq/matrix-authentication-service#3440](https://github.com/element-hq/matrix-authentication-service/issues/3440). You may need update the Matrix Authentication Service's database manually and adjust the `can_request_admin` column in the `users` table to `true` for users that need to be administrators (e.g. `UPDATE users SET can_request_admin = true WHERE username = 'someone';`)"
msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:68
msgid "⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependant on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch."
msgid "⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependent on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:70
@@ -182,7 +166,7 @@ msgid "✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), [El
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:78
msgid "✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work. Going through the old login flow does not require users to have a verified email address, as [is the case](https://github.com/element-hq/matrix-authentication-service/issues/1505) for the new SSO-based login flow."
msgid "✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:80
@@ -210,7 +194,7 @@ msgid "Existing homeserver"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:92
msgid "Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet."
msgid "Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating with Matrix Authentication Service yet."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:94
@@ -298,326 +282,346 @@ msgstr ""
msgid "The playbook exposes a `matrix_authentication_service_config_upstream_oauth2_providers` variable for controlling this setting."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:269
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:273
msgid "💡 Refer to the [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers) for the most up-to-date schema and example for providers. The value shown above here may be out of date."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:271
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:275
msgid "⚠️ The syntax for existing [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) is slightly different, so you will need to adjust your configuration when switching from Synapse OIDC to MAS upstream OAuth2."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:273
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:277
msgid "⚠️ When [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) which contains OIDC-sourced users, you will need to:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:275
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:279
msgid "[Configure upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:276
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:280
msgid "go through the [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) process"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:277
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:281
msgid "remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:279
msgid "Installing"
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:283
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:281
msgid "Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below:"
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:285
msgid "There are some additional things you may wish to configure about the component."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:288
msgid "**Notes**:"
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:287
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:289
msgid "`roles/custom/matrix-authentication-service/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:290
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgid "`roles/custom/matrix-authentication-service/templates/config.yaml.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_authentication_service_configuration_extension_yaml` variable"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:292
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:294
msgid "Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:301
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:303
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:305
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:307
msgid "If you're in the process of migrating an existing Synapse homeserver to MAS, you should now follow the rest of the steps in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) guide."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:296
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:309
msgid "💡 After installation, you should [verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:298
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:311
msgid "Migrating an existing Synapse homeserver to Matrix Authentication Service"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:300
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:313
msgid "Our migration guide is loosely based on the upstream [Migrating an existing homeserver](https://element-hq.github.io/matrix-authentication-service/setup/migration.html) guide."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:302
msgid "Migration is done via a tool called `syn2mas`, which the playbook could run for you (in a container)."
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:315
msgid "Migration is done via a sub-command called `syn2mas`, which the playbook could run for you (in a container)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:304
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:317
msgid "The installation + migration steps are like this:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:306
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:319
msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) to **disable the integration between the homeserver and MAS**. This is done by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:308
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:321
msgid "Perform the initial [installation](#installing). At this point:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:310
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:323
msgid "Matrix Authentication Service will be installed. Its database will be empty, so it cannot validate existing access tokens or authentication users yet."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:312
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:325
msgid "The homeserver will still continue to use its local database for validating existing access tokens."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:314
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:327
msgid "Various [compatibility layer URLs](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) are not yet installed. New login sessions will still be forwarded to the homeserver, which is capable of completing them."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:316
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:329
msgid "The `matrix-user-creator` role would be suppressed, so that it doesn't automatically attempt to create users (for bots, etc.) in the MAS database. These user accounts likely already exist in Synapse's user database and could be migrated over (via syn2mas, as per the steps below), so creating them in the MAS database would have been unnecessary and potentially problematic (conflicts during the syn2mas migration)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:318
msgid "Consider taking a full [backup of your Postgres database](./maintenance-postgres.md#backing-up-postgresql). This is done just in case. The **syn2mas migration tool does not delete any data**, so it should be possible to revert to your previous setup by merely disabling MAS and re-running the playbook (no need to restore a Postgres backup). However, do note that as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:331
msgid "Consider taking a full [backup of your Postgres database](./maintenance-postgres.md#backing-up-postgresql). This is done just in case. The **syn2mas migration command does not delete any data**, so it should be possible to revert to your previous setup by merely disabling MAS and re-running the playbook (no need to restore a Postgres backup). However, do note that as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:320
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:333
msgid "[Migrate your data from Synapse to Matrix Authentication Service using syn2mas](#migrate-your-data-from-synapse-to-matrix-authentication-service-using-syn2mas)"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:322
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:335
msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) again, to:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:324
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:337
msgid "remove the `matrix_authentication_service_migration_in_progress: false` line"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:326
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:339
msgid "if you had been using [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:328
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:341
msgid "Perform the [installation](#installing) again. At this point:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:330
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:343
msgid "The homeserver will start delegating authentication to MAS."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:332
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:345
msgid "The compatibility layer URLs will be installed. New login sessions will be completed by MAS."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:334
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:347
msgid "[Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:336
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:349
msgid "Migrate your data from Synapse to Matrix Authentication Service using syn2mas"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:338
msgid "We **don't** ask you to [run the `syn2mas` migration advisor command](https://element-hq.github.io/matrix-authentication-service/setup/migration.html#run-the-migration-advisor), because it only gives you the green light if your Synapse configuration (`homeserver.yaml`) is configured in a way that's compatible with MAS (delegating authentication to MAS; disabling Synapse's password config; etc.). Until we migrate your data with the `syn2mas` tool, we intentionally avoid doing these changes to allow existing user sessions to work."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:340
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:351
msgid "You can invoke the `syn2mas` tool via the playbook by running the playbook's `matrix-authentication-service-mas-cli-syn2mas` tag. We recommend first doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:342
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:353
msgid "Configuring syn2mas"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:344
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:355
msgid "If you're using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to [Configuring upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:346
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:357
msgid "If you only have local (non-OIDC) users in your Synapse database, you can likely run `syn2mas` as-is (without doing additional configuration changes)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:348
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:359
msgid "When you're done with potentially configuring `syn2mas`, proceed to doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:350
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:361
msgid "Configuring upstream OIDC provider mapping for syn2mas"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:352
msgid "If you have existing OIDC users in your Synapse user database (which will be the case if when using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)), you may need to pass an additional `--upstreamProviderMapping` argument to the `syn2mas` tool to tell it which provider (on the Synapse side) maps to which other provider on the MAS side."
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:363
msgid "Since Matrix Authentication Service v0.16.0 (which replaced the standalone `syn2mas` tool with a `mas-cli syn2mas` sub-command), OIDC configuration (mapping from your old OIDC configuration to your new one, etc) is meant to be configured in the Matrix Authentication Service configuration (via `matrix_authentication_service_config_upstream_oauth2_providers`) as a `synapse_idp_id` property for each provider."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:354
msgid "If you don't do this, `syn2mas` would report errors like this one:"
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:365
msgid "You can refer to the [Map any upstream SSO providers](https://element-hq.github.io/matrix-authentication-service/setup/migration.html#map-any-upstream-sso-providers) section of the MAS documentation for figuring out how to set the `synapse_idp_id` value in `matrix_authentication_service_config_upstream_oauth2_providers` correctly."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:356
msgid "[FATAL] migrate - [Failed to import external id 4264b0f0-4f11-4ddd-aedb-b500e4d07c25 with oidc-keycloak for user @alice:example.com: Error: Unknown upstream provider oidc-keycloak]"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:358
msgid "Below is an example situation and a guide for how to solve it."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:360
msgid "If in `matrix_synapse_oidc_providers` your provider `idp_id` is (was) named `keycloak`, in the Synapse database users would be associated with the `oidc-keycloak` provider (note the `oidc-` prefix that was added automatically by Synapse to your `idp_id` value)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:362
msgid "The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` on the MAS side, as defined in `matrix_authentication_service_config_upstream_oauth2_providers` (see the [Upstream OAuth2 configuration](#upstream-oauth2-configuration) section above)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:364
msgid "To tell `syn2mas` how the Synapse-configured OIDC provider maps to the new MAS-configured OIDC provider, add this additional configuration to your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:373
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:367
msgid "Performing a syn2mas dry-run"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:375
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:369
msgid "Having [configured syn2mas](#configuring-syn2mas), we recommend doing a [dry-run](https://en.wikipedia.org/wiki/Dry_run_(testing)) first to verify that everything will work out as expected."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:377
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:371
msgid "A dry-run would not cause downtime, because it avoids stopping Synapse."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:379
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:373
msgid "To perform a dry-run, run:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:385
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:379
msgid "Observe the command output (especially the last line of the the syn2mas output). If you are confident that the migration will work out as expected, you can proceed with a [real migration](#performing-a-real-syn2mas-migration)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:387
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:381
msgid "Performing a real syn2mas migration"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:389
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:383
msgid "Before performing a real migration make sure:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:391
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:385
msgid "you've familiarized yourself with the [expectations](#expectations)"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:393
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:387
msgid "you've performed a Postgres backup, just in case"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:395
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:389
msgid "you're aware of the irreversibility of the migration process without disruption after users have created new login sessions via the new MAS setup"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:397
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:391
msgid "you've [configured syn2mas](#configuring-syn2mas), especially if you've used [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:399
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:393
msgid "you've performed a [syn2mas dry-run](#performing-a-syn2mas-dry-run) and don't see any issues in its output"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:401
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:395
msgid "To perform a real migration, run the `matrix-authentication-service-mas-cli-syn2mas` tag **without** the `matrix_authentication_service_syn2mas_migrate_dry_run` variable:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:407
msgid "Having performed a `syn2mas` migration once, trying to do it again will report errors for users that were already migrated (e.g. \"Error: Unknown upstream provider oauth-delegated\")."
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:401
msgid "After `syn2mas` completes, Synapse will intentionally remain stopped to avoid new registrations or other authentication changes from being accepted before the migration is completed. Continue with the next steps in this guide before re-running the installation."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:409
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:403
msgid "Having performed a `syn2mas` migration once, trying to do it again will report errors (e.g. \"Error: The MAS database is not empty: rows found in at least `users`. Please drop and recreate the database, then try again.\")."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:405
msgid "Verify that Matrix Authentication Service is installed correctly"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:411
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:407
msgid "After [installation](#installing), run the `doctor` subcommand of the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) to verify that MAS is installed correctly."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:413
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:409
msgid "You can do it:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:415
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:411
msgid "either via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag: `just run-tags matrix-authentication-service-mas-cli-doctor`"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:417
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:413
msgid "or by running the `mas-cli` script on the server (which invokes the `mas-cli` tool inside a container): `/matrix/matrix-authentication-service/bin/mas-cli doctor`"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:419
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:415
msgid "If successful, you should see some output that looks like this:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:431
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:427
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:429
msgid "Management"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:433
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:431
msgid "You can use the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) (exposed via the `/matrix/matrix-authentication-service/bin/mas-cli` script) to perform administrative tasks against MAS."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:435
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:433
msgid "This documentation page already mentions:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:437
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:435
msgid "the `mas-cli doctor` sub-command in the [Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly) section, which you can run via the CLI and via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:439
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:437
msgid "the `mas-cli manage register-user` sub-command in the [Registering users](./registering-users.md) documentation"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:441
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:439
msgid "There are other sub-commands available. Run `/matrix/matrix-authentication-service/bin/mas-cli` to get an overview."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:443
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:441
msgid "User registration"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:445
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:443
msgid "After Matrix Authentication Service is [installed](#installing), users need to be managed there (unless you're managing them in an [upstream OAuth2 provider](#upstream-oauth2-configuration))."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:447
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:445
msgid "You can register users new users as described in the [Registering users](./registering-users.md) documentation (via `mas-cli manage register-user` or the Ansible playbook's `register-user` tag)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:449
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:447
msgid "Working around email deliverability issues"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:449
msgid "Matrix Authentication Service only sends emails when:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:451
msgid "Because Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user, you may need to work around email deliverability issues if [your email-sending configuration](./configuring-playbook-email.md) is not working."
msgid "it verifies email addresses for users who are self-registering with a password"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:453
msgid "Matrix Authentication Service attempts to verify email addresses by sending a verification email to the address specified by the user whenever they log in to an account without a verified email address."
msgid "a user tries to add an email to their account"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:455
msgid "If email delivery is not working, **you can retrieve the email configuration code from the Matrix Authentication Service's logs** (`journalctl -fu matrix-authentication-service`)."
msgid "If Matrix Authentication Service tries to send an email and it fails because [your email-sending configuration](./configuring-playbook-email.md) is not working, you may need to work around email deliverability."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:457
msgid "If email delivery is not working, **you can retrieve the email verification code from the Matrix Authentication Service's logs** (`journalctl -fu matrix-authentication-service`)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:459
msgid "Alternatively, you can use the [`mas-cli` management tool](#management) to manually verify email addresses for users. Example: `/matrix/matrix-authentication-service/bin/mas-cli manage verify-email some.username email@example.com`"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:461
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:463
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-authentication-service`."
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
@@ -19,261 +19,305 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-synapse.md:1
#: ../../../docs/configuring-playbook-synapse.md:12
msgid "Configuring Synapse (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:3
#: ../../../docs/configuring-playbook-synapse.md:14
msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, so that it works for the general case. If that's okay, you can skip this document."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:5
#: ../../../docs/configuring-playbook-synapse.md:16
msgid "💡 See this page for details about maintaining Synapse: [Synapse maintenance](maintenance-synapse.md)"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:18
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:7
#: ../../../docs/configuring-playbook-synapse.md:20
msgid "Load balancing with workers"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:9
#: ../../../docs/configuring-playbook-synapse.md:22
msgid "To have Synapse gracefully handle thousands of users, worker support should be enabled. It factors out some homeserver tasks and spreads the load of incoming client and server-to-server traffic between multiple processes. More information can be found in the [official Synapse workers documentation](https://github.com/element-hq/synapse/blob/master/docs/workers.md) and [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:11
#: ../../../docs/configuring-playbook-synapse.md:24
msgid "To enable Synapse worker support, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:19
#: ../../../docs/configuring-playbook-synapse.md:32
msgid "By default, this enables the `one-of-each` [worker preset](#worker-presets), but you may wish to use another preset or [control the number of worker instances](#controlling-the-number-of-worker-instances)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:21
#: ../../../docs/configuring-playbook-synapse.md:34
msgid "Worker presets"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:23
#: ../../../docs/configuring-playbook-synapse.md:36
msgid "We support a few configuration presets (`matrix_synapse_workers_preset: one-of-each` being the default configuration right now):"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:25
#: ../../../docs/configuring-playbook-synapse.md:38
msgid "(federation-only) `little-federation-helper` — a very minimal worker configuration to improve federation performance"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:26
#: ../../../docs/configuring-playbook-synapse.md:39
msgid "(generic) `one-of-each` — defaults to one worker of each supported type — no smart routing, just generic workers"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:27
#: ../../../docs/configuring-playbook-synapse.md:40
msgid "(specialized) `specialized-workers` — defaults to one worker of each supported type, but disables generic workers and uses [specialized workers](#specialized-workers) instead"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:29
#: ../../../docs/configuring-playbook-synapse.md:42
msgid "These presets represent a few common configurations. There are many worker types which can be mixed and matched based on your needs."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:31
#: ../../../docs/configuring-playbook-synapse.md:44
msgid "Generic workers"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:33
#: ../../../docs/configuring-playbook-synapse.md:46
msgid "Previously, the playbook only supported the most basic type of load-balancing. We call it **generic load-balancing** below, because incoming HTTP requests are sent to a generic worker. Load-balancing was done based on the requestor's IP address. This is simple, but not necessarily optimal. If you're accessing your account from multiple IP addresses (e.g. your mobile phone being on a different network than your PC), these separate requests may potentially be routed to different workers, each of which would need to cache roughly the same data."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:35
#: ../../../docs/configuring-playbook-synapse.md:48
msgid "This is **still the default load-balancing method (preset) used by the playbook**."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:37
#: ../../../docs/configuring-playbook-synapse.md:50
msgid "To use generic load-balancing, do not specify `matrix_synapse_workers_preset` to make it use the default value (`one-of-each`), or better yet — explicitly set it as `one-of-each`."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:39
#: ../../../docs/configuring-playbook-synapse.md:52
msgid "You may also consider [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:41
#: ../../../docs/configuring-playbook-synapse.md:54
msgid "Specialized workers"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:43
msgid "The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requestor's IP adddress, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** — the access token (username) of the requestor and/or on the resource (room, etc.) being requested."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:45
msgid "The playbook supports these **4 types** of specialized workers:"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:47
msgid "Room workers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) & [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs dedicated to handling specific rooms"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:48
msgid "Sync workers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to synchronization (most notably [the `/sync` endpoint](https://spec.matrix.org/v1.9/client-server-api/#get_matrixclientv3sync))"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:49
msgid "Client readers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are not for specific rooms (handled by **room workers**) or for synchronization (handled by **sync workers**)"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:50
msgid "Federation readers — handles various [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which are not for specific rooms (handled by **room workers**)"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:52
msgid "To use specialized load-balancing, consider enabling the `specialized-workers` [worker preset](#worker-presets) and potentially [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:54
msgid "Controlling the number of worker instances"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:56
msgid "If you'd like more customization power, you can start with one of the [worker presets](#worker-presets) and then tweak various `matrix_synapse_workers_*_count` variables manually."
msgid "The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requester's IP address, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** — the access token (username) of the requester and/or on the resource (room, etc.) being requested."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:58
msgid "To find what variables are available for you to override in your own `vars.yml` configuration file, see the [`defaults/main.yml` file for the `matrix-synapse` Ansible role](../roles/custom/matrix-synapse/defaults/main.yml)."
msgid "The playbook supports these **4 types** of specialized workers:"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:60
msgid "The only thing you **cannot** do is mix [generic workers](#generic-workers) and [specialized workers](#specialized-workers)."
msgid "Room workers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) & [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs dedicated to handling specific rooms"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:61
msgid "Sync workers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to synchronization (most notably [the `/sync` endpoint](https://spec.matrix.org/v1.9/client-server-api/#get_matrixclientv3sync))"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:62
msgid "Client readers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are not for specific rooms (handled by **room workers**) or for synchronization (handled by **sync workers**)"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:63
msgid "Federation readers — handles various [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which are not for specific rooms (handled by **room workers**)"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:65
msgid "To use specialized load-balancing, consider enabling the `specialized-workers` [worker preset](#worker-presets) and potentially [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:67
msgid "Controlling the number of worker instances"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:69
msgid "If you'd like more customization power, you can start with one of the [worker presets](#worker-presets) and then tweak various `matrix_synapse_workers_*_count` variables manually."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:71
msgid "To find what variables are available for you to override in your own `vars.yml` configuration file, see the [`defaults/main.yml` file for the `matrix-synapse` Ansible role](../roles/custom/matrix-synapse/defaults/main.yml)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:73
msgid "The only thing you **cannot** do is mix [generic workers](#generic-workers) and [specialized workers](#specialized-workers)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:75
msgid "Effect of enabling workers on the rest of your server"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:64
#: ../../../docs/configuring-playbook-synapse.md:77
msgid "When Synapse workers are enabled, the integrated [Postgres database is tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum number of Postgres connections are increased from `200` to `500`. If you need to decrease or increase the number of maximum Postgres connections further, use the `postgres_max_connections` variable."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:66
msgid "A separate Ansible role (`matrix-synapse-reverse-proxy-companion`) and component handles load-balancing for workers. This role/component is automatically enabled when you enable workers. Make sure to use the `setup-all` tag (not `install-all`!) during the playbook's [installation](./installing.md) process, especially if you're disabling workers, so that components may be installed/uninstalled correctly."
#: ../../../docs/configuring-playbook-synapse.md:79
msgid "The `matrix-synapse` role also manages the `matrix-synapse-reverse-proxy-companion` component for load-balancing with workers. This component is automatically enabled when you enable workers. Make sure to use the `setup-all` tag (not `install-all`!) during the playbook's [installation](./installing.md) process, especially if you're disabling workers, so that components may be installed/uninstalled correctly."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:68
#: ../../../docs/configuring-playbook-synapse.md:81
msgid "In case any problems occur, make sure to have a look at the [list of synapse issues about workers](https://github.com/element-hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit 'matrix-*'`."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:70
#: ../../../docs/configuring-playbook-synapse.md:83
msgid "Limit joining heavy rooms on constrained hosts"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:85
msgid "If your server is underpowered, joining heavy rooms can cause Synapse to consume a lot of resources and be unavailable for long (while it catches up)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:87
msgid "To avoid this, Synapse can be configured to reject joins for remote rooms that are too complex before users enter them."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:89
msgid "Complexity is computed as `current_state_events / 500` (Synapse state event count for current room state). When the resulting value is higher than `matrix_synapse_limit_remote_rooms_complexity` and `matrix_synapse_limit_remote_rooms_enabled` is `true`, Synapse blocks joining the room."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:91
msgid "We recommend using this as a guardrail on low-resource servers:"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:106
msgid "Synapse + OpenID Connect for Single-Sign-On"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:72
#: ../../../docs/configuring-playbook-synapse.md:108
msgid "💡 An alternative to setting up OIDC in Synapse is to use [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS). Newer clients (like Element X) only support SSO-based authentication via MAS and not via the legacy Synapse OIDC setup described below. That said, MAS is still a new experimental service which comes with its own downsides. Consult its documentation to learn if it will be a good fit for your deployment."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:74
#: ../../../docs/configuring-playbook-synapse.md:110
msgid "If you'd like to use OpenID Connect authentication with Synapse, you'll need some additional configuration."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:76
#: ../../../docs/configuring-playbook-synapse.md:112
msgid "This example configuration is for [keycloak](https://www.keycloak.org/), an opensource Identity Provider maintained by Red Hat."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:78
#: ../../../docs/configuring-playbook-synapse.md:114
msgid "For more detailed documentation on available options and how to setup keycloak, see the [Synapse documentation on OpenID Connect with keycloak](https://github.com/element-hq/synapse/blob/develop/docs/openid.md#keycloak)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:80
#, python-format
#: ../../../docs/configuring-playbook-synapse.md:116
#, python-format, python-brace-format
msgid "In case you encounter errors regarding the parsing of the variables, you can try to add `{% raw %}` and `{% endraw %}` blocks around them. For example ;"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:101
#: ../../../docs/configuring-playbook-synapse.md:137
msgid "Customizing templates"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:103
#: ../../../docs/configuring-playbook-synapse.md:139
msgid "[Templates](https://github.com/element-hq/synapse/blob/develop/docs/templates.md) are used by Synapse for showing **certain web pages** handled by the server, as well as for **email notifications**."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:105
#: ../../../docs/configuring-playbook-synapse.md:141
msgid "This playbook allows you to customize the default templates (see the [`synapse/res/templates` directory](https://github.com/element-hq/synapse/tree/develop/synapse/res/templates))."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:107
#: ../../../docs/configuring-playbook-synapse.md:143
msgid "If template customization is enabled, the playbook will build a custom container image based on the official one."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:109
#: ../../../docs/configuring-playbook-synapse.md:145
msgid "Your custom templates need to live in a public or private git repository. This repository will be cloned during Synapse image customization (during the playbook run)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:111
#: ../../../docs/configuring-playbook-synapse.md:147
msgid "To enable template customizations, add the following configuration to your `vars.yml` file (adapt to your needs):"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:137
#: ../../../docs/configuring-playbook-synapse.md:173
msgid "As mentioned in Synapse's Templates documentation, Synapse will fall back to its own templates if a template is not found in that directory. Due to this, it's recommended to only store and maintain template files in your repository if you need to make custom changes. Other files (which you don't need to change), should not be duplicated, so that you don't need to worry about getting out-of-sync with the original Synapse templates."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:139
#: ../../../docs/configuring-playbook-synapse.md:175
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:141
#: ../../../docs/configuring-playbook-synapse.md:177
msgid "There are some additional things you may wish to configure about the server."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:143
#: ../../../docs/configuring-playbook-synapse.md:179
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:145
#: ../../../docs/configuring-playbook-synapse.md:181
msgid "`roles/custom/matrix-synapse/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:146
#: ../../../docs/configuring-playbook-synapse.md:182
msgid "`roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2` for the server's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_synapse_configuration_extension_yaml` variable"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:148
#: ../../../docs/configuring-playbook-synapse.md:184
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:150
#: ../../../docs/configuring-playbook-synapse.md:186
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:157
#: ../../../docs/configuring-playbook-synapse.md:193
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:159
#: ../../../docs/configuring-playbook-synapse.md:195
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:161
#: ../../../docs/configuring-playbook-synapse.md:197
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:163
msgid "Synapse Admin"
#: ../../../docs/configuring-playbook-synapse.md:199
msgid "Ketesa"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:165
msgid "With [Synapse Admin](configuring-playbook-synapse-admin.md), certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace."
#: ../../../docs/configuring-playbook-synapse.md:201
msgid "[Ketesa](configuring-playbook-ketesa.md) is a fully-featured web UI for administrating your homeserver — managing users, rooms, media, sessions, and more."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:167
msgid "The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)."
#: ../../../docs/configuring-playbook-synapse.md:203
msgid "The playbook can install and configure Ketesa for you. For details about it, see [this page](configuring-playbook-ketesa.md)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:169
#: ../../../docs/configuring-playbook-synapse.md:205
msgid "Monitoring Synapse Metrics with Prometheus and Grafana"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:171
#: ../../../docs/configuring-playbook-synapse.md:207
msgid "This playbook allows you to enable Synapse metrics, which can provide insight into the performance and activity of Synapse."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:173
msgid "To enable Synapse runtime metrics see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)"
#: ../../../docs/configuring-playbook-synapse.md:209
msgid "To enable Synapse runtime metrics, see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md) and [its subsection](configuring-playbook-prometheus-grafana.md#expose-metrics-of-other-services-roles)"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:175
#: ../../../docs/configuring-playbook-synapse.md:211
msgid "To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:213
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:215
msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-synapse`."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:217
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:219
msgid "Because Synapse is originally very chatty when it comes to logging, we intentionally reduce its [logging level](https://docs.python.org/3/library/logging.html#logging-levels) from `INFO` to `WARNING`."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:221
msgid "If you'd like to debug an issue or [report a Synapse bug](https://github.com/element-hq/synapse/issues/new/choose) to the developers, it'd be better if you temporarily increase the logging verbosity to `INFO`. To do so, add the following configuration to your `vars.yml` file and re-run the playbook:"
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
@@ -19,528 +19,568 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook.md:1
#: ../../../docs/configuring-playbook.md:17
msgid "Configuring the playbook"
msgstr ""
#: ../../../docs/configuring-playbook.md:3
msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md)</sup>"
msgstr ""
#: ../../../docs/configuring-playbook.md:5
msgid "If you've configured your DNS records and retrieved the playbook's source code to your computer, you can start configuring the playbook. To do so, follow these steps inside the playbook directory:"
msgstr ""
#: ../../../docs/configuring-playbook.md:7
msgid "create a directory to hold your configuration (`mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\")"
msgstr ""
#: ../../../docs/configuring-playbook.md:9
msgid "copy the sample configuration file (`cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`)"
msgstr ""
#: ../../../docs/configuring-playbook.md:11
msgid "edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You may also take a look at the various `roles/*/ROLE_NAME_HERE/defaults/main.yml` files and see if there's something you'd like to copy over and override in your `vars.yml` configuration file."
msgstr ""
#: ../../../docs/configuring-playbook.md:13
msgid "copy the sample inventory hosts file (`cp examples/hosts inventory/hosts`)"
msgstr ""
#: ../../../docs/configuring-playbook.md:15
msgid "edit the inventory hosts file (`inventory/hosts`) to your liking"
msgstr ""
#: ../../../docs/configuring-playbook.md:17
msgid "(optional, advanced) you may wish to keep your `inventory` directory under version control with [git](https://git-scm.com/) or any other version-control system."
msgstr ""
#: ../../../docs/configuring-playbook.md:19
msgid "(optional, advanced) to run Ansible against multiple servers with different `sudo` credentials, you can copy the sample inventory hosts yaml file for each of your hosts: (`cp examples/host.yml inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin/ansible-all-hosts.sh) script [in the installation step](installing.md)."
msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md)</sup>"
msgstr ""
#: ../../../docs/configuring-playbook.md:21
msgid "For a basic Matrix installation, that's all you need."
msgid "If you've configured your DNS records and retrieved the playbook's source code to your computer, you can start configuring the playbook. To do so, follow these steps inside the playbook directory:"
msgstr ""
#: ../../../docs/configuring-playbook.md:23
msgid "For a more custom setup, see the [Other configuration options](#other-configuration-options) below."
msgid "create a directory to hold your configuration (`mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\")"
msgstr ""
#: ../../../docs/configuring-playbook.md:25
msgid "[▶️](installing.md) When you're done with all the configuration you'd like to do, continue with [Installing](installing.md)."
msgid "copy the sample configuration file (`cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`)"
msgstr ""
#: ../../../docs/configuring-playbook.md:27
msgid "Other configuration options"
msgid "edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You may also take a look at the various `roles/*/ROLE_NAME_HERE/defaults/main.yml` files (after importing external roles with `just update` into `roles/galaxy`) and see if there's something you'd like to copy over and override in your `vars.yml` configuration file."
msgstr ""
#: ../../../docs/configuring-playbook.md:29
msgid "**Note**: some of the roles like one for integrating Etherpad or Jitsi are managed by their own repositories, and the configuration files for them cannot be found locally (in `roles/galaxy`) until those roles are fetched from the upstream projects. Check [requirements.yml](../requirements.yml) for the URLs of those roles."
msgid "copy the sample inventory hosts file (`cp examples/hosts inventory/hosts`)"
msgstr ""
#: ../../../docs/configuring-playbook.md:31
msgid "Core service adjustments"
msgid "edit the inventory hosts file (`inventory/hosts`) to your liking"
msgstr ""
#: ../../../docs/configuring-playbook.md:33
msgid "Homeserver configuration:"
msgid "(optional, advanced) you may wish to keep your `inventory` directory under version control with [git](https://git-scm.com/) or any other version-control system. The `inventory` directory path is ignored via `.gitignore`, so it won't be part of the playbook repository. You can safely create a new git repository inside that directory with `git init`, etc."
msgstr ""
#: ../../../docs/configuring-playbook.md:34
msgid "[Configuring Synapse](configuring-playbook-synapse.md), if you're going with the default/recommended homeserver implementation"
#: ../../../docs/configuring-playbook.md:35
msgid "(optional, advanced) to run Ansible against multiple servers with different `sudo` credentials, you can copy the sample inventory hosts yaml file for each of your hosts: (`cp examples/host.yml inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin/ansible-all-hosts.sh) script [in the installation step](installing.md)."
msgstr ""
#: ../../../docs/configuring-playbook.md:36
msgid "[Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation"
#: ../../../docs/configuring-playbook.md:37
msgid "For a basic Matrix installation, that's all you need."
msgstr ""
#: ../../../docs/configuring-playbook.md:38
msgid "[Configuring conduwuit](configuring-playbook-conduwuit.md), if you've switched to the [conduwuit](https://conduwuit.puppyirl.gay/) homeserver implementation"
#: ../../../docs/configuring-playbook.md:39
msgid "For a more custom setup, see the [Other configuration options](#other-configuration-options) below."
msgstr ""
#: ../../../docs/configuring-playbook.md:40
msgid "[Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation"
msgstr ""
#: ../../../docs/configuring-playbook.md:42
msgid "Server components:"
#: ../../../docs/configuring-playbook.md:41
msgid "[▶️](installing.md) When you're done with all the configuration you'd like to do, continue with [Installing](installing.md)."
msgstr ""
#: ../../../docs/configuring-playbook.md:43
msgid "[Using an external PostgreSQL server](configuring-playbook-external-postgres.md)"
msgid "Other configuration options"
msgstr ""
#: ../../../docs/configuring-playbook.md:45
msgid "[Configuring a TURN server](configuring-playbook-turn.md) (advanced)"
msgid "**Note**: some of the roles like one for integrating Etherpad or Jitsi are managed by their own repositories, and the configuration files for them cannot be found locally (in `roles/galaxy`) until those roles are fetched from the upstream projects. Check [requirements.yml](../requirements.yml) for the URLs of those roles."
msgstr ""
#: ../../../docs/configuring-playbook.md:47
msgid "[Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) (advanced)"
msgid "Core service adjustments"
msgstr ""
#: ../../../docs/configuring-playbook.md:49
msgid "[Using your own webserver, instead of this playbook's Traefik reverse-proxy](configuring-playbook-own-webserver.md) (advanced)"
msgid "Homeserver configuration:"
msgstr ""
#: ../../../docs/configuring-playbook.md:51
msgid "[Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) (advanced)"
#: ../../../docs/configuring-playbook.md:50
msgid "[Configuring Synapse](configuring-playbook-synapse.md), if you're going with the default/recommended homeserver implementation"
msgstr ""
#: ../../../docs/configuring-playbook.md:53
msgid "[Adjusting email-sending settings](configuring-playbook-email.md)"
#: ../../../docs/configuring-playbook.md:52
msgid "[Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation"
msgstr ""
#: ../../../docs/configuring-playbook.md:55
msgid "[Setting up ma1sd Identity Server](configuring-playbook-ma1sd.md)"
#: ../../../docs/configuring-playbook.md:54
msgid "[Configuring continuwuity](configuring-playbook-continuwuity.md), if you've switched to the [continuwuity](https://continuwuity.org) homeserver implementation"
msgstr ""
#: ../../../docs/configuring-playbook.md:57
msgid "[Setting up Dynamic DNS](configuring-playbook-dynamic-dns.md)"
#: ../../../docs/configuring-playbook.md:56
msgid "[Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation"
msgstr ""
#: ../../../docs/configuring-playbook.md:58
msgid "Server components:"
msgstr ""
#: ../../../docs/configuring-playbook.md:59
msgid "[Using an external PostgreSQL server](configuring-playbook-external-postgres.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:61
msgid "[Configuring a TURN server](configuring-playbook-turn.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:63
msgid "[Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:65
msgid "[Using your own webserver, instead of this playbook's Traefik reverse-proxy](configuring-playbook-own-webserver.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:67
msgid "[Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:69
msgid "[Adjusting email-sending settings](configuring-playbook-email.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:71
msgid "[Setting up Dynamic DNS](configuring-playbook-dynamic-dns.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:73
msgid "Server connectivity:"
msgstr ""
#: ../../../docs/configuring-playbook.md:60
#: ../../../docs/configuring-playbook.md:74
msgid "[Enabling Telemetry for your Matrix server](configuring-playbook-telemetry.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:62
#: ../../../docs/configuring-playbook.md:76
msgid "[Controlling Matrix federation](configuring-playbook-federation.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:64
msgid "Clients"
msgstr ""
#: ../../../docs/configuring-playbook.md:66
msgid "Web clients for Matrix that you can host on your own domains."
msgstr ""
#: ../../../docs/configuring-playbook.md:68
msgid "[Configuring Element Web](configuring-playbook-client-element-web.md), if you're going with the default/recommended client"
msgstr ""
#: ../../../docs/configuring-playbook.md:70
msgid "[Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a lightweight Matrix client with legacy and mobile browser support"
msgstr ""
#: ../../../docs/configuring-playbook.md:72
msgid "[Setting up Cinny](configuring-playbook-client-cinny.md), if you've enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing primarily on simple, elegant and secure interface"
msgstr ""
#: ../../../docs/configuring-playbook.md:74
msgid "[Setting up SchildiChat Web](configuring-playbook-client-schildichat-web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a web client based on [Element Web](https://element.io/) with some extras and tweaks"
msgstr ""
#: ../../../docs/configuring-playbook.md:76
msgid "Authentication and user-related"
msgstr ""
#: ../../../docs/configuring-playbook.md:78
msgid "Extend and modify how users are authenticated on your homeserver."
msgid "[Configuring IPv6](./configuring-ipv6.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:80
msgid "[Setting up Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (Next-generation auth for Matrix, based on OAuth 2.0/OIDC)"
msgid "Clients"
msgstr ""
#: ../../../docs/configuring-playbook.md:82
msgid "[Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)"
msgid "Web clients for Matrix that you can host on your own domains."
msgstr ""
#: ../../../docs/configuring-playbook.md:84
msgid "[Setting up Synapse Admin](configuring-playbook-synapse-admin.md)"
msgid "[Configuring Element Web](configuring-playbook-client-element-web.md), if you're going with the default/recommended client"
msgstr ""
#: ../../../docs/configuring-playbook.md:86
msgid "[Setting up matrix-registration](configuring-playbook-matrix-registration.md)"
msgid "[Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a lightweight Matrix client with legacy and mobile browser support"
msgstr ""
#: ../../../docs/configuring-playbook.md:88
msgid "[Setting up the REST authentication password provider module](configuring-playbook-rest-auth.md) (advanced)"
msgid "[Setting up Cinny](configuring-playbook-client-cinny.md), if you've enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing primarily on simple, elegant and secure interface"
msgstr ""
#: ../../../docs/configuring-playbook.md:90
msgid "[Setting up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) (advanced)"
msgid "[Setting up Sable](configuring-playbook-client-sable.md), if you've enabled [Sable](https://github.com/7w1/sable), a web client focusing primarily on simple, elegant and secure interface"
msgstr ""
#: ../../../docs/configuring-playbook.md:92
msgid "[Setting up the LDAP authentication password provider module](configuring-playbook-ldap-auth.md) (advanced)"
msgid "[Setting up SchildiChat Web](configuring-playbook-client-schildichat-web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a web client based on [Element Web](https://element.io/) with some extras and tweaks"
msgstr ""
#: ../../../docs/configuring-playbook.md:94
msgid "[Setting up FluffyChat Web](configuring-playbook-client-fluffychat-web.md), if you've enabled [FluffyChat Web](https://github.com/krille-chan/fluffychat), a cute cross-platform messenger (web, iOS, Android) for Matrix written in [Flutter](https://flutter.dev/)"
msgstr ""
#: ../../../docs/configuring-playbook.md:97
msgid "Authentication and user-related"
msgstr ""
#: ../../../docs/configuring-playbook.md:99
msgid "Extend and modify how users are authenticated on your homeserver."
msgstr ""
#: ../../../docs/configuring-playbook.md:101
msgid "[Setting up Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (Next-generation auth for Matrix, based on OAuth 2.0/OIDC)"
msgstr ""
#: ../../../docs/configuring-playbook.md:103
msgid "[Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:105
msgid "[Setting up Ketesa](configuring-playbook-ketesa.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:107
msgid "[Setting up matrix-registration](configuring-playbook-matrix-registration.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:109
msgid "[Setting up the REST authentication password provider module](configuring-playbook-rest-auth.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:111
msgid "[Setting up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:113
msgid "[Setting up the LDAP authentication password provider module](configuring-playbook-ldap-auth.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:115
msgid "[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:96
#: ../../../docs/configuring-playbook.md:117
msgid "[Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:98
#: ../../../docs/configuring-playbook.md:119
msgid "[Setting up Matrix User Verification Service](configuring-playbook-user-verification-service.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:100
#: ../../../docs/configuring-playbook.md:121
msgid "File Storage"
msgstr ""
#: ../../../docs/configuring-playbook.md:102
#: ../../../docs/configuring-playbook.md:123
msgid "Use alternative file storage to the default `media_store` folder."
msgstr ""
#: ../../../docs/configuring-playbook.md:104
msgid "[Storing Matrix media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:106
msgid "[Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:108
#: ../../../docs/configuring-playbook.md:125
msgid "[Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:110
#: ../../../docs/configuring-playbook.md:127
msgid "[Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:129
msgid "[Storing Synapse media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:131
msgid "[Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:133
msgid "Bridging other networks"
msgstr ""
#: ../../../docs/configuring-playbook.md:112
#: ../../../docs/configuring-playbook.md:135
msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
msgstr ""
#: ../../../docs/configuring-playbook.md:114
#: ../../../docs/configuring-playbook.md:137
msgid "[Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) — a common guide for configuring mautrix bridges"
msgstr ""
#: ../../../docs/configuring-playbook.md:116
#: ../../../docs/configuring-playbook.md:139
msgid "[Setting up Mautrix Bluesky bridging](configuring-playbook-bridge-mautrix-bluesky.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:141
msgid "[Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:118
#: ../../../docs/configuring-playbook.md:143
msgid "[Setting up Mautrix Telegram bridging](configuring-playbook-bridge-mautrix-telegram.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:120
#: ../../../docs/configuring-playbook.md:145
msgid "[Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:122
#: ../../../docs/configuring-playbook.md:147
msgid "[Setting up Mautrix Google Messages bridging](configuring-playbook-bridge-mautrix-gmessages.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:124
#: ../../../docs/configuring-playbook.md:149
msgid "[Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-mautrix-whatsapp.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:126
#: ../../../docs/configuring-playbook.md:151
msgid "[Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:128
#: ../../../docs/configuring-playbook.md:153
msgid "[Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:130
#: ../../../docs/configuring-playbook.md:155
msgid "[Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-mautrix-googlechat.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:132
#: ../../../docs/configuring-playbook.md:157
msgid "[Setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:134
#: ../../../docs/configuring-playbook.md:159
msgid "[Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-signal.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:136
#: ../../../docs/configuring-playbook.md:161
msgid "[Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](configuring-playbook-bridge-mautrix-wsproxy.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:138
#: ../../../docs/configuring-playbook.md:163
msgid "[Setting up Appservice IRC bridging](configuring-playbook-bridge-appservice-irc.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:140
#: ../../../docs/configuring-playbook.md:165
msgid "[Setting up Appservice Discord bridging](configuring-playbook-bridge-appservice-discord.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:142
msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:144
#: ../../../docs/configuring-playbook.md:167
msgid "[Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-appservice-kakaotalk.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:146
#: ../../../docs/configuring-playbook.md:169
msgid "[Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-linkedin.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:148
#: ../../../docs/configuring-playbook.md:171
msgid "[Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) — a bridge between Matrix and multiple project management services, such as [GitHub](https://github.com), [GitLab](https://about.gitlab.com) and [JIRA](https://www.atlassian.com/software/jira)."
msgstr ""
#: ../../../docs/configuring-playbook.md:150
msgid "[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:152
msgid "[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-puppet-instagram.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:154
msgid "[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:156
msgid "[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-puppet-discord.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:158
#: ../../../docs/configuring-playbook.md:173
msgid "[Setting up MX Puppet GroupMe bridging](configuring-playbook-bridge-mx-puppet-groupme.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:160
#: ../../../docs/configuring-playbook.md:175
msgid "[Setting up Steam bridging](configuring-playbook-bridge-steam.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:177
msgid "[Setting up MX Puppet Steam bridging](configuring-playbook-bridge-mx-puppet-steam.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:162
msgid "[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:164
#: ../../../docs/configuring-playbook.md:179
msgid "[Setting up Postmoogle email bridging](configuring-playbook-bridge-postmoogle.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:166
#: ../../../docs/configuring-playbook.md:181
msgid "[Setting up Matrix SMS bridging](configuring-playbook-bridge-matrix-bridge-sms.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:168
#: ../../../docs/configuring-playbook.md:183
msgid "[Setting up Heisenbridge bouncer-style IRC bridging](configuring-playbook-bridge-heisenbridge.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:170
#: ../../../docs/configuring-playbook.md:185
msgid "[Setting up WeChat bridging](configuring-playbook-bridge-wechat.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:172
#: ../../../docs/configuring-playbook.md:187
msgid "Bots"
msgstr ""
#: ../../../docs/configuring-playbook.md:174
#: ../../../docs/configuring-playbook.md:189
msgid "Bots provide various additional functionality to your installation."
msgstr ""
#: ../../../docs/configuring-playbook.md:176
#: ../../../docs/configuring-playbook.md:191
msgid "[Setting up baibot](configuring-playbook-bot-baibot.md) — a bot through which you can talk to various [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) services ([OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) and [others](https://github.com/etkecc/baibot/blob/main/docs/providers.md))"
msgstr ""
#: ../../../docs/configuring-playbook.md:178
#: ../../../docs/configuring-playbook.md:193
msgid "[Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md) — a bot to remind you about stuff"
msgstr ""
#: ../../../docs/configuring-playbook.md:180
#: ../../../docs/configuring-playbook.md:195
msgid "[Setting up matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) — a bot to create and manage registration tokens to invite users"
msgstr ""
#: ../../../docs/configuring-playbook.md:182
#: ../../../docs/configuring-playbook.md:197
msgid "[Setting up maubot](configuring-playbook-bot-maubot.md) — a plugin-based Matrix bot system"
msgstr ""
#: ../../../docs/configuring-playbook.md:184
#: ../../../docs/configuring-playbook.md:199
msgid "[Setting up Honoroit](configuring-playbook-bot-honoroit.md) — a helpdesk bot"
msgstr ""
#: ../../../docs/configuring-playbook.md:186
#: ../../../docs/configuring-playbook.md:201
msgid "[Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) — a moderation tool/bot"
msgstr ""
#: ../../../docs/configuring-playbook.md:188
#: ../../../docs/configuring-playbook.md:203
msgid "[Setting up Draupnir](configuring-playbook-bot-draupnir.md) — a moderation tool/bot, forked from Mjolnir and maintained by its former leader developer"
msgstr ""
#: ../../../docs/configuring-playbook.md:190
#: ../../../docs/configuring-playbook.md:205
msgid "[Setting up Draupnir for all/D4A](configuring-playbook-appservice-draupnir-for-all.md) — like the [Draupnir bot](configuring-playbook-bot-draupnir.md) mentioned above, but running in appservice mode and supporting multiple instances"
msgstr ""
#: ../../../docs/configuring-playbook.md:192
#: ../../../docs/configuring-playbook.md:207
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:194
#: ../../../docs/configuring-playbook.md:209
msgid "Administration"
msgstr ""
#: ../../../docs/configuring-playbook.md:196
#: ../../../docs/configuring-playbook.md:211
msgid "Services that help you in administrating and monitoring your Matrix installation."
msgstr ""
#: ../../../docs/configuring-playbook.md:198
#: ../../../docs/configuring-playbook.md:213
msgid "[Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:200
#: ../../../docs/configuring-playbook.md:215
msgid "[Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:202
msgid "[Enabling metrics and graphs for NginX logs](configuring-playbook-prometheus-nginxlog.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:204
#: ../../../docs/configuring-playbook.md:217
msgid "[Setting up the rageshake bug report server](configuring-playbook-rageshake.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:206
#: ../../../docs/configuring-playbook.md:219
msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:208
#: ../../../docs/configuring-playbook.md:221
msgid "Backups:"
msgstr ""
#: ../../../docs/configuring-playbook.md:209
#: ../../../docs/configuring-playbook.md:222
msgid "[Setting up BorgBackup](configuring-playbook-backup-borg.md) — a full Matrix server backup solution, including the Postgres database"
msgstr ""
#: ../../../docs/configuring-playbook.md:211
msgid "[Setting up postgres backup](configuring-playbook-postgres-backup.md) — a Postgres-database backup solution (note: does not include other files)"
#: ../../../docs/configuring-playbook.md:224
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:213
#: ../../../docs/configuring-playbook.md:226
msgid "Other specialized services"
msgstr ""
#: ../../../docs/configuring-playbook.md:215
#: ../../../docs/configuring-playbook.md:228
msgid "Various services that don't fit any other categories."
msgstr ""
#: ../../../docs/configuring-playbook.md:217
msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md)"
#: ../../../docs/configuring-playbook.md:230
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:219
#: ../../../docs/configuring-playbook.md:232
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:234
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:236
msgid "[Setting up Matrix RTC](configuring-playbook-matrix-rtc.md) (optional)"
msgstr ""
#: ../../../docs/configuring-playbook.md:238
msgid "[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers"
msgstr ""
#: ../../../docs/configuring-playbook.md:221
#: ../../../docs/configuring-playbook.md:240
msgid "[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:223
#: ../../../docs/configuring-playbook.md:242
msgid "[Setting up Matrix.to](configuring-playbook-matrixto.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:244
msgid "[Setting up Etherpad](configuring-playbook-etherpad.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:225
#: ../../../docs/configuring-playbook.md:246
msgid "[Setting up the Jitsi video-conferencing platform](configuring-playbook-jitsi.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:227
#: ../../../docs/configuring-playbook.md:248
msgid "[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) — a federated comment system built on Matrix"
msgstr ""
#: ../../../docs/configuring-playbook.md:229
#: ../../../docs/configuring-playbook.md:250
msgid "[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-pantalaimon.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:231
#: ../../../docs/configuring-playbook.md:252
msgid "[Setting up the Sygnal push gateway](configuring-playbook-sygnal.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:233
#: ../../../docs/configuring-playbook.md:254
msgid "[Setting up the ntfy push notifications server](configuring-playbook-ntfy.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:235
#: ../../../docs/configuring-playbook.md:256
msgid "Deprecated / unmaintained / removed services"
msgstr ""
#: ../../../docs/configuring-playbook.md:237
#: ../../../docs/configuring-playbook.md:258
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:239
#: ../../../docs/configuring-playbook.md:260
msgid "[Configuring conduwuit](configuring-playbook-conduwuit.md) (removed; this component has been abandoned and unmaintained)"
msgstr ""
#: ../../../docs/configuring-playbook.md:262
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:241
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))"
#: ../../../docs/configuring-playbook.md:264
msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md) (removed; this component has been discontinued)"
msgstr ""
#: ../../../docs/configuring-playbook.md:243
#: ../../../docs/configuring-playbook.md:266
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:268
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:245
msgid "[Setting up Email2Matrix](configuring-playbook-email2matrix.md) (unmaintained; 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))"
#: ../../../docs/configuring-playbook.md:270
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:247
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))"
#: ../../../docs/configuring-playbook.md:272
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:249
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))"
#: ../../../docs/configuring-playbook.md:274
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:251
#: ../../../docs/configuring-playbook.md:276
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:278
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:280
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:253
msgid "[Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-mautrix-hangouts.md) (deprecated in favor of the Google Chat bridge with [mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md))"
msgstr ""
#: ../../../docs/configuring-playbook.md:255
#: ../../../docs/configuring-playbook.md:282
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:257
#: ../../../docs/configuring-playbook.md:284
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:286
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:288
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:290
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:292
msgid "[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md))"
msgstr ""
#: ../../../docs/configuring-playbook.md:294
msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md) (removed; since Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0) the same feature is available natively.)"
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
@@ -19,21 +19,21 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/container-images.md:1
#: ../../../docs/container-images.md:18
msgid "Container images used by the playbook"
msgstr ""
#: ../../../docs/container-images.md:3
#: ../../../docs/container-images.md:20
msgid "This page summarizes the container ([Docker](https://www.docker.com/)) images used by the playbook when setting up your server."
msgstr ""
#: ../../../docs/container-images.md:5
#: ../../../docs/container-images.md:22
msgid "We try to stick to official images (provided by their respective projects) as much as possible."
msgstr ""
#: ../../../docs/container-images.md:7
#: ../../../docs/container-images.md:24
msgid "Homeserver"
msgstr ""
@@ -86,15 +86,15 @@ msgid "Storing your data and managing your presence in the [Matrix](http://matri
msgstr ""
#: ../../../docs/container-images.md
msgid "[conduwuit](configuring-playbook-conduwuit.md)"
msgid "[continuwuity](configuring-playbook-continuwuity.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[girlbossceo/conduwuit](https://ghcr.io/girlbossceo/conduwuit)"
msgid "[continuwuation/continuwuity](https://forgejo.ellis.link/continuwuation/continuwuity)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit is a fork of Conduit."
msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. continuwuity is a continuation of conduwuit."
msgstr ""
#: ../../../docs/container-images.md
@@ -109,11 +109,11 @@ msgstr ""
msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse."
msgstr ""
#: ../../../docs/container-images.md:16
#: ../../../docs/container-images.md:33
msgid "Clients"
msgstr ""
#: ../../../docs/container-images.md:18
#: ../../../docs/container-images.md:35
msgid "Web clients for Matrix that you can host on your own domains."
msgstr ""
@@ -153,6 +153,14 @@ msgstr ""
msgid "Simple, elegant and secure web client"
msgstr ""
#: ../../../docs/container-images.md
msgid "[Sable](configuring-playbook-client-sable.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[7w1/sable](https://ghcr.io/7w1/sable)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md)"
msgstr ""
@@ -165,11 +173,11 @@ msgstr ""
msgid "Based on Element Web, with a more traditional instant messaging experience"
msgstr ""
#: ../../../docs/container-images.md:27
#: ../../../docs/container-images.md:45
msgid "Server Components"
msgstr ""
#: ../../../docs/container-images.md:29
#: ../../../docs/container-images.md:47
msgid "Services that run on the server to make the various parts of your installation work."
msgstr ""
@@ -206,7 +214,7 @@ msgid "[Traefik](https://hub.docker.com/_/traefik/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Web server, listening on ports 80, 443 and 8448 — standing in front of all the other services. Using your own webserver [is possible](configuring-playbook-own-webserver.md)"
msgid "Web server, listening on ports 80, 443 and 8448 — standing in front of all the other services. [Using your own webserver](configuring-playbook-own-webserver.md) is also possible."
msgstr ""
#: ../../../docs/container-images.md
@@ -218,7 +226,7 @@ msgid "[certbot/certbot](https://hub.docker.com/r/certbot/certbot/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "The [certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/)"
msgid "[Certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/)"
msgstr ""
#: ../../../docs/container-images.md
@@ -233,18 +241,6 @@ msgstr ""
msgid "Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[ma1sd](configuring-playbook-ma1sd.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Matrix Identity Server"
msgstr ""
#: ../../../docs/container-images.md
msgid "[ddclient](configuring-playbook-dynamic-dns.md)"
msgstr ""
@@ -257,11 +253,35 @@ msgstr ""
msgid "Update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider"
msgstr ""
#: ../../../docs/container-images.md:41
#: ../../../docs/container-images.md
msgid "[LiveKit Server](configuring-playbook-livekit-server.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[livekit/livekit-server](https://hub.docker.com/r/livekit/livekit-server/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "WebRTC server for audio/video calls"
msgstr ""
#: ../../../docs/container-images.md
msgid "[Livekit JWT Service](configuring-playbook-livekit-jwt-service.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[element-hq/lk-jwt-service](https://ghcr.io/element-hq/lk-jwt-service)"
msgstr ""
#: ../../../docs/container-images.md
msgid "JWT service for integrating [Element Call](./configuring-playbook-element-call.md) with [LiveKit Server](./configuring-playbook-livekit-server.md)"
msgstr ""
#: ../../../docs/container-images.md:60
msgid "Authentication"
msgstr ""
#: ../../../docs/container-images.md:43
#: ../../../docs/container-images.md:62
msgid "Extend and modify how users are authenticated on your homeserver."
msgstr ""
@@ -302,7 +322,7 @@ msgid "[activism.international/matrix_ldap_registration_proxy](https://gitlab.co
msgstr ""
#: ../../../docs/container-images.md
msgid "A proxy that handles Matrix registration requests and forwards them to LDAP."
msgid "Proxy that handles Matrix registration requests and forwards them to LDAP"
msgstr ""
#: ../../../docs/container-images.md
@@ -314,11 +334,11 @@ msgid "[zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-ma
msgstr ""
#: ../../../docs/container-images.md
msgid "A simple python application to have a token based Matrix registration"
msgid "Simple python application to have a token based Matrix registration"
msgstr ""
#: ../../../docs/container-images.md
msgid "[Matrix User Verification Service](configuring-playbook-user-verification-service.md) (UVS)"
msgid "[Matrix User Verification Service](configuring-playbook-user-verification-service.md)"
msgstr ""
#: ../../../docs/container-images.md
@@ -334,14 +354,14 @@ msgid "[synapse-simple-antispam](configuring-playbook-synapse-simple-antispam.md
msgstr ""
#: ../../../docs/container-images.md
msgid "A spam checker module"
msgid "Spam checker module"
msgstr ""
#: ../../../docs/container-images.md:55
#: ../../../docs/container-images.md:74
msgid "File Storage"
msgstr ""
#: ../../../docs/container-images.md:57
#: ../../../docs/container-images.md:76
msgid "Use alternative file storage to the default `media_store` folder."
msgstr ""
@@ -370,17 +390,29 @@ msgid "[t2bot/matrix-media-repo](https://ghcr.io/t2bot/matrix-media-repo)"
msgstr ""
#: ../../../docs/container-images.md
msgid "matrix-media-repo is a highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
msgid "Highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
msgstr ""
#: ../../../docs/container-images.md:65
#: ../../../docs/container-images.md:84
msgid "Bridges"
msgstr ""
#: ../../../docs/container-images.md:67
#: ../../../docs/container-images.md:86
msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
msgstr ""
#: ../../../docs/container-images.md
msgid "[mautrix-bluesky](configuring-playbook-bridge-mautrix-bluesky.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mautrix/bluesky](https://mau.dev/mautrix/bluesky/container_registry)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge to [Bluesky](https://bsky.social/about)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mautrix-discord](configuring-playbook-bridge-mautrix-discord.md)"
msgstr ""
@@ -549,14 +581,6 @@ msgstr ""
msgid "Bridge to [Discord](https://discordapp.com/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrix-hookshot](configuring-playbook-bridge-hookshot.md)"
msgstr ""
@@ -605,62 +629,6 @@ msgstr ""
msgid "Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[nodefyme/go-skype-bridge](https://hub.docker.com/r/nodefyme/go-skype-bridge)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge to [Skype](https://www.skype.com)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/container_registry)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge to [Slack](https://slack.com)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-puppet-instagram)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/container_registry)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-groupme](configuring-playbook-bridge-mx-puppet-groupme.md)"
msgstr ""
@@ -673,6 +641,18 @@ msgstr ""
msgid "Bridge to [GroupMe](https://groupme.com/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrix-steam-bridge](configuring-playbook-bridge-steam.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[jasonlaguidice/matrix-steam-bridge](https://github.com/jasonlaguidice/matrix-steam-bridge/pkgs/container/matrix-steam-bridge)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge to [Steam](https://steampowered.com/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-steam](configuring-playbook-bridge-mx-puppet-steam.md)"
msgstr ""
@@ -697,11 +677,11 @@ msgstr ""
msgid "Email to Matrix bridge"
msgstr ""
#: ../../../docs/container-images.md:99
#: ../../../docs/container-images.md:114
msgid "Bots"
msgstr ""
#: ../../../docs/container-images.md:101
#: ../../../docs/container-images.md:116
msgid "Bots provide various additional functionality to your installation."
msgstr ""
@@ -714,7 +694,7 @@ msgid "[etke.cc/baibot](https://ghcr.io/etkecc/baibot)"
msgstr ""
#: ../../../docs/container-images.md
msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
msgid "Bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
msgstr ""
#: ../../../docs/container-images.md
@@ -750,7 +730,7 @@ msgid "[dock.mau.dev/maubot/maubot](https://mau.dev/maubot/maubot/container_regi
msgstr ""
#: ../../../docs/container-images.md
msgid "A plugin-based Matrix bot system"
msgid "Plugin-based Matrix bot system"
msgstr ""
#: ../../../docs/container-images.md
@@ -762,7 +742,7 @@ msgid "[etke.cc/honoroit](https://github.com/etkecc/honoroit/container_registry)
msgstr ""
#: ../../../docs/container-images.md
msgid "A helpdesk bot"
msgid "Helpdesk bot"
msgstr ""
#: ../../../docs/container-images.md
@@ -774,7 +754,7 @@ msgid "[matrixdotorg/mjolnir](https://hub.docker.com/r/matrixdotorg/mjolnir)"
msgstr ""
#: ../../../docs/container-images.md
msgid "A moderation tool for Matrix"
msgid "Moderation tool for Matrix"
msgstr ""
#: ../../../docs/container-images.md
@@ -786,7 +766,7 @@ msgid "[gnuxie/draupnir](https://hub.docker.com/r/gnuxie/draupnir)"
msgstr ""
#: ../../../docs/container-images.md
msgid "A moderation tool for Matrix (Fork of Mjolnir)"
msgid "Moderation tool for Matrix (Fork of Mjolnir)"
msgstr ""
#: ../../../docs/container-images.md
@@ -801,11 +781,11 @@ msgstr ""
msgid "Web forms (HTTP POST) to Matrix"
msgstr ""
#: ../../../docs/container-images.md:114
#: ../../../docs/container-images.md:129
msgid "Administration"
msgstr ""
#: ../../../docs/container-images.md:116
#: ../../../docs/container-images.md:131
msgid "Services that help you in administrating and monitoring your Matrix installation."
msgstr ""
@@ -834,15 +814,15 @@ msgid "OAuth 2.0 and OpenID Provider server"
msgstr ""
#: ../../../docs/container-images.md
msgid "[synapse-admin](configuring-playbook-synapse-admin.md)"
msgid "[ketesa](configuring-playbook-ketesa.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[etke.cc/synapse-admin](https://ghcr.io/etkecc/synapse-admin)"
msgid "[etkecc/ketesa](https://ghcr.io/etkecc/ketesa)"
msgstr ""
#: ../../../docs/container-images.md
msgid "A web UI tool for administrating users and rooms on your Matrix server"
msgid "Fully-featured web UI for administrating your Matrix homeserver — users, rooms, media, sessions, and more"
msgstr ""
#: ../../../docs/container-images.md
@@ -874,7 +854,7 @@ msgid "Graphing tool that works well with the above two images. Our playbook als
msgstr ""
#: ../../../docs/container-images.md
msgid "[Metrics and Graphs](configuring-playbook-prometheus-nginxlog.md)"
msgid "[Metrics and Graphs](configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-nginx-logs-optional)"
msgstr ""
#: ../../../docs/container-images.md
@@ -893,6 +873,18 @@ msgstr ""
msgid "Backups"
msgstr ""
#: ../../../docs/container-images.md
msgid "[postgres-backup-local](configuring-playbook-postgres-backup.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[prodrigestivill/postgres-backup-local](https://hub.docker.com/r/prodrigestivill/postgres-backup-local)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Create automatic database backups"
msgstr ""
#: ../../../docs/container-images.md
msgid "[rageshake](configuring-playbook-rageshake.md)"
msgstr ""
@@ -913,44 +905,24 @@ msgstr ""
msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus."
msgstr ""
#: ../../../docs/container-images.md:131
#: ../../../docs/container-images.md:147
msgid "Misc"
msgstr ""
#: ../../../docs/container-images.md:133
#: ../../../docs/container-images.md:149
msgid "Various services that don't fit any other categories."
msgstr ""
#: ../../../docs/container-images.md
msgid "[sliding-sync](configuring-playbook-sliding-sync-proxy.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Sliding Sync support for clients which require it (like old Element X versions, before it got switched to Simplified Sliding Sync)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "A Synapse module to automatically accept invites."
msgstr ""
#: ../../../docs/container-images.md
msgid "[synapse_auto_compressor](configuring-playbook-synapse-auto-compressor.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[etke.cc/rust-synapse-compress-state](https://gitlab.com/etke.cc/rust-synapse-compress-state/container_registry)"
msgid "[mb-saces/rust-synapse-tools](https://gitlab.com/mb-saces/rust-synapse-tools/container_registry)"
msgstr ""
#: ../../../docs/container-images.md
msgid "A cli tool that automatically compresses `state_groups` database table in background."
msgid "Cli tool that automatically compresses Synapse's `state_groups` database table in background"
msgstr ""
#: ../../../docs/container-images.md
@@ -974,7 +946,7 @@ msgid "[etherpad/etherpad](https://hub.docker.com/r/etherpad/etherpad/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "An open source collaborative text editor"
msgid "Open source collaborative text editor"
msgstr ""
#: ../../../docs/container-images.md
@@ -986,7 +958,7 @@ msgid "[jitsi/web](https://hub.docker.com/r/jitsi/web)"
msgstr ""
#: ../../../docs/container-images.md
msgid "the [Jitsi](https://jitsi.org/) web UI"
msgid "[Jitsi](https://jitsi.org/) web UI"
msgstr ""
#: ../../../docs/container-images.md
@@ -994,7 +966,7 @@ msgid "[jitsi/jicofo](https://hub.docker.com/r/jitsi/jicofo)"
msgstr ""
#: ../../../docs/container-images.md
msgid "the [Jitsi](https://jitsi.org/) Focus component"
msgid "[Jitsi](https://jitsi.org/) Focus component"
msgstr ""
#: ../../../docs/container-images.md
@@ -1002,7 +974,7 @@ msgid "[jitsi/prosody](https://hub.docker.com/r/jitsi/prosody)"
msgstr ""
#: ../../../docs/container-images.md
msgid "the [Jitsi](https://jitsi.org/) Prosody XMPP server component"
msgid "[Jitsi](https://jitsi.org/) Prosody XMPP server component"
msgstr ""
#: ../../../docs/container-images.md
@@ -1010,7 +982,7 @@ msgid "[jitsi/jvb](https://hub.docker.com/r/jitsi/jvb)"
msgstr ""
#: ../../../docs/container-images.md
msgid "the [Jitsi](https://jitsi.org/) Video Bridge component"
msgid "[Jitsi](https://jitsi.org/) Video Bridge component"
msgstr ""
#: ../../../docs/container-images.md
@@ -1022,7 +994,7 @@ msgid "[cactuscomments/cactus-appservice](https://hub.docker.com/r/cactuscomment
msgstr ""
#: ../../../docs/container-images.md
msgid "A federated comment system built on Matrix"
msgid "Federated comment system built on Matrix"
msgstr ""
#: ../../../docs/container-images.md
@@ -1038,7 +1010,7 @@ msgid "[matrixdotorg/pantalaimon](https://hub.docker.com/r/matrixdotorg/pantalai
msgstr ""
#: ../../../docs/container-images.md
msgid "An E2EE aware proxy daemon"
msgid "E2EE aware proxy daemon"
msgstr ""
#: ../../../docs/container-images.md
@@ -1065,24 +1037,36 @@ msgstr ""
msgid "Self-hosted, UnifiedPush-compatible push notifications server"
msgstr ""
#: ../../../docs/container-images.md:152
#: ../../../docs/container-images.md
msgid "[Element Call](configuring-playbook-element-call.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[element-hq/element-call](https://ghcr.io/element-hq/element-call)"
msgstr ""
#: ../../../docs/container-images.md
msgid "A native Matrix video conferencing application"
msgstr ""
#: ../../../docs/container-images.md:167
msgid "Container images of deprecated / unmaintained services"
msgstr ""
#: ../../../docs/container-images.md:154
#: ../../../docs/container-images.md:169
msgid "The list of the deprecated or unmaintained services is available [here](configuring-playbook.md#deprecated--unmaintained--removed-services)."
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md)"
msgid "[conduwuit](configuring-playbook-conduwuit.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks)"
msgid "[girlbossceo/conduwuit](https://ghcr.io/girlbossceo/conduwuit)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.)"
msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit was a fork of Conduit."
msgstr ""
#: ../../../docs/container-images.md
@@ -1094,7 +1078,7 @@ msgid "[turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-di
msgstr ""
#: ../../../docs/container-images.md
msgid "An open source integration manager for Matrix clients"
msgid "Open source integration manager for Matrix clients"
msgstr ""
#: ../../../docs/container-images.md
@@ -1118,7 +1102,39 @@ msgid "[matrixdotorg/go-neb](https://hub.docker.com/r/matrixdotorg/go-neb)"
msgstr ""
#: ../../../docs/container-images.md
msgid "A multi functional bot written in Go"
msgid "Multi functional bot written in Go"
msgstr ""
#: ../../../docs/container-images.md
msgid "[ma1sd](configuring-playbook-ma1sd.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Matrix Identity Server"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.)"
msgstr ""
#: ../../../docs/container-images.md
@@ -1145,18 +1161,6 @@ msgstr ""
msgid "Bridge to [Facebook](https://facebook.com/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mautrix-hangouts](configuring-playbook-bridge-mautrix-hangouts.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mautrix/hangouts](https://mau.dev/mautrix/hangouts/container_registry)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge to [Google Hangouts](https://en.wikipedia.org/wiki/Google_Hangouts)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mautrix-instagram](configuring-playbook-bridge-mautrix-instagram.md)"
msgstr ""
@@ -1168,3 +1172,67 @@ msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge to [Instagram](https://instagram.com/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/container_registry)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-puppet-instagram)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/container_registry)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge to [Slack](https://slack.com)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
msgstr ""
#: ../../../docs/container-images.md
msgid "[sliding-sync](configuring-playbook-sliding-sync-proxy.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Sliding Sync support for clients which require it (like old Element X versions, before it got switched to Simplified Sliding Sync)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Synapse module to automatically accept invites"
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
@@ -19,228 +19,225 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/registering-users.md:1
#: ../../../docs/registering-users.md:11
msgid "Registering users"
msgstr ""
#: ../../../docs/registering-users.md:3
#: ../../../docs/registering-users.md:13
msgid "This documentation page tells you how to create user accounts on your Matrix server."
msgstr ""
#: ../../../docs/registering-users.md:5
#: ../../../docs/registering-users.md:15
msgid "Table of contents:"
msgstr ""
#: ../../../docs/registering-users.md:7
#: ../../../docs/registering-users.md:16
msgid "[Registering users](#registering-users)"
msgstr ""
#: ../../../docs/registering-users.md:8
#: ../../../docs/registering-users.md:17
msgid "[Registering users manually](#registering-users-manually)"
msgstr ""
#: ../../../docs/registering-users.md:9
#: ../../../docs/registering-users.md:18
msgid "[Managing users via a Web UI](#managing-users-via-a-web-ui)"
msgstr ""
#: ../../../docs/registering-users.md:10
#: ../../../docs/registering-users.md:19
msgid "[Letting certain users register on your private server](#letting-certain-users-register-on-your-private-server)"
msgstr ""
#: ../../../docs/registering-users.md:11
#: ../../../docs/registering-users.md:20
msgid "[Enabling public user registration](#enabling-public-user-registration)"
msgstr ""
#: ../../../docs/registering-users.md:12
#: ../../../docs/registering-users.md:21
msgid "[Adding/Removing Administrator privileges to an existing user](#addingremoving-administrator-privileges-to-an-existing-user)"
msgstr ""
#: ../../../docs/registering-users.md:14
#: ../../../docs/registering-users.md:23
msgid "Registering users manually"
msgstr ""
#: ../../../docs/registering-users.md:16 ../../../docs/registering-users.md:121
#: ../../../docs/registering-users.md:25 ../../../docs/registering-users.md:127
msgid "**Notes**:"
msgstr ""
#: ../../../docs/registering-users.md:17
#: ../../../docs/registering-users.md:26
msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`"
msgstr ""
#: ../../../docs/registering-users.md:18
#: ../../../docs/registering-users.md:27
msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)"
msgstr ""
#: ../../../docs/registering-users.md:19
#: ../../../docs/registering-users.md:28
msgid "Use `admin=yes` or `admin=no` depending on whether you wish to make the user an administrator of the Matrix server"
msgstr ""
#: ../../../docs/registering-users.md:21
#: ../../../docs/registering-users.md:30
msgid "After registering a user (using one of the methods below), **you can log in with that user** via the [Element Web](configuring-playbook-client-element-web.md) service that this playbook has installed for you at a URL like this: `https://element.example.com/`."
msgstr ""
#: ../../../docs/registering-users.md:23
#: ../../../docs/registering-users.md:32
msgid "Registering users via the Ansible playbook"
msgstr ""
#: ../../../docs/registering-users.md:25
#: ../../../docs/registering-users.md:34
msgid "It's best to register users via the Ansible playbook, because it works regardless of homeserver implementation (Synapse, Dendrite, etc) or usage of [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (MAS)."
msgstr ""
#: ../../../docs/registering-users.md:27
#: ../../../docs/registering-users.md:36
msgid "To register a user via this Ansible playbook:"
msgstr ""
#: ../../../docs/registering-users.md:35
#: ../../../docs/registering-users.md:44
msgid "**or** by invoking `ansible-playbook` manually:"
msgstr ""
#: ../../../docs/registering-users.md:43
#: ../../../docs/registering-users.md:52
msgid "Feel free to register as many users (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your user account only (with `admin=yes`), and others should be created with `admin=no`."
msgstr ""
#: ../../../docs/registering-users.md:45
#: ../../../docs/registering-users.md:54
msgid "[!WARNING] If you're registering users against Matrix Authentication Service, do note that it [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information."
msgstr ""
#: ../../../docs/registering-users.md:48
#: ../../../docs/registering-users.md:57
msgid "Registering users manually for Synapse"
msgstr ""
#: ../../../docs/registering-users.md:50
#: ../../../docs/registering-users.md:59
msgid "If you're using the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default), you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
msgstr ""
#: ../../../docs/registering-users.md:58
#: ../../../docs/registering-users.md:67
msgid "Registering users manually for Dendrite"
msgstr ""
#: ../../../docs/registering-users.md:60
#: ../../../docs/registering-users.md:69
msgid "If you're using the [Dendrite](./configuring-playbook-dendrite.md) homeserver implementation, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
msgstr ""
#: ../../../docs/registering-users.md:68
#: ../../../docs/registering-users.md:77
msgid "Registering users manually for Matrix Authentication Service"
msgstr ""
#: ../../../docs/registering-users.md:70
#: ../../../docs/registering-users.md:79
msgid "If you're using the [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) and your existing homeserver (most likely [Synapse](./configuring-playbook-synapse.md)) is delegating authentication to it, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
msgstr ""
#: ../../../docs/registering-users.md:78
#: ../../../docs/registering-users.md:87
msgid "This `register-user` script actually invokes the `mas-cli manage register-user` command under the hood. If you'd like more control over the registration process, consider invoking the `mas-cli` command directly:"
msgstr ""
#: ../../../docs/registering-users.md:84
#: ../../../docs/registering-users.md:93
msgid "[!WARNING] Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information."
msgstr ""
#: ../../../docs/registering-users.md:87
#: ../../../docs/registering-users.md:96
msgid "Managing users via a Web UI"
msgstr ""
#: ../../../docs/registering-users.md:89
msgid "To manage users more easily (via a web user-interace), you can install [Synapse Admin](configuring-playbook-synapse-admin.md)."
msgstr ""
#: ../../../docs/registering-users.md:91
msgid "[!WARNING] If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information."
msgstr ""
#: ../../../docs/registering-users.md:94
msgid "Letting certain users register on your private server"
msgstr ""
#: ../../../docs/registering-users.md:96
msgid "If you'd rather **keep your server private** (public registration closed, as is the default), and **let certain people create accounts by themselves** (instead of creating user accounts manually like this), consider installing and making use of [matrix-registration](configuring-playbook-matrix-registration.md)."
msgstr ""
#: ../../../docs/registering-users.md:98
msgid "Enabling public user registration"
msgid "To manage users and your homeserver more easily (via a web interface), you can install [Ketesa](configuring-playbook-ketesa.md) — a fully-featured admin UI covering users, rooms, media, sessions, and MAS management."
msgstr ""
#: ../../../docs/registering-users.md:100
msgid "To **open up user registration publicly** (usually **not recommended**), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgid "Letting certain users register on your private server"
msgstr ""
#: ../../../docs/registering-users.md:102
msgid "For Synapse:"
msgid "If you'd rather **keep your server private** (public registration closed, as is the default), and **let certain people create accounts by themselves** (instead of creating user accounts manually like this), consider installing and making use of [matrix-registration](configuring-playbook-matrix-registration.md)."
msgstr ""
#: ../../../docs/registering-users.md:104
msgid "Enabling public user registration"
msgstr ""
#: ../../../docs/registering-users.md:106
msgid "To **open up user registration publicly** (usually **not recommended**), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/registering-users.md:108
msgid "For Dendrite:"
msgid "For Synapse:"
msgstr ""
#: ../../../docs/registering-users.md:114
msgid "For Dendrite:"
msgstr ""
#: ../../../docs/registering-users.md:120
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/registering-users.md:123
#: ../../../docs/registering-users.md:129
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/registering-users.md:125
#: ../../../docs/registering-users.md:131
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgstr ""
#: ../../../docs/registering-users.md:127
#: ../../../docs/registering-users.md:133
msgid "If you're opening up registrations publicly like this, you might also wish to [configure CAPTCHA protection](configuring-captcha.md)."
msgstr ""
#: ../../../docs/registering-users.md:129
#: ../../../docs/registering-users.md:135
msgid "Adding/Removing Administrator privileges to an existing user"
msgstr ""
#: ../../../docs/registering-users.md:131
#: ../../../docs/registering-users.md:137
msgid "Adding/Removing Administrator privileges to an existing user in Synapse"
msgstr ""
#: ../../../docs/registering-users.md:133
#: ../../../docs/registering-users.md:139
msgid "To change the admin privileges for a user in Synapse's local database, you need to run an SQL query like this against the `synapse` database:"
msgstr ""
#: ../../../docs/registering-users.md:139
#: ../../../docs/registering-users.md:145
msgid "where:"
msgstr ""
#: ../../../docs/registering-users.md:141
#: ../../../docs/registering-users.md:147
msgid "`ADMIN_VALUE` being either `0` (regular user) or `1` (admin)"
msgstr ""
#: ../../../docs/registering-users.md:142
#: ../../../docs/registering-users.md:148
msgid "`USER` and `example.com` pointing to a valid user on your server"
msgstr ""
#: ../../../docs/registering-users.md:144
#: ../../../docs/registering-users.md:150
msgid "If you're using the integrated Postgres server and not an [external Postgres server](configuring-playbook-external-postgres.md), you can launch a Postgres into the `synapse` database by:"
msgstr ""
#: ../../../docs/registering-users.md:146
#: ../../../docs/registering-users.md:152
msgid "running `/matrix/postgres/bin/cli` — to launch [`psql`](https://www.postgresql.org/docs/current/app-psql.html)"
msgstr ""
#: ../../../docs/registering-users.md:147
#: ../../../docs/registering-users.md:153
msgid "running `\\c synapse` — to change to the `synapse` database"
msgstr ""
#: ../../../docs/registering-users.md:149
#: ../../../docs/registering-users.md:155
msgid "You can then proceed to run the query above."
msgstr ""
#: ../../../docs/registering-users.md:151
#: ../../../docs/registering-users.md:157
msgid "**Note**: directly modifying the raw data of Synapse (or any other software) could cause the software to break. You've been warned!"
msgstr ""
#: ../../../docs/registering-users.md:153
#: ../../../docs/registering-users.md:159
msgid "Adding/Removing Administrator privileges to an existing user in Matrix Authentication Service"
msgstr ""
#: ../../../docs/registering-users.md:155
msgid "Promoting/demoting a user in Matrix Authentication Service cannot currently (2024-10-19) be done via the [`mas-cli` Management tool](./configuring-playbook-matrix-authentication-service.md#management)."
#: ../../../docs/registering-users.md:161
msgid "Promoting/demoting a user in Matrix Authentication Service can be done using the [`mas-cli`](./configuring-playbook-matrix-authentication-service.md#management) management tool's [`manage promote-admin`](https://element-hq.github.io/matrix-authentication-service/reference/cli/manage.html#manage-promote-admin) and [`manage demote-admin`](https://element-hq.github.io/matrix-authentication-service/reference/cli/manage.html#manage-demote-admin) commands. For example: `/matrix/matrix-authentication-service/bin/mas-cli manage promote-admin some.username`."
msgstr ""
#: ../../../docs/registering-users.md:157
msgid "You can do it via the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html)'s `POST /api/admin/v1/users/{id}/set-admin` endpoint."
#: ../../../docs/registering-users.md:163
#, python-brace-format
msgid "You can also do it via the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html)'s `POST /api/admin/v1/users/{id}/set-admin` endpoint."
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-12-16 12:05+0900\n"
"POT-Creation-Date: 2026-04-03 12:09+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
@@ -19,160 +19,136 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/self-building.md:1
#: ../../../docs/self-building.md:15
msgid "Self-building"
msgstr ""
#: ../../../docs/self-building.md:3
#: ../../../docs/self-building.md:17
msgid "**Caution: self-building does not have to be used on its own. See the [Alternative Architectures](alternative-architectures.md) page.**"
msgstr ""
#: ../../../docs/self-building.md:5
#: ../../../docs/self-building.md:19
msgid "The playbook supports self-building of various components, which don't have a container image for your architecture (see the [container images we use](container-images.md)). For `amd64`, self-building is not required."
msgstr ""
#: ../../../docs/self-building.md:7
#: ../../../docs/self-building.md:21
msgid "For other architectures (e.g. `arm32`, `arm64`), ready-made container images are used when available. If there's no ready-made image for a specific component and said component supports self-building, an image will be built on the host. Building images like this takes more time and resources (some build tools need to get installed by the playbook to assist building)."
msgstr ""
#: ../../../docs/self-building.md:9
#: ../../../docs/self-building.md:23
msgid "To make use of self-building, you don't need to do anything. If a component has an image for the specified architecture, the playbook will use it directly. If not, it will build the image on the server itself."
msgstr ""
#: ../../../docs/self-building.md:11
#: ../../../docs/self-building.md:25
msgid "Note that **not all components support self-building yet**."
msgstr ""
#: ../../../docs/self-building.md:13
#: ../../../docs/self-building.md:27
msgid "Possibly outdated list of roles where self-building the Docker image is currently possible:"
msgstr ""
#: ../../../docs/self-building.md:14
#: ../../../docs/self-building.md:28
msgid "`matrix-synapse`"
msgstr ""
#: ../../../docs/self-building.md:15
msgid "`matrix-synapse-admin`"
msgstr ""
#: ../../../docs/self-building.md:16
msgid "`matrix-client-element`"
msgstr ""
#: ../../../docs/self-building.md:17
msgid "`matrix-client-hydrogen`"
msgstr ""
#: ../../../docs/self-building.md:18
msgid "`matrix-client-cinny`"
msgstr ""
#: ../../../docs/self-building.md:19
msgid "`matrix-registration`"
msgstr ""
#: ../../../docs/self-building.md:20
msgid "`matrix-coturn`"
msgstr ""
#: ../../../docs/self-building.md:21
msgid "`matrix-corporal`"
msgstr ""
#: ../../../docs/self-building.md:22
msgid "`matrix-dimension`"
msgstr ""
#: ../../../docs/self-building.md:23
msgid "`matrix-ma1sd`"
msgstr ""
#: ../../../docs/self-building.md:24
msgid "`exim-relay`"
msgstr ""
#: ../../../docs/self-building.md:25
msgid "`matrix-bridge-hookshot`"
msgstr ""
#: ../../../docs/self-building.md:26
msgid "`matrix-bridge-appservice-irc`"
msgstr ""
#: ../../../docs/self-building.md:27
msgid "`matrix-bridge-appservice-slack`"
msgstr ""
#: ../../../docs/self-building.md:28
msgid "`matrix-bridge-appservice-webhooks`"
msgstr ""
#: ../../../docs/self-building.md:29
msgid "`matrix-bridge-beeper-linkedin`"
msgid "`matrix-ketesa`"
msgstr ""
#: ../../../docs/self-building.md:30
msgid "`matrix-bridge-mautrix-facebook`"
msgid "`matrix-client-element`"
msgstr ""
#: ../../../docs/self-building.md:31
msgid "`matrix-bridge-mautrix-hangouts`"
msgid "`hydrogen`"
msgstr ""
#: ../../../docs/self-building.md:32
msgid "`matrix-bridge-mautrix-googlechat`"
msgid "`cinny`"
msgstr ""
#: ../../../docs/self-building.md:33
msgid "`matrix-bridge-mautrix-telegram`"
msgid "`sable`"
msgstr ""
#: ../../../docs/self-building.md:34
msgid "`matrix-bridge-mautrix-signal`"
msgid "`matrix-registration`"
msgstr ""
#: ../../../docs/self-building.md:35
msgid "`matrix-bridge-mautrix-gmessages`"
msgid "`coturn`"
msgstr ""
#: ../../../docs/self-building.md:36
msgid "`matrix-bridge-mautrix-whatsapp`"
msgid "`matrix-corporal`"
msgstr ""
#: ../../../docs/self-building.md:37
msgid "`matrix-bridge-mx-puppet-steam`"
msgid "`exim-relay`"
msgstr ""
#: ../../../docs/self-building.md:38
msgid "`matrix-bot-mjolnir`"
msgid "`matrix-bridge-hookshot`"
msgstr ""
#: ../../../docs/self-building.md:39
msgid "`matrix-bot-honoroit`"
msgid "`matrix-bridge-appservice-irc`"
msgstr ""
#: ../../../docs/self-building.md:40
msgid "`matrix-bot-matrix-reminder-bot`"
msgid "`matrix-bridge-beeper-linkedin`"
msgstr ""
#: ../../../docs/self-building.md:41
msgid "`matrix-bot-maubot`"
msgid "`matrix-bridge-mautrix-googlechat`"
msgstr ""
#: ../../../docs/self-building.md:42
msgid "`matrix-email2matrix`"
msgid "`matrix-bridge-mautrix-telegram`"
msgstr ""
#: ../../../docs/self-building.md:43
msgid "`matrix-pantalaimon`"
msgid "`matrix-bridge-mautrix-signal`"
msgstr ""
#: ../../../docs/self-building.md:44
msgid "`matrix-bridge-mautrix-gmessages`"
msgstr ""
#: ../../../docs/self-building.md:45
msgid "Adding self-building support to other roles is welcome. Feel free to contribute!"
msgid "`matrix-bridge-mautrix-whatsapp`"
msgstr ""
#: ../../../docs/self-building.md:46
msgid "`matrix-bridge-mx-puppet-steam`"
msgstr ""
#: ../../../docs/self-building.md:47
msgid "`matrix-bot-mjolnir`"
msgstr ""
#: ../../../docs/self-building.md:48
msgid "`matrix-bot-honoroit`"
msgstr ""
#: ../../../docs/self-building.md:49
msgid "`matrix-bot-matrix-reminder-bot`"
msgstr ""
#: ../../../docs/self-building.md:50
msgid "`matrix-bot-maubot`"
msgstr ""
#: ../../../docs/self-building.md:51
msgid "`matrix-pantalaimon`"
msgstr ""
#: ../../../docs/self-building.md:53
msgid "Adding self-building support to other roles is welcome. Feel free to contribute!"
msgstr ""
#: ../../../docs/self-building.md:55
msgid "If you'd like **to force self-building** even if an image is available for your architecture, look into the `matrix_*_self_build` variables provided by individual roles."
msgstr ""
File diff suppressed because it is too large Load Diff
+141 -157
View File
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:59+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,10 +18,10 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../README.md:1
msgid "[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)"
msgid "[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com&fetchMode=summary)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate) [![REUSE status](https://api.reuse.software/badge/github.com/spantaleev/matrix-docker-ansible-deploy)](https://api.reuse.software/info/github.com/spantaleev/matrix-docker-ansible-deploy)"
msgstr ""
#: ../../../README.md:1
@@ -32,6 +32,10 @@ msgstr ""
msgid "donate"
msgstr ""
#: ../../../README.md:1
msgid "REUSE status"
msgstr ""
#: ../../../README.md:3
msgid "Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker"
msgstr ""
@@ -177,15 +181,15 @@ msgid "[Link](docs/configuring-playbook-conduit.md)"
msgstr ""
#: ../../../README.md
msgid "[conduwuit](https://conduwuit.puppyirl.gay/)"
msgid "[continuwuity](https://continuwuity.org)"
msgstr ""
#: ../../../README.md
msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit is a fork of Conduit."
msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network."
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-conduwuit.md)"
msgid "[Link](docs/configuring-playbook-continuwuity.md)"
msgstr ""
#: ../../../README.md
@@ -244,6 +248,14 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-client-cinny.md)"
msgstr ""
#: ../../../README.md
msgid "[Sable](https://github.com/7w1/sable)"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-client-sable.md)"
msgstr ""
#: ../../../README.md
msgid "[SchildiChat Web](https://schildi.chat/)"
msgstr ""
@@ -256,11 +268,23 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-client-schildichat-web.md)"
msgstr ""
#: ../../../README.md:69
msgid "Server Components"
#: ../../../README.md
msgid "[FluffyChat Web](https://fluffychat.im/)"
msgstr ""
#: ../../../README.md
msgid "The cutest messenger in Matrix"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-client-fluffychat-web.md)"
msgstr ""
#: ../../../README.md:71
msgid "Server Components"
msgstr ""
#: ../../../README.md:73
msgid "Services that run on the server to make the various parts of your installation work."
msgstr ""
@@ -276,24 +300,12 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-external-postgres.md)"
msgstr ""
#: ../../../README.md
msgid "[coturn](https://github.com/coturn/coturn)"
msgstr ""
#: ../../../README.md
msgid "STUN/TURN server for WebRTC audio/video calls"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-turn.md)"
msgstr ""
#: ../../../README.md
msgid "[Traefik](https://doc.traefik.io/traefik/)"
msgstr ""
#: ../../../README.md
msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](docs/configuring-playbook-own-webserver.md)"
msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. [Using your own webserver](docs/configuring-playbook-own-webserver.md) is also possible."
msgstr ""
#: ../../../README.md
@@ -325,15 +337,15 @@ msgid "[Link](docs/configuring-playbook-email.md)"
msgstr ""
#: ../../../README.md
msgid "[ma1sd](https://github.com/ma1uta/ma1sd)"
msgid "[coturn](https://github.com/coturn/coturn)"
msgstr ""
#: ../../../README.md
msgid "Matrix Identity Server"
msgid "STUN/TURN server for WebRTC audio/video calls"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-ma1sd.md)"
msgid "[Link](docs/configuring-playbook-turn.md)"
msgstr ""
#: ../../../README.md
@@ -348,11 +360,23 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-dynamic-dns.md)"
msgstr ""
#: ../../../README.md:83
msgid "Authentication"
#: ../../../README.md
msgid "Matrix RTC stack"
msgstr ""
#: ../../../README.md
msgid "Supporting components ([LiveKit Server](docs/configuring-playbook-livekit-server.md) and [LiveKit JWT Service](docs/configuring-playbook-livekit-jwt-service.md)) for in-app audio/video calls for Matrix clients"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-matrix-rtc.md)"
msgstr ""
#: ../../../README.md:85
msgid "Authentication"
msgstr ""
#: ../../../README.md:87
msgid "Extend and modify how users are authenticated on your homeserver."
msgstr ""
@@ -397,7 +421,7 @@ msgid "[matrix-ldap-registration-proxy](https://gitlab.com/activism.internationa
msgstr ""
#: ../../../README.md
msgid "A proxy that handles Matrix registration requests and forwards them to LDAP."
msgid "Proxy that handles Matrix registration requests and forwards them to LDAP"
msgstr ""
#: ../../../README.md
@@ -409,7 +433,7 @@ msgid "[matrix-registration](https://github.com/ZerataX/matrix-registration)"
msgstr ""
#: ../../../README.md
msgid "A simple python application to have a token based Matrix registration"
msgid "Simple python application to have a token based Matrix registration"
msgstr ""
#: ../../../README.md
@@ -417,7 +441,7 @@ msgid "[Link](docs/configuring-playbook-matrix-registration.md)"
msgstr ""
#: ../../../README.md
msgid "[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (UVS)"
msgid "[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service)"
msgstr ""
#: ../../../README.md
@@ -433,18 +457,18 @@ msgid "[synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispa
msgstr ""
#: ../../../README.md
msgid "A spam checker module"
msgid "Spam checker module"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-synapse-simple-antispam.md)"
msgstr ""
#: ../../../README.md:97
#: ../../../README.md:99
msgid "File Storage"
msgstr ""
#: ../../../README.md:99
#: ../../../README.md:101
msgid "Use alternative file storage to the default `media_store` folder."
msgstr ""
@@ -473,18 +497,18 @@ msgid "[matrix-media-repo](https://github.com/turt2live/matrix-media-repo)"
msgstr ""
#: ../../../README.md
msgid "matrix-media-repo is a highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
msgid "Highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-matrix-media-repo.md)"
msgstr ""
#: ../../../README.md:107
#: ../../../README.md:109
msgid "Bridges"
msgstr ""
#: ../../../README.md:109
#: ../../../README.md:111
msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
msgstr ""
@@ -560,6 +584,18 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-bridge-mautrix-wsproxy.md)"
msgstr ""
#: ../../../README.md
msgid "[mautrix-bluesky](https://github.com/mautrix/bluesky)"
msgstr ""
#: ../../../README.md
msgid "Bridge to [Bluesky](https://bsky.social/)"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-bridge-mautrix-bluesky.md)"
msgstr ""
#: ../../../README.md
msgid "[mautrix-twitter](https://github.com/mautrix/twitter)"
msgstr ""
@@ -656,14 +692,6 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-bridge-appservice-discord.md)"
msgstr ""
#: ../../../README.md
msgid "[matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack)"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-bridge-appservice-slack.md)"
msgstr ""
#: ../../../README.md
msgid "[matrix-hookshot](https://github.com/matrix-org/matrix-hookshot)"
msgstr ""
@@ -688,6 +716,18 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-bridge-matrix-bridge-sms.md)"
msgstr ""
#: ../../../README.md
msgid "[matrix-steam-bridge](https://github.com/jasonlaguidice/matrix-steam-bridge)"
msgstr ""
#: ../../../README.md
msgid "Bridge to [Steam](https://steampowered.com/)"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-bridge-steam.md)"
msgstr ""
#: ../../../README.md
msgid "[matrix-wechat](https://github.com/duo/matrix-wechat)"
msgstr ""
@@ -712,62 +752,6 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-bridge-heisenbridge.md)"
msgstr ""
#: ../../../README.md
msgid "[go-skype-bridge](https://github.com/kelaresg/go-skype-bridge)"
msgstr ""
#: ../../../README.md
msgid "Bridge to [Skype](https://www.skype.com)"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-bridge-go-skype-bridge.md)"
msgstr ""
#: ../../../README.md
msgid "[mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack)"
msgstr ""
#: ../../../README.md
msgid "Bridge to [Slack](https://slack.com)"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-slack.md)"
msgstr ""
#: ../../../README.md
msgid "[mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram)"
msgstr ""
#: ../../../README.md
msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-instagram.md)"
msgstr ""
#: ../../../README.md
msgid "[mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter)"
msgstr ""
#: ../../../README.md
msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-twitter.md)"
msgstr ""
#: ../../../README.md
msgid "[mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord)"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-discord.md)"
msgstr ""
#: ../../../README.md
msgid "[mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme)"
msgstr ""
@@ -781,7 +765,7 @@ msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-groupme.md)"
msgstr ""
#: ../../../README.md
msgid "[mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam)"
msgid "[mx-puppet-steam](https://codeberg.org/icewind/mx-puppet-steam)"
msgstr ""
#: ../../../README.md
@@ -804,11 +788,11 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-bridge-postmoogle.md)"
msgstr ""
#: ../../../README.md:141
#: ../../../README.md:139
msgid "Bots"
msgstr ""
#: ../../../README.md:143
#: ../../../README.md:141
msgid "Bots provide various additional functionality to your installation."
msgstr ""
@@ -817,7 +801,7 @@ msgid "[baibot](https://github.com/etkecc/baibot)"
msgstr ""
#: ../../../README.md
msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
msgid "Bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
msgstr ""
#: ../../../README.md
@@ -853,7 +837,7 @@ msgid "[maubot](https://github.com/maubot/maubot)"
msgstr ""
#: ../../../README.md
msgid "A plugin-based Matrix bot system"
msgid "Plugin-based Matrix bot system"
msgstr ""
#: ../../../README.md
@@ -865,7 +849,7 @@ msgid "[Honoroit](https://github.com/etkecc/honoroit)"
msgstr ""
#: ../../../README.md
msgid "A helpdesk bot"
msgid "Helpdesk bot"
msgstr ""
#: ../../../README.md
@@ -877,7 +861,7 @@ msgid "[Mjolnir](https://github.com/matrix-org/mjolnir)"
msgstr ""
#: ../../../README.md
msgid "A moderation tool for Matrix"
msgid "Moderation tool for Matrix"
msgstr ""
#: ../../../README.md
@@ -889,7 +873,7 @@ msgid "[Draupnir](https://github.com/the-draupnir-project/Draupnir)"
msgstr ""
#: ../../../README.md
msgid "A moderation tool for Matrix (Fork of Mjolnir)"
msgid "Moderation tool for Matrix (Fork of Mjolnir)"
msgstr ""
#: ../../../README.md
@@ -908,11 +892,11 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-bot-buscarron.md)"
msgstr ""
#: ../../../README.md:156
#: ../../../README.md:154
msgid "Administration"
msgstr ""
#: ../../../README.md:158
#: ../../../README.md:156
msgid "Services that help you in administrating and monitoring your Matrix installation."
msgstr ""
@@ -941,15 +925,15 @@ msgid "[Link](docs/configuring-playbook-matrix-authentication-service.md)"
msgstr ""
#: ../../../README.md
msgid "[synapse-admin](https://github.com/etkecc/synapse-admin)"
msgid "[Ketesa](https://github.com/etkecc/ketesa)"
msgstr ""
#: ../../../README.md
msgid "A web UI tool for administrating users and rooms on your Matrix server"
msgid "Fully-featured web UI for administrating your Matrix homeserver — users, rooms, media, sessions, and more"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-synapse-admin.md)"
msgid "[Link](docs/configuring-playbook-ketesa.md)"
msgstr ""
#: ../../../README.md
@@ -961,7 +945,7 @@ msgid "Consists of the [Prometheus](https://prometheus.io) time-series database
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-nginxlog.md))"
msgid "[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-nginx-logs-optional))"
msgstr ""
#: ../../../README.md
@@ -1000,44 +984,20 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-synapse-usage-exporter.md)"
msgstr ""
#: ../../../README.md:170
#: ../../../README.md:168
msgid "Misc"
msgstr ""
#: ../../../README.md:172
#: ../../../README.md:170
msgid "Various services that don't fit any other categories."
msgstr ""
#: ../../../README.md
msgid "[sliding-sync](https://github.com/matrix-org/sliding-sync)"
msgstr ""
#: ../../../README.md
msgid "(Superseded by Simplified Sliding Sync integrated into Synapse > `1.114` and Conduit > `0.6.0`) Sliding Sync support for clients which require it (e.g. old Element X versions before Simplified Sliding Sync was developed)"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-sliding-sync-proxy.md)"
msgstr ""
#: ../../../README.md
msgid "[synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-accept-invite)"
msgstr ""
#: ../../../README.md
msgid "A Synapse module to automatically accept invites."
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-synapse-auto-accept-invite.md)"
msgstr ""
#: ../../../README.md
msgid "[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor)"
msgstr ""
#: ../../../README.md
msgid "A cli tool that automatically compresses `state_groups` database table in background."
msgid "Cli tool that automatically compresses `state_groups` database table in background"
msgstr ""
#: ../../../README.md
@@ -1056,12 +1016,24 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-matrix-corporal.md)"
msgstr ""
#: ../../../README.md
msgid "[Matrix.to](https://github.com/matrix-org/matrix.to)"
msgstr ""
#: ../../../README.md
msgid "Simple URL redirection service for the Matrix ecosystem"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-matrixto.md)"
msgstr ""
#: ../../../README.md
msgid "[Etherpad](https://etherpad.org)"
msgstr ""
#: ../../../README.md
msgid "An open source collaborative text editor"
msgid "Open source collaborative text editor"
msgstr ""
#: ../../../README.md
@@ -1073,7 +1045,7 @@ msgid "[Jitsi](https://jitsi.org/)"
msgstr ""
#: ../../../README.md
msgid "An open source video-conferencing platform"
msgid "Open source video-conferencing platform"
msgstr ""
#: ../../../README.md
@@ -1085,7 +1057,7 @@ msgid "[Cactus Comments](https://cactus.chat)"
msgstr ""
#: ../../../README.md
msgid "A federated comment system built on Matrix"
msgid "Federated comment system built on Matrix"
msgstr ""
#: ../../../README.md
@@ -1097,7 +1069,7 @@ msgid "[Pantalaimon](https://github.com/matrix-org/pantalaimon)"
msgstr ""
#: ../../../README.md
msgid "An E2EE aware proxy daemon"
msgid "E2EE aware proxy daemon"
msgstr ""
#: ../../../README.md
@@ -1128,54 +1100,66 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-ntfy.md)"
msgstr ""
#: ../../../README.md:187
#: ../../../README.md
msgid "[Element Call](https://github.com/element-hq/element-call)"
msgstr ""
#: ../../../README.md
msgid "A native Matrix video conferencing application"
msgstr ""
#: ../../../README.md
msgid "[Link](docs/configuring-playbook-element-call.md)"
msgstr ""
#: ../../../README.md:185
msgid "🆕 Changes"
msgstr ""
#: ../../../README.md:189
#: ../../../README.md:187
msgid "This playbook evolves over time, sometimes with backward-incompatible changes."
msgstr ""
#: ../../../README.md:191
#: ../../../README.md:189
msgid "When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up with what's new."
msgstr ""
#: ../../../README.md:193
#: ../../../README.md:191
msgid "🆘 Support"
msgstr ""
#: ../../../README.md:195
#: ../../../README.md:193
msgid "Matrix room: [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)"
msgstr ""
#: ../../../README.md:197
#: ../../../README.md:195
msgid "IRC channel: `#matrix-docker-ansible-deploy` on the [Libera Chat](https://libera.chat/) IRC network (irc.libera.chat:6697)"
msgstr ""
#: ../../../README.md:199
#: ../../../README.md:197
msgid "GitHub issues: [spantaleev/matrix-docker-ansible-deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues)"
msgstr ""
#: ../../../README.md:201
#: ../../../README.md:199
msgid "🌐 Translation"
msgstr ""
#: ../../../README.md:203
#: ../../../README.md:201
msgid "See the [i18n/README.md](i18n/README.md) file for more information about translation."
msgstr ""
#: ../../../README.md:205
#: ../../../README.md:203
msgid "Translations are still work in progress."
msgstr ""
#: ../../../README.md:207
#: ../../../README.md:205
msgid "🤝 Related"
msgstr ""
#: ../../../README.md:209
#: ../../../README.md:207
msgid "You may also be interested in [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) - another Ansible playbook for self-hosting non-Matrix services (see its [List of supported services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md))."
msgstr ""
#: ../../../README.md:211
#: ../../../README.md:209
msgid "mash-playbook also makes use of [Traefik](./docs/configuring-playbook-traefik.md) as its reverse-proxy, so with minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md), you can make matrix-docker-ansible-deploy and mash-playbook co-exist and host Matrix and non-Matrix services on the same server."
msgstr ""
+45 -45
View File
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,156 +18,156 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/README.md:1
#: ../../../docs/README.md:10
msgid "Table of Contents"
msgstr ""
#: ../../../docs/README.md:3
msgid "⬇️ Installaton guides <!-- NOTE: the 🚀 emoji is used by \"Getting started\" on README.md -->"
#: ../../../docs/README.md:12
msgid "⬇️ Installation guides <!-- NOTE: the 🚀 emoji is used by \"Getting started\" on README.md -->"
msgstr ""
#: ../../../docs/README.md:5
#: ../../../docs/README.md:14
msgid "There are two installation guides available for beginners and advanced users."
msgstr ""
#: ../../../docs/README.md:7
#: ../../../docs/README.md:16
msgid "⚡ **[Quick start](quick-start.md) (for beginners)**: this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"."
msgstr ""
#: ../../../docs/README.md:9
#: ../../../docs/README.md:18
msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide."
msgstr ""
#: ../../../docs/README.md:11
#: ../../../docs/README.md:20
msgid "[Prerequisites](prerequisites.md)"
msgstr ""
#: ../../../docs/README.md:13
msgid "[Configuring your DNS settings](configuring-dns.md)"
#: ../../../docs/README.md:22
msgid "[Configuring DNS settings](configuring-dns.md)"
msgstr ""
#: ../../../docs/README.md:15
#: ../../../docs/README.md:24
msgid "[Getting the playbook](getting-the-playbook.md)"
msgstr ""
#: ../../../docs/README.md:17
#: ../../../docs/README.md:26
msgid "[Configuring the playbook](configuring-playbook.md)"
msgstr ""
#: ../../../docs/README.md:19
#: ../../../docs/README.md:28
msgid "[Installing](installing.md)"
msgstr ""
#: ../../../docs/README.md:21
#: ../../../docs/README.md:30
msgid "🛠️ Configuration options"
msgstr ""
#: ../../../docs/README.md:28
#: ../../../docs/README.md:37
msgid "You can check useful documentation for configuring components here: [Configuring the playbook](configuring-playbook.md)"
msgstr ""
#: ../../../docs/README.md:30
#: ../../../docs/README.md:39
msgid "[Administration](configuring-playbook.md#administration) — services that help you in administrating and monitoring your Matrix installation"
msgstr ""
#: ../../../docs/README.md:32
#: ../../../docs/README.md:41
msgid "[Authentication and user-related](configuring-playbook.md#authentication-and-user-related) — extend and modify how users are authenticated on your homeserver"
msgstr ""
#: ../../../docs/README.md:34
#: ../../../docs/README.md:43
msgid "[Bots](configuring-playbook.md#bots) — bots provide various additional functionality to your installation"
msgstr ""
#: ../../../docs/README.md:36
#: ../../../docs/README.md:45
msgid "[Bridges](configuring-playbook.md#bridging-other-networks) — bridges can be used to connect your Matrix installation with third-party communication networks"
msgstr ""
#: ../../../docs/README.md:38
#: ../../../docs/README.md:47
msgid "[Clients](configuring-playbook.md#clients) — web clients for Matrix that you can host on your own domains"
msgstr ""
#: ../../../docs/README.md:40
#: ../../../docs/README.md:49
msgid "[Core service adjustments](configuring-playbook.md#core-service-adjustments) — backbone of your Matrix system"
msgstr ""
#: ../../../docs/README.md:42
#: ../../../docs/README.md:51
msgid "[File Storage](configuring-playbook.md#file-storage) — use alternative file storage to the default `media_store` folder"
msgstr ""
#: ../../../docs/README.md:46
#: ../../../docs/README.md:55
msgid "[Other specialized services](configuring-playbook.md#other-specialized-services) — various services that don't fit any other categories"
msgstr ""
#: ../../../docs/README.md:48
#: ../../../docs/README.md:57
msgid "👨‍🔧 Maintenance"
msgstr ""
#: ../../../docs/README.md:50
#: ../../../docs/README.md:59
msgid "If your server and services experience issues, feel free to come to [our support room](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) and ask for help."
msgstr ""
#: ../../../docs/README.md:54
msgid "[Checking if services work](maintenance-checking-services.md)"
msgstr ""
#: ../../../docs/README.md:56
#: ../../../docs/README.md:63
msgid "[Maintenance and Troubleshooting](maintenance-and-troubleshooting.md)"
msgstr ""
#: ../../../docs/README.md:58
#: ../../../docs/README.md:65
msgid "[PostgreSQL maintenance](maintenance-postgres.md)"
msgstr ""
#: ../../../docs/README.md:60
#: ../../../docs/README.md:67
msgid "[Synapse maintenance](maintenance-synapse.md)"
msgstr ""
#: ../../../docs/README.md:62
#: ../../../docs/README.md:69
msgid "[Upgrading services](maintenance-upgrading-services.md)"
msgstr ""
#: ../../../docs/README.md:64
#: ../../../docs/README.md:71
msgid "Other documentation pages <!-- NOTE: this header's title and the section below need optimization -->"
msgstr ""
#: ../../../docs/README.md:66
#: ../../../docs/README.md:73
msgid "️ **[FAQ](faq.md)** — various Frequently Asked Questions about Matrix, with a focus on this Ansible playbook"
msgstr ""
#: ../../../docs/README.md:70
#: ../../../docs/README.md:77
msgid "[Alternative architectures](alternative-architectures.md)"
msgstr ""
#: ../../../docs/README.md:72
#: ../../../docs/README.md:79
msgid "[Container images used by the playbook](container-images.md)"
msgstr ""
#: ../../../docs/README.md:74
#: ../../../docs/README.md:81
msgid "[Obtaining an Access Token](obtaining-access-tokens.md)"
msgstr ""
#: ../../../docs/README.md:76
#: ../../../docs/README.md:83
msgid "[Playbook tags](playbook-tags.md)"
msgstr ""
#: ../../../docs/README.md:78
#: ../../../docs/README.md:85
msgid "[Registering users](registering-users.md)"
msgstr ""
#: ../../../docs/README.md:80
#: ../../../docs/README.md:87
msgid "[Running `just` commands](just.md)"
msgstr ""
#: ../../../docs/README.md:82
#: ../../../docs/README.md:89
msgid "[Self-building](self-building.md)"
msgstr ""
#: ../../../docs/README.md:84
#: ../../../docs/README.md:91
msgid "[Uninstalling](uninstalling.md)"
msgstr ""
#: ../../../docs/README.md:86
#: ../../../docs/README.md:93
msgid "[Updating users passwords](updating-users-passwords.md)"
msgstr ""
#: ../../../docs/README.md:95
msgid "[Using Ansible for the playbook](ansible.md)"
msgstr ""
@@ -162,7 +162,7 @@ msgid "Granting Users the ability to use D4A"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:97
msgid "Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recomendation. Using the chat is recomended."
msgid "Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recomendation. Using the chat is recommended."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:99
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,431 +18,459 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bot-baibot.md:1
#: ../../../docs/configuring-playbook-bot-baibot.md:8
msgid "Setting up baibot (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:8
#: ../../../docs/configuring-playbook-bot-baibot.md:15
msgid "🤖 [baibot](https://github.com/etkecc/baibot) (pronounced bye-bot) is a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:10
#: ../../../docs/configuring-playbook-bot-baibot.md:17
msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as many well as other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:12
#: ../../../docs/configuring-playbook-bot-baibot.md:19
msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to [matrix-chatgpt-bot](./configuring-playbook-bot-chatgpt.md). See the [baibot](https://github.com/etkecc/baibot) project and its documentation for more information."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:14
#: ../../../docs/configuring-playbook-bot-baibot.md:21
msgid "Prerequisites"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:16
#: ../../../docs/configuring-playbook-bot-baibot.md:23
msgid "API access to one or more LLM [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:18
#: ../../../docs/configuring-playbook-bot-baibot.md:25
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:20
#: ../../../docs/configuring-playbook-bot-baibot.md:27
msgid "There are **a lot of configuration options** (some required, some possibly required, some optional), so they're **split into multiple sections below**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:23
#: ../../../docs/configuring-playbook-bot-baibot.md:30
msgid "[Base configuration](#base-configuration)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:24
#: ../../../docs/configuring-playbook-bot-baibot.md:31
msgid "[👮‍♂️ Administrator configuration](#-administrator-configuration)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:25
#: ../../../docs/configuring-playbook-bot-baibot.md:32
msgid "[👥 Initial users configuration](#-initial-users-configuration)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:26
#: ../../../docs/configuring-playbook-bot-baibot.md:33
msgid "[🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:27
#: ../../../docs/configuring-playbook-bot-baibot.md:34
msgid "[🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:29
#: ../../../docs/configuring-playbook-bot-baibot.md:36
msgid "Depending on your current `vars.yml` file and desired configuration, **you may require more than just the [base configuration](#base-configuration)**."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:31
#: ../../../docs/configuring-playbook-bot-baibot.md:38
msgid "Base configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:33
#: ../../../docs/configuring-playbook-bot-baibot.md:40
msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:71
msgid "As mentioned above, **this may not be enough**. Continue with the configuration sections below."
#: ../../../docs/configuring-playbook-bot-baibot.md:42
msgid "Authentication can be configured in one of two mutually-exclusive ways:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:73
msgid "👮‍♂️ Administrator configuration"
#: ../../../docs/configuring-playbook-bot-baibot.md:44
msgid "**Password authentication** (`matrix_bot_baibot_config_user_password`) - recommended for most playbook-managed setups, because it integrates with automatic user creation flow used by the playbook, and auto-creates the bot account"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:75
#: ../../../docs/configuring-playbook-bot-baibot.md:99
msgid "This is an addition to the [base configuration](#base-configuration)."
#: ../../../docs/configuring-playbook-bot-baibot.md:45
msgid "**Access-token authentication** (`matrix_bot_baibot_config_user_access_token` + `matrix_bot_baibot_config_user_device_id`) - useful for specific [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md)/OIDC setups where password authentication is not available or not desired"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:77
msgid "To specify who is considered a bot [👮‍♂️ Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators), you either need to specify `matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The latter is a single variable which affects all bridges and bots."
#: ../../../docs/configuring-playbook-bot-baibot.md:47
msgid "Even when [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) is enabled, password authentication is still typically the best fit for baibot if you're using a playbook-managed bot account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:79
msgid "If `matrix_admin` is already configured in your `vars.yml` configuration, you can skip this section."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:81
#: ../../../docs/configuring-playbook-bot-baibot.md:110
msgid "**If necessary**, add the following configuration to your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:95
msgid "👥 Initial users configuration"
#: ../../../docs/configuring-playbook-bot-baibot.md:49
msgid "For upstream details, see baibot's [🔐 Authentication](https://github.com/etkecc/baibot/blob/main/docs/configuration/authentication.md) documentation."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:97
msgid "By default, **all users on your homeserver are considered allowed users**. If that's OK, you can skip this section."
msgid "As mentioned above, **this may not be enough**. Continue with the configuration sections below."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:99
msgid "👮‍♂️ Administrator configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:101
msgid "To specify who is considered a bot [👥 User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), you may:"
#: ../../../docs/configuring-playbook-bot-baibot.md:125
msgid "This is an addition to the [base configuration](#base-configuration)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:103
msgid "To specify who is considered a bot [👮‍♂️ Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators), you either need to specify `matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The latter is a single variable which affects all bridges and bots."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:105
msgid "If `matrix_admin` is already configured in your `vars.yml` configuration, you can skip this section."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:107
#: ../../../docs/configuring-playbook-bot-baibot.md:136
msgid "**If necessary**, add the following configuration to your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:121
msgid "👥 Initial users configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:123
msgid "By default, **all users on your homeserver are considered allowed users**. If that's OK, you can skip this section."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:127
msgid "To specify who is considered a bot [👥 User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), you may:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:129
msgid "define an **initial** value for `matrix_bot_baibot_config_initial_global_config_user_patterns` Ansible variable, as shown below"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:104
#: ../../../docs/configuring-playbook-bot-baibot.md:130
msgid "configure the list at runtime via the bot's `!bai access set-users SPACE_SEPARATED_PATTERNS` command"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:106
#: ../../../docs/configuring-playbook-bot-baibot.md:132
msgid "Configuring `matrix_bot_baibot_config_initial_global_config_user_patterns` is optional, but it can be useful to pre-configure the bot with a list of users who should have access to the bot's features."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:108
#: ../../../docs/configuring-playbook-bot-baibot.md:134
msgid "**Note**: Once initially configured, the allowed users list **cannot be managed via Ansible anymore**. It can only be managed subsequently via bot commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:122
#: ../../../docs/configuring-playbook-bot-baibot.md:148
msgid "🤖 Configuring agents via Ansible"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:124
#: ../../../docs/configuring-playbook-bot-baibot.md:150
msgid "You are **not required** to define agents [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration) via Ansible. **To get started quickly**, you can **skip this section and define agents at runtime via chat commands** (following the bot's guidance)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:126
#: ../../../docs/configuring-playbook-bot-baibot.md:152
msgid "Privileged users (like the [👮‍♂️ Administrator](#-administrator-configuration), but potentially others too — see the upstream [🔒 access](https://github.com/etkecc/baibot/blob/main/docs/access.md) documentation) can **define agents dynamically at any time** via chat commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:128
#: ../../../docs/configuring-playbook-bot-baibot.md:154
msgid "The Ansible role includes preset variables for easily enabling some [🤖 agents](https://github.com/etkecc/baibot/blob/main/docs/agents.md) on various [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md) (e.g. OpenAI, etc)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:130
#: ../../../docs/configuring-playbook-bot-baibot.md:156
msgid "Besides the presets, the Ansible role also includes support for configuring additional statically-defined agents via the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:132
#: ../../../docs/configuring-playbook-bot-baibot.md:158
msgid "Agents defined statically and those created dynamically (via chat) are named differently, so **conflict cannot arise**."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:134
#: ../../../docs/configuring-playbook-bot-baibot.md:160
msgid "Depending on your propensity for [GitOps](https://en.wikipedia.org/wiki/DevOps#GitOps), you may prefer to define agents statically via Ansible, or you may wish to do it dynamically via chat."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:136
#: ../../../docs/configuring-playbook-bot-baibot.md:162
msgid "Before proceeding, we recommend reading the upstream documentation on [How to choose a provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#how-to-choose-a-provider). In short, it's probably best to go with [OpenAI](#openai)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:138
#: ../../../docs/configuring-playbook-bot-baibot.md:164
msgid "Anthropic"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:140
#: ../../../docs/configuring-playbook-bot-baibot.md:166
msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Anthropic provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic) with the help of the playbook's preset variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:142
#: ../../../docs/configuring-playbook-bot-baibot.md:166
#: ../../../docs/configuring-playbook-bot-baibot.md:197
#: ../../../docs/configuring-playbook-bot-baibot.md:225
#: ../../../docs/configuring-playbook-bot-baibot.md:168
#: ../../../docs/configuring-playbook-bot-baibot.md:192
#: ../../../docs/configuring-playbook-bot-baibot.md:223
#: ../../../docs/configuring-playbook-bot-baibot.md:251
msgid "Here's an example **addition** to your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:158
#: ../../../docs/configuring-playbook-bot-baibot.md:189
#: ../../../docs/configuring-playbook-bot-baibot.md:184
#: ../../../docs/configuring-playbook-bot-baibot.md:215
#: ../../../docs/configuring-playbook-bot-baibot.md:243
#: ../../../docs/configuring-playbook-bot-baibot.md:241
#: ../../../docs/configuring-playbook-bot-baibot.md:275
msgid "If you'd like to use more than one model, take a look at the [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset) section below."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:160
#: ../../../docs/configuring-playbook-bot-baibot.md:191
#: ../../../docs/configuring-playbook-bot-baibot.md:186
#: ../../../docs/configuring-playbook-bot-baibot.md:217
#: ../../../docs/configuring-playbook-bot-baibot.md:245
#: ../../../docs/configuring-playbook-bot-baibot.md:243
#: ../../../docs/configuring-playbook-bot-baibot.md:277
msgid "💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:162
#: ../../../docs/configuring-playbook-bot-baibot.md:188
msgid "Groq"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:164
#: ../../../docs/configuring-playbook-bot-baibot.md:190
msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Groq provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq) with the help of the playbook's preset variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:187
#: ../../../docs/configuring-playbook-bot-baibot.md:213
msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/groq`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:193
#: ../../../docs/configuring-playbook-bot-baibot.md:219
msgid "Mistral"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:195
#: ../../../docs/configuring-playbook-bot-baibot.md:221
msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [🇫🇷 Mistral provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral) with the help of the playbook's preset variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:213
#: ../../../docs/configuring-playbook-bot-baibot.md:239
msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/mistral`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:219
#: ../../../docs/configuring-playbook-bot-baibot.md:245
msgid "OpenAI"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:221
#: ../../../docs/configuring-playbook-bot-baibot.md:247
msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai) with the help of the playbook's preset variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:223
#: ../../../docs/configuring-playbook-bot-baibot.md:249
msgid "The OpenAI provider is **only meant to be used with OpenAI's official API** and compatibility with other services (which do not fully adhere to the OpenAI API spec completely) is limited. **If you're targeting an OpenAI-compatible service**, use the [OpenAI Compatible](#openai-compatible) provider instead."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:241
#: ../../../docs/configuring-playbook-bot-baibot.md:273
msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/openai`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:247
#: ../../../docs/configuring-playbook-bot-baibot.md:279
msgid "OpenAI Compatible"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:249
#: ../../../docs/configuring-playbook-bot-baibot.md:281
msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI Compatible provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai-compatible) with the help of the playbook's preset variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:251
#: ../../../docs/configuring-playbook-bot-baibot.md:283
msgid "This provider allows you to use OpenAI-compatible API services like [OpenRouter](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openrouter), [Together AI](https://github.com/etkecc/baibot/blob/main/docs/providers.md#together-ai), etc."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:253
#: ../../../docs/configuring-playbook-bot-baibot.md:285
msgid "Some of these popular services already have **shortcut** providers (see [supported providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md#supported-providers) leading to this one behind the scenes — this make it easier to get started."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:255
#: ../../../docs/configuring-playbook-bot-baibot.md:287
msgid "As of this moment, the playbook does not include presets for any of these services, so you'll need to [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:257
#: ../../../docs/configuring-playbook-bot-baibot.md:289
msgid "Configuring additional agents (without a preset)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:259
#: ../../../docs/configuring-playbook-bot-baibot.md:291
msgid "The Ansible role may be lacking preset variables for some [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), or you may wish to statically-define an agent on the same provider twice (or more) with different configuration."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:261
#: ../../../docs/configuring-playbook-bot-baibot.md:293
msgid "It's possible to inject your own agent configuration using the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:263
#: ../../../docs/configuring-playbook-bot-baibot.md:295
msgid "You can also define providers at runtime, by chatting with the bot, so using Ansible is not a requirement."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:265
#: ../../../docs/configuring-playbook-bot-baibot.md:297
msgid "Below is an an **example** demonstrating **statically-defining agents via Ansible without using presets**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:304
#: ../../../docs/configuring-playbook-bot-baibot.md:336
msgid "Because these are [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agents, they will be given a `static/` ID prefix and will be named `static/my-openai-gpt-3.5-turbo-agent` and `static/my-ollama-agent`, respectively."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:306
#: ../../../docs/configuring-playbook-bot-baibot.md:338
msgid "💡 To figure out what to put in the `config` section, refer to the [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md) page, which contains **sample configuration YAML for each provider**."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:308
#: ../../../docs/configuring-playbook-bot-baibot.md:340
msgid "As with any [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), defining them means they exist. To actually make use of them, they need to be configured as handlers globally or in a specific room — see [Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:310
#: ../../../docs/configuring-playbook-bot-baibot.md:342
msgid "💡 You may also wish to use these new agents for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:312
#: ../../../docs/configuring-playbook-bot-baibot.md:344
msgid "🤝 Configuring initial default handlers"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:314
#: ../../../docs/configuring-playbook-bot-baibot.md:346
msgid "This section is only useful if you're [🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible), as it lets you put these agents to use as soon as the bot starts (by adjusting the bot's **initial global configuration**)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:316
#: ../../../docs/configuring-playbook-bot-baibot.md:348
msgid "If you're not configuring agents via Ansible, you can skip this section."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:318
#: ../../../docs/configuring-playbook-bot-baibot.md:350
msgid "This section is only useful the first time around. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:320
#: ../../../docs/configuring-playbook-bot-baibot.md:352
msgid "baibot supports [various purposes](https://github.com/etkecc/baibot/blob/main/docs/features.md):"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:322
#: ../../../docs/configuring-playbook-bot-baibot.md:354
msgid "[💬 text-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-generation): communicating with you via text"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:324
#: ../../../docs/configuring-playbook-bot-baibot.md:356
msgid "[🦻 speech-to-text](https://github.com/etkecc/baibot/blob/main/docs/features.md#-speech-to-text): turning your voice messages into text"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:326
#: ../../../docs/configuring-playbook-bot-baibot.md:358
msgid "[🗣️ text-to-speech](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-to-speech): turning bot or users text messages into voice messages"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:328
#: ../../../docs/configuring-playbook-bot-baibot.md:360
msgid "[🖌️ image-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-image-generation): generating images based on instructions"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:330
#: ../../../docs/configuring-playbook-bot-baibot.md:362
msgid "❓ catch-all: special purposes, indicating use as a fallback (when no specific handler is configured)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:332
#: ../../../docs/configuring-playbook-bot-baibot.md:364
msgid "[Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models) is made possible by the bot's ability to have different [🤝 handlers](https://github.com/etkecc/baibot/blob/main/docs/configuration/handlers.md) configured for different purposes."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:334
#: ../../../docs/configuring-playbook-bot-baibot.md:366
msgid "This configuration can be done as a global fallback, or per-room. Both of these [🛠️ configurations](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md) are managed at runtime (viat chat), but **the global configuration can have some initial defaults configured via Ansible**."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:336
#: ../../../docs/configuring-playbook-bot-baibot.md:368
msgid "You can configure the **initial values** for these via Ansible, via the `matrix_bot_baibot_config_initial_global_config_handler_*` variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:338
#: ../../../docs/configuring-playbook-bot-baibot.md:370
msgid "Example **additional** `vars.yml` configuration:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:355
#: ../../../docs/configuring-playbook-bot-baibot.md:387
msgid "**Note**: these are initial defaults for the bot's global configuration. As such, changing any of these values subsequently has no effect on the bot's behavior. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:357
#: ../../../docs/configuring-playbook-bot-baibot.md:389
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:359
#: ../../../docs/configuring-playbook-bot-baibot.md:391
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:361
#: ../../../docs/configuring-playbook-bot-baibot.md:393
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:363
#: ../../../docs/configuring-playbook-bot-baibot.md:395
msgid "`roles/custom/matrix-bot-baibot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:364
#: ../../../docs/configuring-playbook-bot-baibot.md:396
msgid "`roles/custom/matrix-bot-baibot/templates/config.yaml.j2` for the bot's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_bot_baibot_configuration_extension_yaml` variable"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:366
#: ../../../docs/configuring-playbook-bot-baibot.md:398
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:368
#: ../../../docs/configuring-playbook-bot-baibot.md:400
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:375
#: ../../../docs/configuring-playbook-bot-baibot.md:407
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:377
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
#: ../../../docs/configuring-playbook-bot-baibot.md:409
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account when password authentication is used."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:379
#: ../../../docs/configuring-playbook-bot-baibot.md:411
msgid "If you're using access-token authentication, the bot account must already exist and the configured token + device ID must match that account. This mode is mainly for MAS/OIDC setups where password-based bot login is not suitable."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:413
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:381
#: ../../../docs/configuring-playbook-bot-baibot.md:415
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:383
msgid "If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password."
#: ../../../docs/configuring-playbook-bot-baibot.md:417
msgid "If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password. (This note applies to password authentication mode.)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:385
#: ../../../docs/configuring-playbook-bot-baibot.md:419
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:387
#: ../../../docs/configuring-playbook-bot-baibot.md:421
msgid "To use the bot, invite it to any existing Matrix room (`/invite @baibot:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:389
#: ../../../docs/configuring-playbook-bot-baibot.md:423
msgid "If you're an allowed bot [👥 user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) (see [👥 Initial users configuration](#-initial-users-configuration)), the bot will accept your invitation and join the room."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:391
#: ../../../docs/configuring-playbook-bot-baibot.md:425
msgid "After joining, the bot will introduce itself and show information about the [✨ features](https://github.com/etkecc/baibot/blob/main/docs/features.md) that are enabled for it."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:393
#: ../../../docs/configuring-playbook-bot-baibot.md:427
msgid "If you've [🤖 configured one or more agents via Ansible](#-configuring-agents-via-ansible) and have [🤝 configured initial default handlers](#configuring-initial-default-handlers), the bot will immediately be able to make use of these agents for this new room. Otherwise, you will need to configure agents and/or handlers via chat commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:395
#: ../../../docs/configuring-playbook-bot-baibot.md:429
msgid "Send `!bai help` to the bot in the room to see the available commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:397
#: ../../../docs/configuring-playbook-bot-baibot.md:431
msgid "You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) project's documentation."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:399
#: ../../../docs/configuring-playbook-bot-baibot.md:433
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:401
msgid "As with all other services, you can find service logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-bot-baibot`"
#: ../../../docs/configuring-playbook-bot-baibot.md:435
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-baibot`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:403
msgid "The default logging level for this service is `info`, but you can increase it to `debug` (or even `trace`) with the following additional configuration:"
#: ../../../docs/configuring-playbook-bot-baibot.md:437
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:417
#: ../../../docs/configuring-playbook-bot-baibot.md:439
msgid "The default logging level for this service is `info`. If you want to increase the verbosity to `debug` (or even `trace`), add the following configuration to your `vars.yml` file and re-run the playbook:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:453
msgid "**Alternatively**, you can use a single variable to set the logging level for all of the above (bot + all libraries):"
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,156 +18,156 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bot-buscarron.md:1
#: ../../../docs/configuring-playbook-bot-buscarron.md:9
msgid "Setting up Buscarron (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:3
#: ../../../docs/configuring-playbook-bot-buscarron.md:11
msgid "The playbook can install and configure [Buscarron](https://github.com/etkecc/buscarron) for you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:5
#: ../../../docs/configuring-playbook-bot-buscarron.md:13
msgid "Buscarron is bot that receives HTTP POST submissions of web forms and forwards them to a Matrix room."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:7
#: ../../../docs/configuring-playbook-bot-buscarron.md:15
msgid "See the project's [documentation](https://github.com/etkecc/buscarron/blob/main/README.md) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:9
#: ../../../docs/configuring-playbook-bot-buscarron.md:17
msgid "Adjusting DNS records"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:11
#: ../../../docs/configuring-playbook-bot-buscarron.md:19
msgid "By default, this playbook installs Buscarron on the `buscarron.` subdomain (`buscarron.example.com`) and requires you to create a CNAME record for `buscarron`, which targets `matrix.example.com`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:13
#: ../../../docs/configuring-playbook-bot-buscarron.md:21
msgid "When setting, replace `example.com` with your own."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:15
#: ../../../docs/configuring-playbook-bot-buscarron.md:23
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:17
#: ../../../docs/configuring-playbook-bot-buscarron.md:25
msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:40
#: ../../../docs/configuring-playbook-bot-buscarron.md:48
msgid "Adjusting the Buscarron URL (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:42
#: ../../../docs/configuring-playbook-bot-buscarron.md:50
msgid "By tweaking the `matrix_bot_buscarron_hostname` and `matrix_bot_buscarron_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:44
#: ../../../docs/configuring-playbook-bot-buscarron.md:52
msgid "Example additional configuration for your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:55
#: ../../../docs/configuring-playbook-bot-buscarron.md:63
msgid "After changing the domain, **you may need to adjust your DNS** records to point the Buscarron domain to the Matrix server."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:57
#: ../../../docs/configuring-playbook-bot-buscarron.md:65
msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:59
#: ../../../docs/configuring-playbook-bot-buscarron.md:67
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:61
#: ../../../docs/configuring-playbook-bot-buscarron.md:69
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:63
#: ../../../docs/configuring-playbook-bot-buscarron.md:71
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:65
#: ../../../docs/configuring-playbook-bot-buscarron.md:73
msgid "`roles/custom/matrix-bot-buscarron/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:67
#: ../../../docs/configuring-playbook-bot-buscarron.md:75
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:69
#: ../../../docs/configuring-playbook-bot-buscarron.md:77
msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:76
#: ../../../docs/configuring-playbook-bot-buscarron.md:84
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:78
#: ../../../docs/configuring-playbook-bot-buscarron.md:86
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:80
#: ../../../docs/configuring-playbook-bot-buscarron.md:88
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:82
#: ../../../docs/configuring-playbook-bot-buscarron.md:90
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:84
msgid "If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password."
#: ../../../docs/configuring-playbook-bot-buscarron.md:92
msgid "If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:86
#: ../../../docs/configuring-playbook-bot-buscarron.md:94
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:88
#: ../../../docs/configuring-playbook-bot-buscarron.md:96
msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.buscarron:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:90
#: ../../../docs/configuring-playbook-bot-buscarron.md:98
msgid "After the bot joins the room, anyone can call the web form via HTTP POST method."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:92
#: ../../../docs/configuring-playbook-bot-buscarron.md:100
msgid "Here is an example for the `contact` form:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:100
#: ../../../docs/configuring-playbook-bot-buscarron.md:108
msgid "**Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:102
#: ../../../docs/configuring-playbook-bot-buscarron.md:110
msgid "you hit the homepage (HTTP `GET` request to `/`)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:103
#: ../../../docs/configuring-playbook-bot-buscarron.md:111
msgid "you submit a form to the wrong URL (`POST` request to `/non-existing-form`)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:104
#: ../../../docs/configuring-playbook-bot-buscarron.md:112
msgid "`hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:106
#: ../../../docs/configuring-playbook-bot-buscarron.md:114
msgid "If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:108
#: ../../../docs/configuring-playbook-bot-buscarron.md:116
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:110
#: ../../../docs/configuring-playbook-bot-buscarron.md:118
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-buscarron`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:112
#: ../../../docs/configuring-playbook-bot-buscarron.md:120
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:114
#: ../../../docs/configuring-playbook-bot-buscarron.md:122
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 ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,392 +18,421 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bot-draupnir.md:1
#: ../../../docs/configuring-playbook-bot-draupnir.md:10
msgid "Setting up Draupnir (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:3
#: ../../../docs/configuring-playbook-bot-draupnir.md:12
msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation bot for you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:5
#: ../../../docs/configuring-playbook-bot-draupnir.md:14
msgid "See the project's [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:7
#: ../../../docs/configuring-playbook-bot-draupnir.md:16
msgid "This documentation page is about installing Draupnir in bot mode. As an alternative, you can run a multi-instance Draupnir deployment by installing [Draupnir in appservice mode](./configuring-playbook-appservice-draupnir-for-all.md) (called Draupnir-for-all) instead."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:9
#: ../../../docs/configuring-playbook-bot-draupnir.md:18
msgid "If your 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:11
#: ../../../docs/configuring-playbook-bot-draupnir.md:20
msgid "Prerequisites"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:13
#: ../../../docs/configuring-playbook-bot-draupnir.md:22
msgid "Create a management room"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:15
#: ../../../docs/configuring-playbook-bot-draupnir.md:24
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:17
#: ../../../docs/configuring-playbook-bot-draupnir.md:26
msgid "[!WARNING] 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:20
#: ../../../docs/configuring-playbook-bot-draupnir.md:29
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:22
#: ../../../docs/configuring-playbook-bot-draupnir.md:31
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:24
#: ../../../docs/configuring-playbook-bot-draupnir.md:33
msgid "End-to-End Encryption support"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:26
#: ../../../docs/configuring-playbook-bot-draupnir.md:35
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:28
#: ../../../docs/configuring-playbook-bot-draupnir.md:37
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:30
#: ../../../docs/configuring-playbook-bot-draupnir.md:39
msgid "Disable Pantalaimon for Draupnir (since v2.0.0; optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:32
#: ../../../docs/configuring-playbook-bot-draupnir.md:41
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:34
#: ../../../docs/configuring-playbook-bot-draupnir.md:43
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:36
#: ../../../docs/configuring-playbook-bot-draupnir.md:45
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:38
#: ../../../docs/configuring-playbook-bot-draupnir.md:47
msgid "Native E2EE support"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:40
#: ../../../docs/configuring-playbook-bot-draupnir.md:49
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:42
#: ../../../docs/configuring-playbook-bot-draupnir.md:51
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:44
#: ../../../docs/configuring-playbook-bot-draupnir.md:53
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:55
#: ../../../docs/configuring-playbook-bot-draupnir.md:64
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:57
#: ../../../docs/configuring-playbook-bot-draupnir.md:66
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 earlier."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:76
#: ../../../docs/configuring-playbook-bot-draupnir.md:85
msgid "Create and invite the bot to the management room"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:78
#: ../../../docs/configuring-playbook-bot-draupnir.md:87
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:84
#: ../../../docs/configuring-playbook-bot-draupnir.md:93
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:86
#: ../../../docs/configuring-playbook-bot-draupnir.md:95
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:88
#: ../../../docs/configuring-playbook-bot-draupnir.md:97
msgid "Make sure the account is free from rate limiting (optional, recommended)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:90
#: ../../../docs/configuring-playbook-bot-draupnir.md:99
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:92
#: ../../../docs/configuring-playbook-bot-draupnir.md:101
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:94
#: ../../../docs/configuring-playbook-bot-draupnir.md:103
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:96
msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)."
#: ../../../docs/configuring-playbook-bot-draupnir.md:105
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:98
#: ../../../docs/configuring-playbook-bot-draupnir.md:107
msgid "Add the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:100
#: ../../../docs/configuring-playbook-bot-draupnir.md:109
msgid "To expose the APIs publicly, add the following configuration to your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:106
#: ../../../docs/configuring-playbook-bot-draupnir.md:115
msgid "Obtain an access token for admin account"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:108
#: ../../../docs/configuring-playbook-bot-draupnir.md:117
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:110
#: ../../../docs/configuring-playbook-bot-draupnir.md:119
msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:113
#: ../../../docs/configuring-playbook-bot-draupnir.md:122
msgid "Run the `curl` command"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:115
#: ../../../docs/configuring-playbook-bot-draupnir.md:124
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:117
#: ../../../docs/configuring-playbook-bot-draupnir.md:126
msgid "`ADMIN_ACCESS_TOKEN_HERE` with the access token of the admin account"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:118
#: ../../../docs/configuring-playbook-bot-draupnir.md:127
msgid "`example.com` with your base domain"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:119
#: ../../../docs/configuring-playbook-bot-draupnir.md:128
msgid "`@bot.draupnir:example.com` with the MXID of your Draupnir bot user"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:125
#: ../../../docs/configuring-playbook-bot-draupnir.md:134
#: ../../../docs/configuring-playbook-bot-draupnir.md:207
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:126
#: ../../../docs/configuring-playbook-bot-draupnir.md:135
msgid "This does not work on outdated Windows 10 as curl is not available there."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:127
#: ../../../docs/configuring-playbook-bot-draupnir.md:136
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:129
#: ../../../docs/configuring-playbook-bot-draupnir.md:138
msgid "Abuse Reports"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:131
#: ../../../docs/configuring-playbook-bot-draupnir.md:140
msgid "Draupnir can receive reports in the management room."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:133
#: ../../../docs/configuring-playbook-bot-draupnir.md:142
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:145
#: ../../../docs/configuring-playbook-bot-draupnir.md:148
msgid "Enabling synapse-http-antispam support"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:150
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:160
msgid "These protections need to be manually activated and consulting the [enabling protections](#enabling-built-in-protections) guide can be helpful or consulting upstream documentation."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:168
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:147
#: ../../../docs/configuring-playbook-bot-draupnir.md:170
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:149
#: ../../../docs/configuring-playbook-bot-draupnir.md:172
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:151
#: ../../../docs/configuring-playbook-bot-draupnir.md:174
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:153
#: ../../../docs/configuring-playbook-bot-draupnir.md:176
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:167
#: ../../../docs/configuring-playbook-bot-draupnir.md:190
msgid "Migrating from Mjolnir (Only required if migrating)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:169
#: ../../../docs/configuring-playbook-bot-draupnir.md:192
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:171
#: ../../../docs/configuring-playbook-bot-draupnir.md:194
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:173
#: ../../../docs/configuring-playbook-bot-draupnir.md:196
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:175
#: ../../../docs/configuring-playbook-bot-draupnir.md:198
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:177
#: ../../../docs/configuring-playbook-bot-draupnir.md:200
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:184
#: ../../../docs/configuring-playbook-bot-draupnir.md:209
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:211
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:186
#: ../../../docs/configuring-playbook-bot-draupnir.md:213
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:188
#: ../../../docs/configuring-playbook-bot-draupnir.md:215
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:217
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:190
#: ../../../docs/configuring-playbook-bot-draupnir.md:219
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:192
#: ../../../docs/configuring-playbook-bot-draupnir.md:221
msgid "Below is a **non-exhaustive quick-start guide** for the impatient."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:194
#: ../../../docs/configuring-playbook-bot-draupnir.md:223
msgid "Making Draupnir join and protect a room"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:196
#: ../../../docs/configuring-playbook-bot-draupnir.md:225
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:198
#: ../../../docs/configuring-playbook-bot-draupnir.md:227
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:200
#: ../../../docs/configuring-playbook-bot-draupnir.md:229
msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:202
#: ../../../docs/configuring-playbook-bot-draupnir.md:231
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:204
#: ../../../docs/configuring-playbook-bot-draupnir.md:233
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:206
#: ../../../docs/configuring-playbook-bot-draupnir.md:235
msgid "Giving Draupnir permissions to do its job"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:208
#: ../../../docs/configuring-playbook-bot-draupnir.md:237
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:210
#: ../../../docs/configuring-playbook-bot-draupnir.md:239
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:212
#: ../../../docs/configuring-playbook-bot-draupnir.md:241
msgid "Subscribing to a public policy list"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:214
#: ../../../docs/configuring-playbook-bot-draupnir.md:243
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:216
msgid "Polcy lists are maintained in Matrix rooms. A popular policy list is maintained in the public `#community-moderation-effort-bl:neko.dev` room."
#: ../../../docs/configuring-playbook-bot-draupnir.md:245
msgid "Policy lists are maintained in Matrix rooms. Popular ones maintained in the public are:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:218
msgid "You can tell Draupnir to subscribe to it by sending the following command to the Management Room: `!draupnir watch #community-moderation-effort-bl:neko.dev`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:220
msgid "Creating your own policy lists and rules"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:222
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:224
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:226
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:228
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:230
msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:232
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:233
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:235
msgid "As a result of running these commands, you may observe:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:237
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:238
msgid "applying these rules against all rooms that Draupnir is an Administrator in"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:240
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:242
msgid "Enabling built-in protections"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:244
msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the room to invite-only\")."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:246
msgid "To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room."
#: ../../../docs/configuring-playbook-bot-draupnir.md:247
msgid "`#community-moderation-effort-bl:neko.dev`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:248
msgid "To **see the configuration options for a given protection**, send a `!draupnir protections show PROTECTION_NAME` (e.g. `!draupnir protections show JoinWaveShortCircuit`)."
msgid "`#huginn-muninn-active-threats:feline.support`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:250
msgid "To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)."
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:252
msgid "To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)."
msgid "Creating your own policy lists and rules"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:254
msgid "To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)."
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:256
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:258
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:260
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:262
msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:264
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:265
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:267
msgid "As a result of running these commands, you may observe:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:269
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:270
msgid "applying these rules against all rooms that Draupnir is an Administrator in"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:272
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:274
msgid "Enabling built-in protections"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:276
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:278
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:280
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:282
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:284
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:286
msgid "To **disable a given protection**, send a command like this: `!draupnir protections disable PROTECTION_NAME` (e.g. `!draupnir protections disable JoinWaveShortCircuitProtection`)."
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,108 +18,140 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bot-honoroit.md:1
#: ../../../docs/configuring-playbook-bot-honoroit.md:9
msgid "Setting up Honoroit (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:3
#: ../../../docs/configuring-playbook-bot-honoroit.md:11
msgid "The playbook can install and configure [Honoroit](https://github.com/etkecc/honoroit) for you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:5
#: ../../../docs/configuring-playbook-bot-honoroit.md:13
msgid "It's a bot you can use to setup **your own helpdesk on matrix**"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:7
#: ../../../docs/configuring-playbook-bot-honoroit.md:15
msgid "See the project's [documentation](https://github.com/etkecc/honoroit/blob/main/README.md) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:9
#: ../../../docs/configuring-playbook-bot-honoroit.md:17
msgid "Adjusting DNS records (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:11
#: ../../../docs/configuring-playbook-bot-honoroit.md:19
msgid "By default, this playbook installs Honoroit on the `matrix.` subdomain, at the `/honoroit` path (https://matrix.example.com/honoroit). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:13
#: ../../../docs/configuring-playbook-bot-honoroit.md:21
msgid "If you wish to adjust it, see the section [below](#adjusting-the-honoroit-url-optional) for details about DNS configuration."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:15
#: ../../../docs/configuring-playbook-bot-honoroit.md:23
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:17
#: ../../../docs/configuring-playbook-bot-honoroit.md:25
msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:32
#: ../../../docs/configuring-playbook-bot-honoroit.md:40
msgid "Adjusting the Honoroit URL (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:34
#: ../../../docs/configuring-playbook-bot-honoroit.md:42
msgid "By tweaking the `matrix_bot_honoroit_hostname` and `matrix_bot_honoroit_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:36
#: ../../../docs/configuring-playbook-bot-honoroit.md:44
msgid "Example additional configuration for your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:44
#: ../../../docs/configuring-playbook-bot-honoroit.md:52
msgid "If you've changed the default hostname, you may need to create a CNAME record for the Honoroit domain (`honoroit.example.com`), which targets `matrix.example.com`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:46
#: ../../../docs/configuring-playbook-bot-honoroit.md:54
msgid "When setting, replace `example.com` with your own."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:48
#: ../../../docs/configuring-playbook-bot-honoroit.md:56
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:58
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:60
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:62
msgid "`roles/custom/matrix-bot-honoroit/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:64
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:50
#: ../../../docs/configuring-playbook-bot-honoroit.md:66
msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:57
#: ../../../docs/configuring-playbook-bot-honoroit.md:73
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:59
#: ../../../docs/configuring-playbook-bot-honoroit.md:75
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:61
#: ../../../docs/configuring-playbook-bot-honoroit.md:77
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:63
#: ../../../docs/configuring-playbook-bot-honoroit.md:79
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:65
msgid "If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password."
#: ../../../docs/configuring-playbook-bot-honoroit.md:81
msgid "If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:67
#: ../../../docs/configuring-playbook-bot-honoroit.md:83
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:69
#: ../../../docs/configuring-playbook-bot-honoroit.md:85
msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @honoroit:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:71
#: ../../../docs/configuring-playbook-bot-honoroit.md:87
msgid "After the bot joins the room, any Matrix user can send a message to it to start a new thread in that room."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:73
#: ../../../docs/configuring-playbook-bot-honoroit.md:89
msgid "Send `!ho help` to the bot in the room to see the available commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:75
#: ../../../docs/configuring-playbook-bot-honoroit.md:91
msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/honoroit#features)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:93
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:95
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-honoroit`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:97
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:99
msgid "If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-12-23 13:09+0900\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,84 +18,120 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:1
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:13
msgid "Setting up matrix-registration-bot (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:3
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:15
msgid "The playbook can install and configure [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) for you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:5
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:17
msgid "The bot allows you to easily **create and manage registration tokens** aka. invitation codes. It can be used for an invitation-based server, where you invite someone by sending them a registration token (tokens look like this: `rbalQ0zkaDSRQCOp`). They can register as per normal but have to provide a valid registration token in the final step of the registration process."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:7
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:19
msgid "See the project's [documentation](https://github.com/moan0s/matrix-registration-bot/blob/master/README.md) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:9
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:21
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:11
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:23
msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:30
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:46
msgid "The bot account will be created automatically."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:32
msgid "Installing"
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:48
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:34
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:50
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:41
msgid "**Notes**:"
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:52
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:43
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:45
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:47
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:49
msgid "If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:51
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:53
msgid "To use the bot, start a chat with `@bot.matrix-registration-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:54
msgid "`roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55
msgid "Send `help` to the bot to see the available commands."
msgid "`roles/custom/matrix-bot-matrix-registration-bot/templates/config.yaml.j2` for the bridge's default configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57
msgid "You can also refer to the upstream [Usage documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands)."
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:59
msgid "If you have any questions, or if you need help setting it up, read the [troublshooting guide](https://github.com/moan0s/matrix-registration-bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)."
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:61
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:66
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:68
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:70
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:72
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:74
msgid "If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:76
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:78
msgid "To use the bot, start a chat with `@bot.matrix-registration-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:80
msgid "Send `help` to the bot to see the available commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:82
msgid "You can also refer to the upstream [Usage documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:84
msgid "If you have any questions, or if you need help setting it up, read the [troubleshooting guide](https://github.com/moan0s/matrix-registration-bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:86
msgid "To clean the cache (session & encryption data) after you changed the bot's username, changed the login method from access_token to password etc… you can use:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:92
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:94
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-matrix-registration-bot`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:96
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:98
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 ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-12-23 13:09+0900\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,80 +18,116 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:1
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9
msgid "Setting up matrix-reminder-bot (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:3
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11
msgid "The playbook can install and configure [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot) for you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:5
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:13
msgid "It's a bot you can use to **schedule one-off & recurring reminders and alarms**."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:7
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:15
msgid "See the project's [documentation](https://github.com/anoadragon453/matrix-reminder-bot/blob/master/README.md) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:17
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:19
msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:26
msgid "Installing"
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:34
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:28
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:36
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:35
msgid "**Notes**:"
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:38
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:37
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:39
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:40
msgid "`roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:41
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgid "`roles/custom/matrix-bot-matrix-reminder-bot/templates/config.yaml.j2` for the bot's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_bot_matrix_reminder_bot_configuration_extension_yaml` variable"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:43
msgid "If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password."
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:45
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:52
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:54
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:56
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:58
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:60
msgid "If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:62
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:47
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:64
msgid "To use the bot, start a chat with `@bot.matrix-reminder-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:49
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:66
msgid "You can also add the bot to any existing Matrix room (`/invite @bot.matrix-reminder-bot:example.com`)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:51
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:68
msgid "Basic usage is like this: `!remindme in 2 minutes; This is a test`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:53
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:70
msgid "Send `!help reminders` to the room to see the bot's help menu for additional commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:55
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:72
msgid "You can also refer to the upstream [Usage documentation](https://github.com/anoadragon453/matrix-reminder-bot#usage)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:74
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:76
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-matrix-reminder-bot`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:78
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:80
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 ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,149 +18,185 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bot-maubot.md:1
#: ../../../docs/configuring-playbook-bot-maubot.md:12
msgid "Setting up maubot (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:3
#: ../../../docs/configuring-playbook-bot-maubot.md:14
msgid "The playbook can install and configure [maubot](https://github.com/maubot/maubot) for you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:5
#: ../../../docs/configuring-playbook-bot-maubot.md:16
msgid "After setting up maubot, you can use the web management interface to make it do things. The default location of the management interface is `matrix.example.com/_matrix/maubot/`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:7
#: ../../../docs/configuring-playbook-bot-maubot.md:18
msgid "See the project's [documentation](https://docs.mau.fi/maubot/usage/basic.html) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:9
#: ../../../docs/configuring-playbook-bot-maubot.md:20
msgid "Adjusting DNS records (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:11
#: ../../../docs/configuring-playbook-bot-maubot.md:22
msgid "By default, this playbook installs maubot on the `matrix.` subdomain, at the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:13
#: ../../../docs/configuring-playbook-bot-maubot.md:24
msgid "If you wish to adjust it, see the section [below](#adjusting-the-maubot-url-optional) for details about DNS configuration."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:15
#: ../../../docs/configuring-playbook-bot-maubot.md:26
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:17
#: ../../../docs/configuring-playbook-bot-maubot.md:28
msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:32
#: ../../../docs/configuring-playbook-bot-maubot.md:43
msgid "You can add multiple admins. The admin accounts are only used to access the maubot administration interface."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:34
#: ../../../docs/configuring-playbook-bot-maubot.md:45
msgid "Adjusting the maubot URL (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:36
#: ../../../docs/configuring-playbook-bot-maubot.md:47
msgid "By tweaking the `matrix_bot_maubot_hostname` and `matrix_bot_maubot_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:38
#: ../../../docs/configuring-playbook-bot-maubot.md:56
#: ../../../docs/configuring-playbook-bot-maubot.md:49
#: ../../../docs/configuring-playbook-bot-maubot.md:76
msgid "Example additional configuration for your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:46
#: ../../../docs/configuring-playbook-bot-maubot.md:57
msgid "If you've changed the default hostname, you may need to create a CNAME record for the maubot domain (`maubot.example.com`), which targets `matrix.example.com`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:48
#: ../../../docs/configuring-playbook-bot-maubot.md:59
msgid "When setting, replace `example.com` with your own."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:50
msgid "Customizing the maubot container image"
#: ../../../docs/configuring-playbook-bot-maubot.md:61
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:52
msgid "Certain [maubot plugins](https://plugins.mau.bot/) require additional dependencies to be installed."
#: ../../../docs/configuring-playbook-bot-maubot.md:63
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:54
msgid "You can customize the default maubot container image and install your own dependencies."
#: ../../../docs/configuring-playbook-bot-maubot.md:65
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:67
msgid "`roles/custom/matrix-bot-maubot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:68
msgid "`roles/custom/matrix-bot-maubot/templates/config.yaml.j2` for the bot's default configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:70
msgid "Customizing the maubot container image"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:72
msgid "Certain [maubot plugins](https://plugins.mau.bot/) require additional dependencies to be installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:74
msgid "You can customize the default maubot container image and install your own dependencies."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:87
msgid "Consult the [Dockerfile reference](https://docs.docker.com/reference/dockerfile/) for more information about the syntax."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:69
#: ../../../docs/configuring-playbook-bot-maubot.md:89
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:71
#: ../../../docs/configuring-playbook-bot-maubot.md:91
msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:78
#: ../../../docs/configuring-playbook-bot-maubot.md:98
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:80
#: ../../../docs/configuring-playbook-bot-maubot.md:100
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:82
#: ../../../docs/configuring-playbook-bot-maubot.md:102
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:84
#: ../../../docs/configuring-playbook-bot-maubot.md:104
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:86
msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password."
#: ../../../docs/configuring-playbook-bot-maubot.md:106
msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:88
#: ../../../docs/configuring-playbook-bot-maubot.md:108
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:90
#: ../../../docs/configuring-playbook-bot-maubot.md:110
msgid "By default, you can visit `matrix.example.com/_matrix/maubot/` to manage your available plugins, clients and instances."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:92
#: ../../../docs/configuring-playbook-bot-maubot.md:112
msgid "You should start in the following order"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:93
#: ../../../docs/configuring-playbook-bot-maubot.md:113
msgid "**Create one or more clients**: A client is a Matrix account which the bot will use to message. By default, the playbook creates a `bot.maubot` account (as per the configuration above). You only need to [obtain an access token](#obtaining-an-access-token) for it"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:94
#: ../../../docs/configuring-playbook-bot-maubot.md:114
msgid "**Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:95
#: ../../../docs/configuring-playbook-bot-maubot.md:115
msgid "**Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:97
#: ../../../docs/configuring-playbook-bot-maubot.md:117
msgid "Obtain an access token"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:99
#: ../../../docs/configuring-playbook-bot-maubot.md:119
msgid "This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:101
#: ../../../docs/configuring-playbook-bot-maubot.md:121
msgid "Alternatively, you can refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will causes issues to your bot in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:103
#: ../../../docs/configuring-playbook-bot-maubot.md:123
msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:126
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:128
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-maubot`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:130
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:132
msgid "The default logging level for this component is `WARNING`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,254 +18,266 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bot-mjolnir.md:1
#: ../../../docs/configuring-playbook-bot-mjolnir.md:12
msgid "Setting up Mjolnir (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:3
#: ../../../docs/configuring-playbook-bot-mjolnir.md:14
msgid "The playbook can install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation bot for you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:5
#: ../../../docs/configuring-playbook-bot-mjolnir.md:16
msgid "See the project's [documentation](https://github.com/matrix-org/mjolnir/blob/main/README.md) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:7
#: ../../../docs/configuring-playbook-bot-mjolnir.md:18
msgid "Prerequisites"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:9
#: ../../../docs/configuring-playbook-bot-mjolnir.md:20
msgid "Register the bot account"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:11
#: ../../../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."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:13
#: ../../../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`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:15
#: ../../../docs/configuring-playbook-bot-mjolnir.md:26
msgid "You can use the playbook to [register a new user](registering-users.md):"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:21
#: ../../../docs/configuring-playbook-bot-mjolnir.md:32
msgid "If you would like Mjolnir to be able to deactivate users, move aliases, shutdown rooms, etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:23
#: ../../../docs/configuring-playbook-bot-mjolnir.md:34
msgid "Obtain an access token"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:25
#: ../../../docs/configuring-playbook-bot-mjolnir.md:36
msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:27
#: ../../../docs/configuring-playbook-bot-mjolnir.md:52
#: ../../../docs/configuring-playbook-bot-mjolnir.md:38
#: ../../../docs/configuring-playbook-bot-mjolnir.md:63
msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:30
#: ../../../docs/configuring-playbook-bot-mjolnir.md:41
msgid "Make sure the account is free from rate limiting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:32
#: ../../../docs/configuring-playbook-bot-mjolnir.md:43
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:34
#: ../../../docs/configuring-playbook-bot-mjolnir.md:45
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:36
#: ../../../docs/configuring-playbook-bot-mjolnir.md:47
msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:38
msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)."
#: ../../../docs/configuring-playbook-bot-mjolnir.md:49
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:40
#: ../../../docs/configuring-playbook-bot-mjolnir.md:51
msgid "Add the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:42
#: ../../../docs/configuring-playbook-bot-mjolnir.md:53
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:48
#: ../../../docs/configuring-playbook-bot-mjolnir.md:59
msgid "Obtain an access token for admin account"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:50
#: ../../../docs/configuring-playbook-bot-mjolnir.md:61
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:55
#: ../../../docs/configuring-playbook-bot-mjolnir.md:66
msgid "Run the `curl` command"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:57
#: ../../../docs/configuring-playbook-bot-mjolnir.md:68
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:59
#: ../../../docs/configuring-playbook-bot-mjolnir.md:70
msgid "`ADMIN_ACCESS_TOKEN_HERE` with the access token of the admin account"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:60
#: ../../../docs/configuring-playbook-bot-mjolnir.md:71
msgid "`example.com` with your base domain"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:61
#: ../../../docs/configuring-playbook-bot-mjolnir.md:72
msgid "`@bot.mjolnir:example.com` with the MXID of your Mjolnir bot user"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:67
#: ../../../docs/configuring-playbook-bot-mjolnir.md:184
#: ../../../docs/configuring-playbook-bot-mjolnir.md:78
#: ../../../docs/configuring-playbook-bot-mjolnir.md:195
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:68
#: ../../../docs/configuring-playbook-bot-mjolnir.md:79
msgid "This does not work on outdated Windows 10 as curl is not available there."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:69
#: ../../../docs/configuring-playbook-bot-mjolnir.md:80
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:71
#: ../../../docs/configuring-playbook-bot-mjolnir.md:82
msgid "Create a management room"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:73
#: ../../../docs/configuring-playbook-bot-mjolnir.md:84
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:75
#: ../../../docs/configuring-playbook-bot-mjolnir.md:86
msgid "[!WARNING] 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:78
#: ../../../docs/configuring-playbook-bot-mjolnir.md:89
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:80
#: ../../../docs/configuring-playbook-bot-mjolnir.md:91
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:82
#: ../../../docs/configuring-playbook-bot-mjolnir.md:93
msgid "Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:84
#: ../../../docs/configuring-playbook-bot-mjolnir.md:95
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:86
#: ../../../docs/configuring-playbook-bot-mjolnir.md:97
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:95
#: ../../../docs/configuring-playbook-bot-mjolnir.md:106
msgid "End-to-End Encryption support"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:97
#: ../../../docs/configuring-playbook-bot-mjolnir.md:108
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:99
#: ../../../docs/configuring-playbook-bot-mjolnir.md:110
msgid "To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:101
#: ../../../docs/configuring-playbook-bot-mjolnir.md:112
msgid "Configuration with E2EE support"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:103
#: ../../../docs/configuring-playbook-bot-mjolnir.md:114
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:105
#: ../../../docs/configuring-playbook-bot-mjolnir.md:116
msgid "Add the following configuration to your `vars.yml` file (adapt to your needs):"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:119
#: ../../../docs/configuring-playbook-bot-mjolnir.md:130
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:131
#: ../../../docs/configuring-playbook-bot-mjolnir.md:142
msgid "Configuration without E2EE support"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:133
#: ../../../docs/configuring-playbook-bot-mjolnir.md:144
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:135
#: ../../../docs/configuring-playbook-bot-mjolnir.md:146
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:141
#: ../../../docs/configuring-playbook-bot-mjolnir.md:152
msgid "Adding Mjolnir synapse antispam module (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:143
#: ../../../docs/configuring-playbook-bot-mjolnir.md:154
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:153
#: ../../../docs/configuring-playbook-bot-mjolnir.md:164
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:155
#: ../../../docs/configuring-playbook-bot-mjolnir.md:166
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:157
#: ../../../docs/configuring-playbook-bot-mjolnir.md:168
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:159
#: ../../../docs/configuring-playbook-bot-mjolnir.md:170
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:161
#: ../../../docs/configuring-playbook-bot-mjolnir.md:172
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:175
#: ../../../docs/configuring-playbook-bot-mjolnir.md:186
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:177
#: ../../../docs/configuring-playbook-bot-mjolnir.md:188
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:186
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:188
#: ../../../docs/configuring-playbook-bot-mjolnir.md:197
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:190
#: ../../../docs/configuring-playbook-bot-mjolnir.md:199
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:192
msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password."
#: ../../../docs/configuring-playbook-bot-mjolnir.md:201
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:194
#: ../../../docs/configuring-playbook-bot-mjolnir.md:203
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:196
#: ../../../docs/configuring-playbook-bot-mjolnir.md:205
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
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:209
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
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:213
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 ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,53 +18,53 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:1
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:10
msgid "Setting up Postmoogle email bridging (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:3
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:12
msgid "The playbook can install and configure [Postmoogle](https://github.com/etkecc/postmoogle) for you."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:5
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:14
msgid "Postmoogle is a bridge you can use to have its bot user forward emails to Matrix rooms. It runs an SMTP email server and allows you to assign mailbox addresses to the rooms."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:7
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:16
msgid "See the project's [documentation](https://github.com/etkecc/postmoogle/blob/master/README.md) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:9
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:18
msgid "Prerequisites"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:11
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:20
msgid "Open the following ports on your server to be able to receive incoming emails:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:13
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:22
msgid "`25/tcp`: SMTP"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:14
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:23
msgid "`587/tcp`: Submission (TLS-encrypted SMTP)"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:16
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:25
msgid "If you don't open these ports, you will still be able to send emails, but not receive any."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:18
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:27
msgid "These port numbers are configurable via the `matrix_postmoogle_smtp_host_bind_port` and `matrix_postmoogle_submission_host_bind_port` variables, but other email servers will try to deliver on these default (standard) ports, so changing them is of little use."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:20
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:29
msgid "Adjusting DNS records"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:22
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:31
msgid "To make Postmoogle enable its email sending features, you need to configure MX and TXT (SPF, DMARC, and DKIM) records. See the table below for values which need to be specified."
msgstr ""
@@ -140,90 +140,94 @@ msgstr ""
msgid "get it from `!pm dkim`"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:31
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:40
msgid "**Note**: the DKIM record can be retrieved after configuring and installing the bridge's bot."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:33
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:42
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:35
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:44
msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:56
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:65
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:58
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:67
msgid "There are some additional things you may wish to configure about the bridge."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:60
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:69
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:62
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:71
msgid "`roles/custom/matrix-bridge-postmoogle/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:64
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:73
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:66
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:75
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:73
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:82
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:75
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:84
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create a user account of the bridge's bot."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:77
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:86
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:79
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:88
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:81
msgid "If you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password."
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:90
msgid "If you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:83
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:92
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:85
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:94
msgid "To use the bridge, invite the `@postmoogle:example.com` bot user into a room you want to use as a mailbox."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:87
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:96
msgid "Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with the email address `NAME@matrix.example.com`. Emails sent to that email address will be forwarded to the room."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:89
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:98
msgid "Send `!pm help` to the bot in the room to see the available commands."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:91
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:100
msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/postmoogle)."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:93
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:102
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:95
msgid "As with all other services, you can find their logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-postmoogle`"
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:104
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-postmoogle`."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:97
msgid "The default logging level for this bridge is `INFO`, but you can increase it to `DEBUG` with the following additional configuration:"
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:106
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-postmoogle.md:108
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 ""
@@ -0,0 +1,117 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018-2026, Slavi Pantaleev, Aine Etke, MDAD community
# members
# This file is distributed under the same license as the
# matrix-docker-ansible-deploy package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2026.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
"Language-Team: jp <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-element-admin.md:8
msgid "Setting up Element Admin (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:10
msgid "The playbook can install and configure [Element Admin](https://github.com/element-hq/element-admin) for you."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:12
msgid "Element Admin is a web-based administration panel for Synapse and [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md)."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:14
msgid "See the project's [documentation](https://github.com/element-hq/element-admin) to learn more."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:16
msgid "💡 **Note**: This project is still very young and doesn't have many features. [Ketesa](./configuring-playbook-ketesa.md) is the fully-featured alternative — it covers all Synapse and MAS Admin APIs, including complete user management, session management, and MAS policy data. Element Admin remains a valid choice if you prefer its interface."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:18
msgid "Prerequisites"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:20
msgid "A [Synapse](configuring-playbook-synapse.md) homeserver with its Admin API enabled (the playbook automatically enables it for you when you enable Element Admin)"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:21
msgid "[Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) with its Admin API enabled (the playbook automatically enables it for you when you enable Element Admin)"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:23
msgid "Decide on a domain and path"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:25
msgid "By default, the Element Admin is configured to be served on the `admin.element.example.com` domain."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:27
msgid "If you'd like to run Element Admin on another hostname, see the [Adjusting the Element Admin URL](#adjusting-the-element-admin-url-optional) section below."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:29
msgid "Adjusting DNS records (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:31
msgid "By default, this playbook installs Element Admin on the `admin.element.` subdomain (`admin.element.example.com`) and requires you to create a `CNAME` record for `admin.element`, which targets `matrix.example.com`."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:33
msgid "When setting these values, replace `example.com` with your own."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:35
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:37
msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:43
msgid "Adjusting the Element Admin URL (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:45
msgid "By tweaking the `matrix_element_admin_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:47
msgid "Example additional configuration for your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:53
msgid "[!WARNING] A `matrix_element_admin_path_prefix` variable is also available and mean to let you configure a path prefix for the Element Admin service, but **Element Admin does not support running under a sub-path yet**."
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:56
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:58
msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:65
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-element-admin.md:67
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgstr ""
@@ -0,0 +1,165 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018-2026, Slavi Pantaleev, Aine Etke, MDAD community
# members
# This file is distributed under the same license as the
# matrix-docker-ansible-deploy package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2026.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-04-03 12:02+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
"Language-Team: jp <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-ketesa.md:14
msgid "Setting up Ketesa (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:16
msgid "The playbook can install and configure [Ketesa](https://github.com/etkecc/ketesa) for you."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:18
msgid "Ketesa is a fully-featured admin interface for Matrix homeservers — manage users, rooms, media, sessions, and more from one clean, responsive web UI. It is the evolution of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin): what began as a fork has grown into its own independent project with a redesigned interface, comprehensive Synapse and MAS API coverage, and multi-language support."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:20
msgid "[!NOTE]"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:22
msgid "Ketesa does not work with other homeserver implementations than Synapse due to API's incompatibility."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:23
msgid "The latest version of Ketesa is hosted by [etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). If you only need this service occasionally and trust giving your admin credentials to a 3rd party Single Page Application, you can consider using it from there and avoiding the (small) overhead of self-hosting."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:24
msgid "This playbook also supports an alternative management UI in the shape of [Element Admin](./configuring-playbook-element-admin.md). Please note that it's currently less feature-rich than Ketesa and requires [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md)."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:26
msgid "Adjusting DNS records (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:28
msgid "By default, this playbook installs Ketesa on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin) — the legacy path is kept for backward compatibility. This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:30
msgid "If you wish to adjust it, see the section [below](#adjusting-the-ketesa-url-optional) for details about DNS configuration."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:32
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:34
msgid "To enable Ketesa, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:40
msgid "**Note**: Ketesa requires Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to function. Access to them is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, for additional security, we normally leave them unexposed, following [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). Because Ketesa needs these APIs to function, when installing Ketesa, the playbook **automatically** exposes the Synapse Admin API publicly for you. Depending on the homeserver implementation you're using (Synapse, Dendrite), this is equivalent to:"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:42
msgid "for [Synapse](./configuring-playbook-synapse.md) (our default homeserver implementation): `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true`"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:43
msgid "for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true`"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:45
msgid "By default, Ketesa installation will be [restricted to only work with one homeserver](https://github.com/etkecc/ketesa/blob/main/README.md#restricting-available-homeserver) — the one managed by the playbook. To adjust these restrictions, tweak the `matrix_ketesa_config_restrictBaseUrl` variable."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:47
msgid "Adjusting the Ketesa URL (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:49
msgid "By tweaking the `matrix_ketesa_hostname` and `matrix_ketesa_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:51
msgid "We recommend updating the path prefix to `/ketesa` to align with the new branding, while the default `/synapse-admin` is kept for backward compatibility:"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:57
msgid "Or to change the hostname entirely:"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:65
msgid "If you've changed the default hostname, you may need to create a CNAME record for the Ketesa domain (`admin.example.com`), which targets `matrix.example.com`."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:67
msgid "When setting, replace `example.com` with your own."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:69
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:71
msgid "There are some additional things you may wish to configure about the component."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:73
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:75
msgid "`roles/custom/matrix-ketesa/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_ketesa_configuration_extension_json` variable"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:77
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:79
msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:86
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:88
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:90
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:92
msgid "After installation, Ketesa will be accessible at: `https://matrix.example.com/synapse-admin/` (or `/ketesa/` if you updated the path prefix as recommended)"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:94
msgid "To use Ketesa, you need to have [registered at least one administrator account](registering-users.md) on your server."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:96
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:98
msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-ketesa`."
msgstr ""
#: ../../../docs/configuring-playbook-ketesa.md:100
msgid "If you have questions, you can join this community room and feel free to ask: [#ketesa:etke.cc](https://matrix.to/#/#ketesa:etke.cc)"
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,150 +18,134 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:1
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:8
msgid "Setting up Matrix Authentication Service (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:3
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:10
msgid "The playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) — a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:5
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:12
msgid "Matrix Authentication Service is an implementation of [MSC3861: Next-generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:7
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:14
msgid "**Before going through with starting to use Matrix Authentication Service**, make sure to read:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:9
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:16
msgid "the [Reasons to use Matrix Authentication Service](#reasons-to-use-matrix-authentication-service) section below"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:10
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:17
msgid "the [Expectations](#expectations) section below"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:11
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:18
msgid "the [FAQ section on areweoidcyet.com](https://areweoidcyet.com/#faqs)"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:13
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:20
msgid "**If you've already been using Synapse** and have user accounts in its database, you can [migrate to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:15
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:22
msgid "Reasons to use Matrix Authentication Service"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:17
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:24
msgid "You may be wondering whether you should make the switch to Matrix Authentication Service (MAS) or keep using your existing authentication flow via Synapse (password-based or [OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)-enabled)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:19
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:26
msgid "Matrix Authentication Service is **still an experimental service** and **not a default** for this Ansible playbook."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:21
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:28
msgid "The [Expectations](#expectations) section contains a list of what works and what doesn't (**some services don't work with MAS yet**), as well as the **relative irreversability** of the migration process."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:23
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:30
msgid "Below, we'll try to **highlight some potential reasons for switching** to Matrix Authentication Service:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:25
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:32
msgid "To use SSO in [Element X](https://element.io/blog/element-x-ignition/). The old [Synapse OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) login flow is only supported in old Element clients and will not be supported in Element X. Element X will only support the new SSO-based login flow provided by MAS, so if you want to use SSO with Element X, you will need to switch to MAS."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:27
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:34
msgid "To help drive adoption of the \"Next-generation auth for Matrix\" by switching to what's ultimately coming anyway"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:29
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:36
msgid "To help discover (and potentially fix) MAS integration issues with this Ansible playbook"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:31
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:38
msgid "To help discover (and potentially fix) MAS integration issues with various other Matrix components (bridges, bots, clients, etc.)"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:33
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:40
msgid "To reap some of the security benefits that Matrix Authentication Service offers, as outlined in the [Better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/) article."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:35
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:42
msgid "Prerequisites"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:37
msgid "⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet."
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:44
msgid "⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating with Matrix Authentication Service yet."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:39
msgid "⚠️ **email sending** configured (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:41
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:46
msgid "❌ **disabling all password providers** for Synapse (things like [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc.) More details about this are available in the [Expectations](#expectations) section below."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:43
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:48
msgid "Expectations"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:45
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:50
msgid "This section details what you can expect when switching to the Matrix Authentication Service (MAS)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:47
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:52
msgid "❌ **Synapse password providers will need to be disabled**. You can no longer use [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc. When the authentication flow is handled by MAS (not by Synapse anymore), it doesn't make sense to extend the Synapse authentication flow with additional modules. Many bridges used to rely on shared-secret-auth for doing double-puppeting (impersonating other users), but most (at least the mautrix bridges) nowadays use [Appservice Double Puppet](./configuring-playbook-appservice-double-puppet.md) as a better alternative. Older/maintained bridges may still rely on shared-secret-auth, as do other services like [matrix-corporal](./configuring-playbook-matrix-corporal.md)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:49
msgid "❌ Certain **tools like [synapse-admin](./configuring-playbook-synapse-admin.md) do not have full compatibility with MAS yet**. synapse-admin already supports [login with access token](https://github.com/etkecc/synapse-admin/pull/58), browsing users (which Synapse will internally fetch from MAS) and updating user avatars. However, editing users (passwords, etc.) now needs to happen directly against MAS using the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html), which synapse-admin cannot interact with yet."
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:54
msgid "✅ **[Ketesa](./configuring-playbook-ketesa.md) has full MAS integration**. Ketesa supports OIDC auth, user management, all session types (browser, OAuth2, compatibility), linked email addresses, upstream OAuth provider links, MAS policy data, and user creation through MAS. It is the recommended tool for managing homeservers running MAS."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:51
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:56
msgid "❌ **Some services experience issues when authenticating via MAS**:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:53
msgid "[Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first time around, but it consistently fails after restarting:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:55
msgid "cannot initialize matrix bot error=\"olm account is marked as shared, keys seem to have disappeared from the server\""
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:57
msgid "[matrix-reminder-bot](./configuring-playbook-bot-matrix-reminder-bot.md) fails to start (see [element-hq/matrix-authentication-service#3439](https://github.com/element-hq/matrix-authentication-service/issues/3439))"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:58
msgid "Other services may be similarly affected. This list is not exhaustive."
msgid "[Reminder bot](configuring-playbook-bot-matrix-reminder-bot.md) seems to be losing some of its state on each restart and may reschedule old reminders once again"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:60
msgid "❌ **Encrypted appservices** do not work yet (related to [MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) and [PR 17705 for Synapse](https://github.com/element-hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will fail to start (see [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3658) for Hookshot). You can use these bridges/bots only if you **keep end-to-bridge encryption disabled** (which is the default setting)."
msgid "[Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first time around, but it consistently fails after restarting:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:62
msgid "⚠️ **You will need to have email sending configured** (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working."
msgid "cannot initialize matrix bot error=\"olm account is marked as shared, keys seem to have disappeared from the server\""
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:64
msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
msgid "❌ **Encrypted appservices** do not work yet (related to [MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) and [PR 17705 for Synapse](https://github.com/element-hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will fail to start (see [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3658) for Hookshot). You can use these bridges/bots only if you **keep end-to-bridge encryption disabled** (which is the default setting)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:66
msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) does not currently seem to preserve the \"admin\" flag for users (as found in the Synapse database). All users are imported as non-admin — see [element-hq/matrix-authentication-service#3440](https://github.com/element-hq/matrix-authentication-service/issues/3440). You may need update the Matrix Authentication Service's database manually and adjust the `can_request_admin` column in the `users` table to `true` for users that need to be administrators (e.g. `UPDATE users SET can_request_admin = true WHERE username = 'someone';`)"
msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:68
msgid "⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependant on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch."
msgid "⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependent on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:70
@@ -181,7 +165,7 @@ msgid "✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), [El
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:78
msgid "✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work. Going through the old login flow does not require users to have a verified email address, as [is the case](https://github.com/element-hq/matrix-authentication-service/issues/1505) for the new SSO-based login flow."
msgid "✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:80
@@ -209,7 +193,7 @@ msgid "Existing homeserver"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:92
msgid "Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet."
msgid "Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating with Matrix Authentication Service yet."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:94
@@ -297,326 +281,346 @@ msgstr ""
msgid "The playbook exposes a `matrix_authentication_service_config_upstream_oauth2_providers` variable for controlling this setting."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:269
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:273
msgid "💡 Refer to the [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers) for the most up-to-date schema and example for providers. The value shown above here may be out of date."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:271
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:275
msgid "⚠️ The syntax for existing [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) is slightly different, so you will need to adjust your configuration when switching from Synapse OIDC to MAS upstream OAuth2."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:273
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:277
msgid "⚠️ When [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) which contains OIDC-sourced users, you will need to:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:275
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:279
msgid "[Configure upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:276
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:280
msgid "go through the [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) process"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:277
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:281
msgid "remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:279
msgid "Installing"
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:283
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:281
msgid "Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below:"
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:285
msgid "There are some additional things you may wish to configure about the component."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:288
msgid "**Notes**:"
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:287
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:289
msgid "`roles/custom/matrix-authentication-service/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:290
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgid "`roles/custom/matrix-authentication-service/templates/config.yaml.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_authentication_service_configuration_extension_yaml` variable"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:292
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:294
msgid "Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:301
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:303
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:305
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:307
msgid "If you're in the process of migrating an existing Synapse homeserver to MAS, you should now follow the rest of the steps in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) guide."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:296
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:309
msgid "💡 After installation, you should [verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:298
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:311
msgid "Migrating an existing Synapse homeserver to Matrix Authentication Service"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:300
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:313
msgid "Our migration guide is loosely based on the upstream [Migrating an existing homeserver](https://element-hq.github.io/matrix-authentication-service/setup/migration.html) guide."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:302
msgid "Migration is done via a tool called `syn2mas`, which the playbook could run for you (in a container)."
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:315
msgid "Migration is done via a sub-command called `syn2mas`, which the playbook could run for you (in a container)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:304
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:317
msgid "The installation + migration steps are like this:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:306
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:319
msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) to **disable the integration between the homeserver and MAS**. This is done by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:308
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:321
msgid "Perform the initial [installation](#installing). At this point:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:310
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:323
msgid "Matrix Authentication Service will be installed. Its database will be empty, so it cannot validate existing access tokens or authentication users yet."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:312
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:325
msgid "The homeserver will still continue to use its local database for validating existing access tokens."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:314
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:327
msgid "Various [compatibility layer URLs](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) are not yet installed. New login sessions will still be forwarded to the homeserver, which is capable of completing them."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:316
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:329
msgid "The `matrix-user-creator` role would be suppressed, so that it doesn't automatically attempt to create users (for bots, etc.) in the MAS database. These user accounts likely already exist in Synapse's user database and could be migrated over (via syn2mas, as per the steps below), so creating them in the MAS database would have been unnecessary and potentially problematic (conflicts during the syn2mas migration)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:318
msgid "Consider taking a full [backup of your Postgres database](./maintenance-postgres.md#backing-up-postgresql). This is done just in case. The **syn2mas migration tool does not delete any data**, so it should be possible to revert to your previous setup by merely disabling MAS and re-running the playbook (no need to restore a Postgres backup). However, do note that as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:331
msgid "Consider taking a full [backup of your Postgres database](./maintenance-postgres.md#backing-up-postgresql). This is done just in case. The **syn2mas migration command does not delete any data**, so it should be possible to revert to your previous setup by merely disabling MAS and re-running the playbook (no need to restore a Postgres backup). However, do note that as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:320
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:333
msgid "[Migrate your data from Synapse to Matrix Authentication Service using syn2mas](#migrate-your-data-from-synapse-to-matrix-authentication-service-using-syn2mas)"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:322
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:335
msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) again, to:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:324
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:337
msgid "remove the `matrix_authentication_service_migration_in_progress: false` line"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:326
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:339
msgid "if you had been using [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:328
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:341
msgid "Perform the [installation](#installing) again. At this point:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:330
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:343
msgid "The homeserver will start delegating authentication to MAS."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:332
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:345
msgid "The compatibility layer URLs will be installed. New login sessions will be completed by MAS."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:334
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:347
msgid "[Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:336
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:349
msgid "Migrate your data from Synapse to Matrix Authentication Service using syn2mas"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:338
msgid "We **don't** ask you to [run the `syn2mas` migration advisor command](https://element-hq.github.io/matrix-authentication-service/setup/migration.html#run-the-migration-advisor), because it only gives you the green light if your Synapse configuration (`homeserver.yaml`) is configured in a way that's compatible with MAS (delegating authentication to MAS; disabling Synapse's password config; etc.). Until we migrate your data with the `syn2mas` tool, we intentionally avoid doing these changes to allow existing user sessions to work."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:340
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:351
msgid "You can invoke the `syn2mas` tool via the playbook by running the playbook's `matrix-authentication-service-mas-cli-syn2mas` tag. We recommend first doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:342
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:353
msgid "Configuring syn2mas"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:344
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:355
msgid "If you're using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to [Configuring upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:346
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:357
msgid "If you only have local (non-OIDC) users in your Synapse database, you can likely run `syn2mas` as-is (without doing additional configuration changes)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:348
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:359
msgid "When you're done with potentially configuring `syn2mas`, proceed to doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:350
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:361
msgid "Configuring upstream OIDC provider mapping for syn2mas"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:352
msgid "If you have existing OIDC users in your Synapse user database (which will be the case if when using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)), you may need to pass an additional `--upstreamProviderMapping` argument to the `syn2mas` tool to tell it which provider (on the Synapse side) maps to which other provider on the MAS side."
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:363
msgid "Since Matrix Authentication Service v0.16.0 (which replaced the standalone `syn2mas` tool with a `mas-cli syn2mas` sub-command), OIDC configuration (mapping from your old OIDC configuration to your new one, etc) is meant to be configured in the Matrix Authentication Service configuration (via `matrix_authentication_service_config_upstream_oauth2_providers`) as a `synapse_idp_id` property for each provider."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:354
msgid "If you don't do this, `syn2mas` would report errors like this one:"
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:365
msgid "You can refer to the [Map any upstream SSO providers](https://element-hq.github.io/matrix-authentication-service/setup/migration.html#map-any-upstream-sso-providers) section of the MAS documentation for figuring out how to set the `synapse_idp_id` value in `matrix_authentication_service_config_upstream_oauth2_providers` correctly."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:356
msgid "[FATAL] migrate - [Failed to import external id 4264b0f0-4f11-4ddd-aedb-b500e4d07c25 with oidc-keycloak for user @alice:example.com: Error: Unknown upstream provider oidc-keycloak]"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:358
msgid "Below is an example situation and a guide for how to solve it."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:360
msgid "If in `matrix_synapse_oidc_providers` your provider `idp_id` is (was) named `keycloak`, in the Synapse database users would be associated with the `oidc-keycloak` provider (note the `oidc-` prefix that was added automatically by Synapse to your `idp_id` value)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:362
msgid "The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` on the MAS side, as defined in `matrix_authentication_service_config_upstream_oauth2_providers` (see the [Upstream OAuth2 configuration](#upstream-oauth2-configuration) section above)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:364
msgid "To tell `syn2mas` how the Synapse-configured OIDC provider maps to the new MAS-configured OIDC provider, add this additional configuration to your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:373
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:367
msgid "Performing a syn2mas dry-run"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:375
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:369
msgid "Having [configured syn2mas](#configuring-syn2mas), we recommend doing a [dry-run](https://en.wikipedia.org/wiki/Dry_run_(testing)) first to verify that everything will work out as expected."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:377
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:371
msgid "A dry-run would not cause downtime, because it avoids stopping Synapse."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:379
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:373
msgid "To perform a dry-run, run:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:385
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:379
msgid "Observe the command output (especially the last line of the the syn2mas output). If you are confident that the migration will work out as expected, you can proceed with a [real migration](#performing-a-real-syn2mas-migration)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:387
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:381
msgid "Performing a real syn2mas migration"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:389
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:383
msgid "Before performing a real migration make sure:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:391
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:385
msgid "you've familiarized yourself with the [expectations](#expectations)"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:393
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:387
msgid "you've performed a Postgres backup, just in case"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:395
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:389
msgid "you're aware of the irreversibility of the migration process without disruption after users have created new login sessions via the new MAS setup"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:397
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:391
msgid "you've [configured syn2mas](#configuring-syn2mas), especially if you've used [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:399
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:393
msgid "you've performed a [syn2mas dry-run](#performing-a-syn2mas-dry-run) and don't see any issues in its output"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:401
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:395
msgid "To perform a real migration, run the `matrix-authentication-service-mas-cli-syn2mas` tag **without** the `matrix_authentication_service_syn2mas_migrate_dry_run` variable:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:407
msgid "Having performed a `syn2mas` migration once, trying to do it again will report errors for users that were already migrated (e.g. \"Error: Unknown upstream provider oauth-delegated\")."
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:401
msgid "After `syn2mas` completes, Synapse will intentionally remain stopped to avoid new registrations or other authentication changes from being accepted before the migration is completed. Continue with the next steps in this guide before re-running the installation."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:409
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:403
msgid "Having performed a `syn2mas` migration once, trying to do it again will report errors (e.g. \"Error: The MAS database is not empty: rows found in at least `users`. Please drop and recreate the database, then try again.\")."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:405
msgid "Verify that Matrix Authentication Service is installed correctly"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:411
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:407
msgid "After [installation](#installing), run the `doctor` subcommand of the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) to verify that MAS is installed correctly."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:413
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:409
msgid "You can do it:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:415
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:411
msgid "either via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag: `just run-tags matrix-authentication-service-mas-cli-doctor`"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:417
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:413
msgid "or by running the `mas-cli` script on the server (which invokes the `mas-cli` tool inside a container): `/matrix/matrix-authentication-service/bin/mas-cli doctor`"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:419
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:415
msgid "If successful, you should see some output that looks like this:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:431
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:427
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:429
msgid "Management"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:433
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:431
msgid "You can use the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) (exposed via the `/matrix/matrix-authentication-service/bin/mas-cli` script) to perform administrative tasks against MAS."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:435
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:433
msgid "This documentation page already mentions:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:437
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:435
msgid "the `mas-cli doctor` sub-command in the [Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly) section, which you can run via the CLI and via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:439
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:437
msgid "the `mas-cli manage register-user` sub-command in the [Registering users](./registering-users.md) documentation"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:441
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:439
msgid "There are other sub-commands available. Run `/matrix/matrix-authentication-service/bin/mas-cli` to get an overview."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:443
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:441
msgid "User registration"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:445
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:443
msgid "After Matrix Authentication Service is [installed](#installing), users need to be managed there (unless you're managing them in an [upstream OAuth2 provider](#upstream-oauth2-configuration))."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:447
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:445
msgid "You can register users new users as described in the [Registering users](./registering-users.md) documentation (via `mas-cli manage register-user` or the Ansible playbook's `register-user` tag)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:449
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:447
msgid "Working around email deliverability issues"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:449
msgid "Matrix Authentication Service only sends emails when:"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:451
msgid "Because Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user, you may need to work around email deliverability issues if [your email-sending configuration](./configuring-playbook-email.md) is not working."
msgid "it verifies email addresses for users who are self-registering with a password"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:453
msgid "Matrix Authentication Service attempts to verify email addresses by sending a verification email to the address specified by the user whenever they log in to an account without a verified email address."
msgid "a user tries to add an email to their account"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:455
msgid "If email delivery is not working, **you can retrieve the email configuration code from the Matrix Authentication Service's logs** (`journalctl -fu matrix-authentication-service`)."
msgid "If Matrix Authentication Service tries to send an email and it fails because [your email-sending configuration](./configuring-playbook-email.md) is not working, you may need to work around email deliverability."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:457
msgid "If email delivery is not working, **you can retrieve the email verification code from the Matrix Authentication Service's logs** (`journalctl -fu matrix-authentication-service`)."
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:459
msgid "Alternatively, you can use the [`mas-cli` management tool](#management) to manually verify email addresses for users. Example: `/matrix/matrix-authentication-service/bin/mas-cli manage verify-email some.username email@example.com`"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:461
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-matrix-authentication-service.md:463
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-authentication-service`."
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,261 +18,305 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook-synapse.md:1
#: ../../../docs/configuring-playbook-synapse.md:12
msgid "Configuring Synapse (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:3
#: ../../../docs/configuring-playbook-synapse.md:14
msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, so that it works for the general case. If that's okay, you can skip this document."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:5
#: ../../../docs/configuring-playbook-synapse.md:16
msgid "💡 See this page for details about maintaining Synapse: [Synapse maintenance](maintenance-synapse.md)"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:18
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:7
#: ../../../docs/configuring-playbook-synapse.md:20
msgid "Load balancing with workers"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:9
#: ../../../docs/configuring-playbook-synapse.md:22
msgid "To have Synapse gracefully handle thousands of users, worker support should be enabled. It factors out some homeserver tasks and spreads the load of incoming client and server-to-server traffic between multiple processes. More information can be found in the [official Synapse workers documentation](https://github.com/element-hq/synapse/blob/master/docs/workers.md) and [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:11
#: ../../../docs/configuring-playbook-synapse.md:24
msgid "To enable Synapse worker support, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:19
#: ../../../docs/configuring-playbook-synapse.md:32
msgid "By default, this enables the `one-of-each` [worker preset](#worker-presets), but you may wish to use another preset or [control the number of worker instances](#controlling-the-number-of-worker-instances)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:21
#: ../../../docs/configuring-playbook-synapse.md:34
msgid "Worker presets"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:23
#: ../../../docs/configuring-playbook-synapse.md:36
msgid "We support a few configuration presets (`matrix_synapse_workers_preset: one-of-each` being the default configuration right now):"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:25
#: ../../../docs/configuring-playbook-synapse.md:38
msgid "(federation-only) `little-federation-helper` — a very minimal worker configuration to improve federation performance"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:26
#: ../../../docs/configuring-playbook-synapse.md:39
msgid "(generic) `one-of-each` — defaults to one worker of each supported type — no smart routing, just generic workers"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:27
#: ../../../docs/configuring-playbook-synapse.md:40
msgid "(specialized) `specialized-workers` — defaults to one worker of each supported type, but disables generic workers and uses [specialized workers](#specialized-workers) instead"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:29
#: ../../../docs/configuring-playbook-synapse.md:42
msgid "These presets represent a few common configurations. There are many worker types which can be mixed and matched based on your needs."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:31
#: ../../../docs/configuring-playbook-synapse.md:44
msgid "Generic workers"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:33
#: ../../../docs/configuring-playbook-synapse.md:46
msgid "Previously, the playbook only supported the most basic type of load-balancing. We call it **generic load-balancing** below, because incoming HTTP requests are sent to a generic worker. Load-balancing was done based on the requestor's IP address. This is simple, but not necessarily optimal. If you're accessing your account from multiple IP addresses (e.g. your mobile phone being on a different network than your PC), these separate requests may potentially be routed to different workers, each of which would need to cache roughly the same data."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:35
#: ../../../docs/configuring-playbook-synapse.md:48
msgid "This is **still the default load-balancing method (preset) used by the playbook**."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:37
#: ../../../docs/configuring-playbook-synapse.md:50
msgid "To use generic load-balancing, do not specify `matrix_synapse_workers_preset` to make it use the default value (`one-of-each`), or better yet — explicitly set it as `one-of-each`."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:39
#: ../../../docs/configuring-playbook-synapse.md:52
msgid "You may also consider [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:41
#: ../../../docs/configuring-playbook-synapse.md:54
msgid "Specialized workers"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:43
msgid "The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requestor's IP adddress, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** — the access token (username) of the requestor and/or on the resource (room, etc.) being requested."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:45
msgid "The playbook supports these **4 types** of specialized workers:"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:47
msgid "Room workers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) & [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs dedicated to handling specific rooms"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:48
msgid "Sync workers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to synchronization (most notably [the `/sync` endpoint](https://spec.matrix.org/v1.9/client-server-api/#get_matrixclientv3sync))"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:49
msgid "Client readers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are not for specific rooms (handled by **room workers**) or for synchronization (handled by **sync workers**)"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:50
msgid "Federation readers — handles various [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which are not for specific rooms (handled by **room workers**)"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:52
msgid "To use specialized load-balancing, consider enabling the `specialized-workers` [worker preset](#worker-presets) and potentially [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:54
msgid "Controlling the number of worker instances"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:56
msgid "If you'd like more customization power, you can start with one of the [worker presets](#worker-presets) and then tweak various `matrix_synapse_workers_*_count` variables manually."
msgid "The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requester's IP address, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** — the access token (username) of the requester and/or on the resource (room, etc.) being requested."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:58
msgid "To find what variables are available for you to override in your own `vars.yml` configuration file, see the [`defaults/main.yml` file for the `matrix-synapse` Ansible role](../roles/custom/matrix-synapse/defaults/main.yml)."
msgid "The playbook supports these **4 types** of specialized workers:"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:60
msgid "The only thing you **cannot** do is mix [generic workers](#generic-workers) and [specialized workers](#specialized-workers)."
msgid "Room workers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) & [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs dedicated to handling specific rooms"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:61
msgid "Sync workers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to synchronization (most notably [the `/sync` endpoint](https://spec.matrix.org/v1.9/client-server-api/#get_matrixclientv3sync))"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:62
msgid "Client readers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are not for specific rooms (handled by **room workers**) or for synchronization (handled by **sync workers**)"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:63
msgid "Federation readers — handles various [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which are not for specific rooms (handled by **room workers**)"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:65
msgid "To use specialized load-balancing, consider enabling the `specialized-workers` [worker preset](#worker-presets) and potentially [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:67
msgid "Controlling the number of worker instances"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:69
msgid "If you'd like more customization power, you can start with one of the [worker presets](#worker-presets) and then tweak various `matrix_synapse_workers_*_count` variables manually."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:71
msgid "To find what variables are available for you to override in your own `vars.yml` configuration file, see the [`defaults/main.yml` file for the `matrix-synapse` Ansible role](../roles/custom/matrix-synapse/defaults/main.yml)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:73
msgid "The only thing you **cannot** do is mix [generic workers](#generic-workers) and [specialized workers](#specialized-workers)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:75
msgid "Effect of enabling workers on the rest of your server"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:64
#: ../../../docs/configuring-playbook-synapse.md:77
msgid "When Synapse workers are enabled, the integrated [Postgres database is tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum number of Postgres connections are increased from `200` to `500`. If you need to decrease or increase the number of maximum Postgres connections further, use the `postgres_max_connections` variable."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:66
msgid "A separate Ansible role (`matrix-synapse-reverse-proxy-companion`) and component handles load-balancing for workers. This role/component is automatically enabled when you enable workers. Make sure to use the `setup-all` tag (not `install-all`!) during the playbook's [installation](./installing.md) process, especially if you're disabling workers, so that components may be installed/uninstalled correctly."
#: ../../../docs/configuring-playbook-synapse.md:79
msgid "The `matrix-synapse` role also manages the `matrix-synapse-reverse-proxy-companion` component for load-balancing with workers. This component is automatically enabled when you enable workers. Make sure to use the `setup-all` tag (not `install-all`!) during the playbook's [installation](./installing.md) process, especially if you're disabling workers, so that components may be installed/uninstalled correctly."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:68
#: ../../../docs/configuring-playbook-synapse.md:81
msgid "In case any problems occur, make sure to have a look at the [list of synapse issues about workers](https://github.com/element-hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit 'matrix-*'`."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:70
#: ../../../docs/configuring-playbook-synapse.md:83
msgid "Limit joining heavy rooms on constrained hosts"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:85
msgid "If your server is underpowered, joining heavy rooms can cause Synapse to consume a lot of resources and be unavailable for long (while it catches up)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:87
msgid "To avoid this, Synapse can be configured to reject joins for remote rooms that are too complex before users enter them."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:89
msgid "Complexity is computed as `current_state_events / 500` (Synapse state event count for current room state). When the resulting value is higher than `matrix_synapse_limit_remote_rooms_complexity` and `matrix_synapse_limit_remote_rooms_enabled` is `true`, Synapse blocks joining the room."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:91
msgid "We recommend using this as a guardrail on low-resource servers:"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:106
msgid "Synapse + OpenID Connect for Single-Sign-On"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:72
#: ../../../docs/configuring-playbook-synapse.md:108
msgid "💡 An alternative to setting up OIDC in Synapse is to use [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS). Newer clients (like Element X) only support SSO-based authentication via MAS and not via the legacy Synapse OIDC setup described below. That said, MAS is still a new experimental service which comes with its own downsides. Consult its documentation to learn if it will be a good fit for your deployment."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:74
#: ../../../docs/configuring-playbook-synapse.md:110
msgid "If you'd like to use OpenID Connect authentication with Synapse, you'll need some additional configuration."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:76
#: ../../../docs/configuring-playbook-synapse.md:112
msgid "This example configuration is for [keycloak](https://www.keycloak.org/), an opensource Identity Provider maintained by Red Hat."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:78
#: ../../../docs/configuring-playbook-synapse.md:114
msgid "For more detailed documentation on available options and how to setup keycloak, see the [Synapse documentation on OpenID Connect with keycloak](https://github.com/element-hq/synapse/blob/develop/docs/openid.md#keycloak)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:80
#, python-format
#: ../../../docs/configuring-playbook-synapse.md:116
#, python-format, python-brace-format
msgid "In case you encounter errors regarding the parsing of the variables, you can try to add `{% raw %}` and `{% endraw %}` blocks around them. For example ;"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:101
#: ../../../docs/configuring-playbook-synapse.md:137
msgid "Customizing templates"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:103
#: ../../../docs/configuring-playbook-synapse.md:139
msgid "[Templates](https://github.com/element-hq/synapse/blob/develop/docs/templates.md) are used by Synapse for showing **certain web pages** handled by the server, as well as for **email notifications**."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:105
#: ../../../docs/configuring-playbook-synapse.md:141
msgid "This playbook allows you to customize the default templates (see the [`synapse/res/templates` directory](https://github.com/element-hq/synapse/tree/develop/synapse/res/templates))."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:107
#: ../../../docs/configuring-playbook-synapse.md:143
msgid "If template customization is enabled, the playbook will build a custom container image based on the official one."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:109
#: ../../../docs/configuring-playbook-synapse.md:145
msgid "Your custom templates need to live in a public or private git repository. This repository will be cloned during Synapse image customization (during the playbook run)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:111
#: ../../../docs/configuring-playbook-synapse.md:147
msgid "To enable template customizations, add the following configuration to your `vars.yml` file (adapt to your needs):"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:137
#: ../../../docs/configuring-playbook-synapse.md:173
msgid "As mentioned in Synapse's Templates documentation, Synapse will fall back to its own templates if a template is not found in that directory. Due to this, it's recommended to only store and maintain template files in your repository if you need to make custom changes. Other files (which you don't need to change), should not be duplicated, so that you don't need to worry about getting out-of-sync with the original Synapse templates."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:139
#: ../../../docs/configuring-playbook-synapse.md:175
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:141
#: ../../../docs/configuring-playbook-synapse.md:177
msgid "There are some additional things you may wish to configure about the server."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:143
#: ../../../docs/configuring-playbook-synapse.md:179
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:145
#: ../../../docs/configuring-playbook-synapse.md:181
msgid "`roles/custom/matrix-synapse/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:146
#: ../../../docs/configuring-playbook-synapse.md:182
msgid "`roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2` for the server's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_synapse_configuration_extension_yaml` variable"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:148
#: ../../../docs/configuring-playbook-synapse.md:184
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:150
#: ../../../docs/configuring-playbook-synapse.md:186
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:157
#: ../../../docs/configuring-playbook-synapse.md:193
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:159
#: ../../../docs/configuring-playbook-synapse.md:195
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:161
#: ../../../docs/configuring-playbook-synapse.md:197
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:163
msgid "Synapse Admin"
#: ../../../docs/configuring-playbook-synapse.md:199
msgid "Ketesa"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:165
msgid "With [Synapse Admin](configuring-playbook-synapse-admin.md), certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace."
#: ../../../docs/configuring-playbook-synapse.md:201
msgid "[Ketesa](configuring-playbook-ketesa.md) is a fully-featured web UI for administrating your homeserver — managing users, rooms, media, sessions, and more."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:167
msgid "The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)."
#: ../../../docs/configuring-playbook-synapse.md:203
msgid "The playbook can install and configure Ketesa for you. For details about it, see [this page](configuring-playbook-ketesa.md)."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:169
#: ../../../docs/configuring-playbook-synapse.md:205
msgid "Monitoring Synapse Metrics with Prometheus and Grafana"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:171
#: ../../../docs/configuring-playbook-synapse.md:207
msgid "This playbook allows you to enable Synapse metrics, which can provide insight into the performance and activity of Synapse."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:173
msgid "To enable Synapse runtime metrics see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)"
#: ../../../docs/configuring-playbook-synapse.md:209
msgid "To enable Synapse runtime metrics, see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md) and [its subsection](configuring-playbook-prometheus-grafana.md#expose-metrics-of-other-services-roles)"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:175
#: ../../../docs/configuring-playbook-synapse.md:211
msgid "To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:213
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:215
msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-synapse`."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:217
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:219
msgid "Because Synapse is originally very chatty when it comes to logging, we intentionally reduce its [logging level](https://docs.python.org/3/library/logging.html#logging-levels) from `INFO` to `WARNING`."
msgstr ""
#: ../../../docs/configuring-playbook-synapse.md:221
msgid "If you'd like to debug an issue or [report a Synapse bug](https://github.com/element-hq/synapse/issues/new/choose) to the developers, it'd be better if you temporarily increase the logging verbosity to `INFO`. To do so, add the following configuration to your `vars.yml` file and re-run the playbook:"
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,528 +18,568 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/configuring-playbook.md:1
#: ../../../docs/configuring-playbook.md:17
msgid "Configuring the playbook"
msgstr ""
#: ../../../docs/configuring-playbook.md:3
msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md)</sup>"
msgstr ""
#: ../../../docs/configuring-playbook.md:5
msgid "If you've configured your DNS records and retrieved the playbook's source code to your computer, you can start configuring the playbook. To do so, follow these steps inside the playbook directory:"
msgstr ""
#: ../../../docs/configuring-playbook.md:7
msgid "create a directory to hold your configuration (`mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\")"
msgstr ""
#: ../../../docs/configuring-playbook.md:9
msgid "copy the sample configuration file (`cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`)"
msgstr ""
#: ../../../docs/configuring-playbook.md:11
msgid "edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You may also take a look at the various `roles/*/ROLE_NAME_HERE/defaults/main.yml` files and see if there's something you'd like to copy over and override in your `vars.yml` configuration file."
msgstr ""
#: ../../../docs/configuring-playbook.md:13
msgid "copy the sample inventory hosts file (`cp examples/hosts inventory/hosts`)"
msgstr ""
#: ../../../docs/configuring-playbook.md:15
msgid "edit the inventory hosts file (`inventory/hosts`) to your liking"
msgstr ""
#: ../../../docs/configuring-playbook.md:17
msgid "(optional, advanced) you may wish to keep your `inventory` directory under version control with [git](https://git-scm.com/) or any other version-control system."
msgstr ""
#: ../../../docs/configuring-playbook.md:19
msgid "(optional, advanced) to run Ansible against multiple servers with different `sudo` credentials, you can copy the sample inventory hosts yaml file for each of your hosts: (`cp examples/host.yml inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin/ansible-all-hosts.sh) script [in the installation step](installing.md)."
msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md)</sup>"
msgstr ""
#: ../../../docs/configuring-playbook.md:21
msgid "For a basic Matrix installation, that's all you need."
msgid "If you've configured your DNS records and retrieved the playbook's source code to your computer, you can start configuring the playbook. To do so, follow these steps inside the playbook directory:"
msgstr ""
#: ../../../docs/configuring-playbook.md:23
msgid "For a more custom setup, see the [Other configuration options](#other-configuration-options) below."
msgid "create a directory to hold your configuration (`mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\")"
msgstr ""
#: ../../../docs/configuring-playbook.md:25
msgid "[▶️](installing.md) When you're done with all the configuration you'd like to do, continue with [Installing](installing.md)."
msgid "copy the sample configuration file (`cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`)"
msgstr ""
#: ../../../docs/configuring-playbook.md:27
msgid "Other configuration options"
msgid "edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You may also take a look at the various `roles/*/ROLE_NAME_HERE/defaults/main.yml` files (after importing external roles with `just update` into `roles/galaxy`) and see if there's something you'd like to copy over and override in your `vars.yml` configuration file."
msgstr ""
#: ../../../docs/configuring-playbook.md:29
msgid "**Note**: some of the roles like one for integrating Etherpad or Jitsi are managed by their own repositories, and the configuration files for them cannot be found locally (in `roles/galaxy`) until those roles are fetched from the upstream projects. Check [requirements.yml](../requirements.yml) for the URLs of those roles."
msgid "copy the sample inventory hosts file (`cp examples/hosts inventory/hosts`)"
msgstr ""
#: ../../../docs/configuring-playbook.md:31
msgid "Core service adjustments"
msgid "edit the inventory hosts file (`inventory/hosts`) to your liking"
msgstr ""
#: ../../../docs/configuring-playbook.md:33
msgid "Homeserver configuration:"
msgid "(optional, advanced) you may wish to keep your `inventory` directory under version control with [git](https://git-scm.com/) or any other version-control system. The `inventory` directory path is ignored via `.gitignore`, so it won't be part of the playbook repository. You can safely create a new git repository inside that directory with `git init`, etc."
msgstr ""
#: ../../../docs/configuring-playbook.md:34
msgid "[Configuring Synapse](configuring-playbook-synapse.md), if you're going with the default/recommended homeserver implementation"
#: ../../../docs/configuring-playbook.md:35
msgid "(optional, advanced) to run Ansible against multiple servers with different `sudo` credentials, you can copy the sample inventory hosts yaml file for each of your hosts: (`cp examples/host.yml inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin/ansible-all-hosts.sh) script [in the installation step](installing.md)."
msgstr ""
#: ../../../docs/configuring-playbook.md:36
msgid "[Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation"
#: ../../../docs/configuring-playbook.md:37
msgid "For a basic Matrix installation, that's all you need."
msgstr ""
#: ../../../docs/configuring-playbook.md:38
msgid "[Configuring conduwuit](configuring-playbook-conduwuit.md), if you've switched to the [conduwuit](https://conduwuit.puppyirl.gay/) homeserver implementation"
#: ../../../docs/configuring-playbook.md:39
msgid "For a more custom setup, see the [Other configuration options](#other-configuration-options) below."
msgstr ""
#: ../../../docs/configuring-playbook.md:40
msgid "[Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation"
msgstr ""
#: ../../../docs/configuring-playbook.md:42
msgid "Server components:"
#: ../../../docs/configuring-playbook.md:41
msgid "[▶️](installing.md) When you're done with all the configuration you'd like to do, continue with [Installing](installing.md)."
msgstr ""
#: ../../../docs/configuring-playbook.md:43
msgid "[Using an external PostgreSQL server](configuring-playbook-external-postgres.md)"
msgid "Other configuration options"
msgstr ""
#: ../../../docs/configuring-playbook.md:45
msgid "[Configuring a TURN server](configuring-playbook-turn.md) (advanced)"
msgid "**Note**: some of the roles like one for integrating Etherpad or Jitsi are managed by their own repositories, and the configuration files for them cannot be found locally (in `roles/galaxy`) until those roles are fetched from the upstream projects. Check [requirements.yml](../requirements.yml) for the URLs of those roles."
msgstr ""
#: ../../../docs/configuring-playbook.md:47
msgid "[Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) (advanced)"
msgid "Core service adjustments"
msgstr ""
#: ../../../docs/configuring-playbook.md:49
msgid "[Using your own webserver, instead of this playbook's Traefik reverse-proxy](configuring-playbook-own-webserver.md) (advanced)"
msgid "Homeserver configuration:"
msgstr ""
#: ../../../docs/configuring-playbook.md:51
msgid "[Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) (advanced)"
#: ../../../docs/configuring-playbook.md:50
msgid "[Configuring Synapse](configuring-playbook-synapse.md), if you're going with the default/recommended homeserver implementation"
msgstr ""
#: ../../../docs/configuring-playbook.md:53
msgid "[Adjusting email-sending settings](configuring-playbook-email.md)"
#: ../../../docs/configuring-playbook.md:52
msgid "[Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation"
msgstr ""
#: ../../../docs/configuring-playbook.md:55
msgid "[Setting up ma1sd Identity Server](configuring-playbook-ma1sd.md)"
#: ../../../docs/configuring-playbook.md:54
msgid "[Configuring continuwuity](configuring-playbook-continuwuity.md), if you've switched to the [continuwuity](https://continuwuity.org) homeserver implementation"
msgstr ""
#: ../../../docs/configuring-playbook.md:57
msgid "[Setting up Dynamic DNS](configuring-playbook-dynamic-dns.md)"
#: ../../../docs/configuring-playbook.md:56
msgid "[Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation"
msgstr ""
#: ../../../docs/configuring-playbook.md:58
msgid "Server components:"
msgstr ""
#: ../../../docs/configuring-playbook.md:59
msgid "[Using an external PostgreSQL server](configuring-playbook-external-postgres.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:61
msgid "[Configuring a TURN server](configuring-playbook-turn.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:63
msgid "[Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:65
msgid "[Using your own webserver, instead of this playbook's Traefik reverse-proxy](configuring-playbook-own-webserver.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:67
msgid "[Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:69
msgid "[Adjusting email-sending settings](configuring-playbook-email.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:71
msgid "[Setting up Dynamic DNS](configuring-playbook-dynamic-dns.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:73
msgid "Server connectivity:"
msgstr ""
#: ../../../docs/configuring-playbook.md:60
#: ../../../docs/configuring-playbook.md:74
msgid "[Enabling Telemetry for your Matrix server](configuring-playbook-telemetry.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:62
#: ../../../docs/configuring-playbook.md:76
msgid "[Controlling Matrix federation](configuring-playbook-federation.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:64
msgid "Clients"
msgstr ""
#: ../../../docs/configuring-playbook.md:66
msgid "Web clients for Matrix that you can host on your own domains."
msgstr ""
#: ../../../docs/configuring-playbook.md:68
msgid "[Configuring Element Web](configuring-playbook-client-element-web.md), if you're going with the default/recommended client"
msgstr ""
#: ../../../docs/configuring-playbook.md:70
msgid "[Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a lightweight Matrix client with legacy and mobile browser support"
msgstr ""
#: ../../../docs/configuring-playbook.md:72
msgid "[Setting up Cinny](configuring-playbook-client-cinny.md), if you've enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing primarily on simple, elegant and secure interface"
msgstr ""
#: ../../../docs/configuring-playbook.md:74
msgid "[Setting up SchildiChat Web](configuring-playbook-client-schildichat-web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a web client based on [Element Web](https://element.io/) with some extras and tweaks"
msgstr ""
#: ../../../docs/configuring-playbook.md:76
msgid "Authentication and user-related"
msgstr ""
#: ../../../docs/configuring-playbook.md:78
msgid "Extend and modify how users are authenticated on your homeserver."
msgid "[Configuring IPv6](./configuring-ipv6.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:80
msgid "[Setting up Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (Next-generation auth for Matrix, based on OAuth 2.0/OIDC)"
msgid "Clients"
msgstr ""
#: ../../../docs/configuring-playbook.md:82
msgid "[Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)"
msgid "Web clients for Matrix that you can host on your own domains."
msgstr ""
#: ../../../docs/configuring-playbook.md:84
msgid "[Setting up Synapse Admin](configuring-playbook-synapse-admin.md)"
msgid "[Configuring Element Web](configuring-playbook-client-element-web.md), if you're going with the default/recommended client"
msgstr ""
#: ../../../docs/configuring-playbook.md:86
msgid "[Setting up matrix-registration](configuring-playbook-matrix-registration.md)"
msgid "[Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a lightweight Matrix client with legacy and mobile browser support"
msgstr ""
#: ../../../docs/configuring-playbook.md:88
msgid "[Setting up the REST authentication password provider module](configuring-playbook-rest-auth.md) (advanced)"
msgid "[Setting up Cinny](configuring-playbook-client-cinny.md), if you've enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing primarily on simple, elegant and secure interface"
msgstr ""
#: ../../../docs/configuring-playbook.md:90
msgid "[Setting up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) (advanced)"
msgid "[Setting up Sable](configuring-playbook-client-sable.md), if you've enabled [Sable](https://github.com/7w1/sable), a web client focusing primarily on simple, elegant and secure interface"
msgstr ""
#: ../../../docs/configuring-playbook.md:92
msgid "[Setting up the LDAP authentication password provider module](configuring-playbook-ldap-auth.md) (advanced)"
msgid "[Setting up SchildiChat Web](configuring-playbook-client-schildichat-web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a web client based on [Element Web](https://element.io/) with some extras and tweaks"
msgstr ""
#: ../../../docs/configuring-playbook.md:94
msgid "[Setting up FluffyChat Web](configuring-playbook-client-fluffychat-web.md), if you've enabled [FluffyChat Web](https://github.com/krille-chan/fluffychat), a cute cross-platform messenger (web, iOS, Android) for Matrix written in [Flutter](https://flutter.dev/)"
msgstr ""
#: ../../../docs/configuring-playbook.md:97
msgid "Authentication and user-related"
msgstr ""
#: ../../../docs/configuring-playbook.md:99
msgid "Extend and modify how users are authenticated on your homeserver."
msgstr ""
#: ../../../docs/configuring-playbook.md:101
msgid "[Setting up Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (Next-generation auth for Matrix, based on OAuth 2.0/OIDC)"
msgstr ""
#: ../../../docs/configuring-playbook.md:103
msgid "[Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:105
msgid "[Setting up Ketesa](configuring-playbook-ketesa.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:107
msgid "[Setting up matrix-registration](configuring-playbook-matrix-registration.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:109
msgid "[Setting up the REST authentication password provider module](configuring-playbook-rest-auth.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:111
msgid "[Setting up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:113
msgid "[Setting up the LDAP authentication password provider module](configuring-playbook-ldap-auth.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:115
msgid "[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:96
#: ../../../docs/configuring-playbook.md:117
msgid "[Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:98
#: ../../../docs/configuring-playbook.md:119
msgid "[Setting up Matrix User Verification Service](configuring-playbook-user-verification-service.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:100
#: ../../../docs/configuring-playbook.md:121
msgid "File Storage"
msgstr ""
#: ../../../docs/configuring-playbook.md:102
#: ../../../docs/configuring-playbook.md:123
msgid "Use alternative file storage to the default `media_store` folder."
msgstr ""
#: ../../../docs/configuring-playbook.md:104
msgid "[Storing Matrix media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:106
msgid "[Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:108
#: ../../../docs/configuring-playbook.md:125
msgid "[Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:110
#: ../../../docs/configuring-playbook.md:127
msgid "[Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:129
msgid "[Storing Synapse media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:131
msgid "[Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:133
msgid "Bridging other networks"
msgstr ""
#: ../../../docs/configuring-playbook.md:112
#: ../../../docs/configuring-playbook.md:135
msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
msgstr ""
#: ../../../docs/configuring-playbook.md:114
#: ../../../docs/configuring-playbook.md:137
msgid "[Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) — a common guide for configuring mautrix bridges"
msgstr ""
#: ../../../docs/configuring-playbook.md:116
#: ../../../docs/configuring-playbook.md:139
msgid "[Setting up Mautrix Bluesky bridging](configuring-playbook-bridge-mautrix-bluesky.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:141
msgid "[Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:118
#: ../../../docs/configuring-playbook.md:143
msgid "[Setting up Mautrix Telegram bridging](configuring-playbook-bridge-mautrix-telegram.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:120
#: ../../../docs/configuring-playbook.md:145
msgid "[Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:122
#: ../../../docs/configuring-playbook.md:147
msgid "[Setting up Mautrix Google Messages bridging](configuring-playbook-bridge-mautrix-gmessages.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:124
#: ../../../docs/configuring-playbook.md:149
msgid "[Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-mautrix-whatsapp.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:126
#: ../../../docs/configuring-playbook.md:151
msgid "[Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:128
#: ../../../docs/configuring-playbook.md:153
msgid "[Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:130
#: ../../../docs/configuring-playbook.md:155
msgid "[Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-mautrix-googlechat.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:132
#: ../../../docs/configuring-playbook.md:157
msgid "[Setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:134
#: ../../../docs/configuring-playbook.md:159
msgid "[Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-signal.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:136
#: ../../../docs/configuring-playbook.md:161
msgid "[Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](configuring-playbook-bridge-mautrix-wsproxy.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:138
#: ../../../docs/configuring-playbook.md:163
msgid "[Setting up Appservice IRC bridging](configuring-playbook-bridge-appservice-irc.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:140
#: ../../../docs/configuring-playbook.md:165
msgid "[Setting up Appservice Discord bridging](configuring-playbook-bridge-appservice-discord.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:142
msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:144
#: ../../../docs/configuring-playbook.md:167
msgid "[Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-appservice-kakaotalk.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:146
#: ../../../docs/configuring-playbook.md:169
msgid "[Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-linkedin.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:148
#: ../../../docs/configuring-playbook.md:171
msgid "[Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) — a bridge between Matrix and multiple project management services, such as [GitHub](https://github.com), [GitLab](https://about.gitlab.com) and [JIRA](https://www.atlassian.com/software/jira)."
msgstr ""
#: ../../../docs/configuring-playbook.md:150
msgid "[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:152
msgid "[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-puppet-instagram.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:154
msgid "[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:156
msgid "[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-puppet-discord.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:158
#: ../../../docs/configuring-playbook.md:173
msgid "[Setting up MX Puppet GroupMe bridging](configuring-playbook-bridge-mx-puppet-groupme.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:160
#: ../../../docs/configuring-playbook.md:175
msgid "[Setting up Steam bridging](configuring-playbook-bridge-steam.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:177
msgid "[Setting up MX Puppet Steam bridging](configuring-playbook-bridge-mx-puppet-steam.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:162
msgid "[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:164
#: ../../../docs/configuring-playbook.md:179
msgid "[Setting up Postmoogle email bridging](configuring-playbook-bridge-postmoogle.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:166
#: ../../../docs/configuring-playbook.md:181
msgid "[Setting up Matrix SMS bridging](configuring-playbook-bridge-matrix-bridge-sms.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:168
#: ../../../docs/configuring-playbook.md:183
msgid "[Setting up Heisenbridge bouncer-style IRC bridging](configuring-playbook-bridge-heisenbridge.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:170
#: ../../../docs/configuring-playbook.md:185
msgid "[Setting up WeChat bridging](configuring-playbook-bridge-wechat.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:172
#: ../../../docs/configuring-playbook.md:187
msgid "Bots"
msgstr ""
#: ../../../docs/configuring-playbook.md:174
#: ../../../docs/configuring-playbook.md:189
msgid "Bots provide various additional functionality to your installation."
msgstr ""
#: ../../../docs/configuring-playbook.md:176
#: ../../../docs/configuring-playbook.md:191
msgid "[Setting up baibot](configuring-playbook-bot-baibot.md) — a bot through which you can talk to various [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) services ([OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) and [others](https://github.com/etkecc/baibot/blob/main/docs/providers.md))"
msgstr ""
#: ../../../docs/configuring-playbook.md:178
#: ../../../docs/configuring-playbook.md:193
msgid "[Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md) — a bot to remind you about stuff"
msgstr ""
#: ../../../docs/configuring-playbook.md:180
#: ../../../docs/configuring-playbook.md:195
msgid "[Setting up matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) — a bot to create and manage registration tokens to invite users"
msgstr ""
#: ../../../docs/configuring-playbook.md:182
#: ../../../docs/configuring-playbook.md:197
msgid "[Setting up maubot](configuring-playbook-bot-maubot.md) — a plugin-based Matrix bot system"
msgstr ""
#: ../../../docs/configuring-playbook.md:184
#: ../../../docs/configuring-playbook.md:199
msgid "[Setting up Honoroit](configuring-playbook-bot-honoroit.md) — a helpdesk bot"
msgstr ""
#: ../../../docs/configuring-playbook.md:186
#: ../../../docs/configuring-playbook.md:201
msgid "[Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) — a moderation tool/bot"
msgstr ""
#: ../../../docs/configuring-playbook.md:188
#: ../../../docs/configuring-playbook.md:203
msgid "[Setting up Draupnir](configuring-playbook-bot-draupnir.md) — a moderation tool/bot, forked from Mjolnir and maintained by its former leader developer"
msgstr ""
#: ../../../docs/configuring-playbook.md:190
#: ../../../docs/configuring-playbook.md:205
msgid "[Setting up Draupnir for all/D4A](configuring-playbook-appservice-draupnir-for-all.md) — like the [Draupnir bot](configuring-playbook-bot-draupnir.md) mentioned above, but running in appservice mode and supporting multiple instances"
msgstr ""
#: ../../../docs/configuring-playbook.md:192
#: ../../../docs/configuring-playbook.md:207
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:194
#: ../../../docs/configuring-playbook.md:209
msgid "Administration"
msgstr ""
#: ../../../docs/configuring-playbook.md:196
#: ../../../docs/configuring-playbook.md:211
msgid "Services that help you in administrating and monitoring your Matrix installation."
msgstr ""
#: ../../../docs/configuring-playbook.md:198
#: ../../../docs/configuring-playbook.md:213
msgid "[Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:200
#: ../../../docs/configuring-playbook.md:215
msgid "[Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:202
msgid "[Enabling metrics and graphs for NginX logs](configuring-playbook-prometheus-nginxlog.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:204
#: ../../../docs/configuring-playbook.md:217
msgid "[Setting up the rageshake bug report server](configuring-playbook-rageshake.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:206
#: ../../../docs/configuring-playbook.md:219
msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:208
#: ../../../docs/configuring-playbook.md:221
msgid "Backups:"
msgstr ""
#: ../../../docs/configuring-playbook.md:209
#: ../../../docs/configuring-playbook.md:222
msgid "[Setting up BorgBackup](configuring-playbook-backup-borg.md) — a full Matrix server backup solution, including the Postgres database"
msgstr ""
#: ../../../docs/configuring-playbook.md:211
msgid "[Setting up postgres backup](configuring-playbook-postgres-backup.md) — a Postgres-database backup solution (note: does not include other files)"
#: ../../../docs/configuring-playbook.md:224
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:213
#: ../../../docs/configuring-playbook.md:226
msgid "Other specialized services"
msgstr ""
#: ../../../docs/configuring-playbook.md:215
#: ../../../docs/configuring-playbook.md:228
msgid "Various services that don't fit any other categories."
msgstr ""
#: ../../../docs/configuring-playbook.md:217
msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md)"
#: ../../../docs/configuring-playbook.md:230
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:219
#: ../../../docs/configuring-playbook.md:232
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:234
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:236
msgid "[Setting up Matrix RTC](configuring-playbook-matrix-rtc.md) (optional)"
msgstr ""
#: ../../../docs/configuring-playbook.md:238
msgid "[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers"
msgstr ""
#: ../../../docs/configuring-playbook.md:221
#: ../../../docs/configuring-playbook.md:240
msgid "[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:223
#: ../../../docs/configuring-playbook.md:242
msgid "[Setting up Matrix.to](configuring-playbook-matrixto.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:244
msgid "[Setting up Etherpad](configuring-playbook-etherpad.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:225
#: ../../../docs/configuring-playbook.md:246
msgid "[Setting up the Jitsi video-conferencing platform](configuring-playbook-jitsi.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:227
#: ../../../docs/configuring-playbook.md:248
msgid "[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) — a federated comment system built on Matrix"
msgstr ""
#: ../../../docs/configuring-playbook.md:229
#: ../../../docs/configuring-playbook.md:250
msgid "[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-pantalaimon.md) (advanced)"
msgstr ""
#: ../../../docs/configuring-playbook.md:231
#: ../../../docs/configuring-playbook.md:252
msgid "[Setting up the Sygnal push gateway](configuring-playbook-sygnal.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:233
#: ../../../docs/configuring-playbook.md:254
msgid "[Setting up the ntfy push notifications server](configuring-playbook-ntfy.md)"
msgstr ""
#: ../../../docs/configuring-playbook.md:235
#: ../../../docs/configuring-playbook.md:256
msgid "Deprecated / unmaintained / removed services"
msgstr ""
#: ../../../docs/configuring-playbook.md:237
#: ../../../docs/configuring-playbook.md:258
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:239
#: ../../../docs/configuring-playbook.md:260
msgid "[Configuring conduwuit](configuring-playbook-conduwuit.md) (removed; this component has been abandoned and unmaintained)"
msgstr ""
#: ../../../docs/configuring-playbook.md:262
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:241
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))"
#: ../../../docs/configuring-playbook.md:264
msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md) (removed; this component has been discontinued)"
msgstr ""
#: ../../../docs/configuring-playbook.md:243
#: ../../../docs/configuring-playbook.md:266
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:268
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:245
msgid "[Setting up Email2Matrix](configuring-playbook-email2matrix.md) (unmaintained; 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))"
#: ../../../docs/configuring-playbook.md:270
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:247
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))"
#: ../../../docs/configuring-playbook.md:272
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:249
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))"
#: ../../../docs/configuring-playbook.md:274
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:251
#: ../../../docs/configuring-playbook.md:276
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:278
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:280
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:253
msgid "[Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-mautrix-hangouts.md) (deprecated in favor of the Google Chat bridge with [mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md))"
msgstr ""
#: ../../../docs/configuring-playbook.md:255
#: ../../../docs/configuring-playbook.md:282
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:257
#: ../../../docs/configuring-playbook.md:284
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:286
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:288
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:290
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:292
msgid "[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md))"
msgstr ""
#: ../../../docs/configuring-playbook.md:294
msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md) (removed; since Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0) the same feature is available natively.)"
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,21 +18,21 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/container-images.md:1
#: ../../../docs/container-images.md:18
msgid "Container images used by the playbook"
msgstr ""
#: ../../../docs/container-images.md:3
#: ../../../docs/container-images.md:20
msgid "This page summarizes the container ([Docker](https://www.docker.com/)) images used by the playbook when setting up your server."
msgstr ""
#: ../../../docs/container-images.md:5
#: ../../../docs/container-images.md:22
msgid "We try to stick to official images (provided by their respective projects) as much as possible."
msgstr ""
#: ../../../docs/container-images.md:7
#: ../../../docs/container-images.md:24
msgid "Homeserver"
msgstr ""
@@ -85,15 +85,15 @@ msgid "Storing your data and managing your presence in the [Matrix](http://matri
msgstr ""
#: ../../../docs/container-images.md
msgid "[conduwuit](configuring-playbook-conduwuit.md)"
msgid "[continuwuity](configuring-playbook-continuwuity.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[girlbossceo/conduwuit](https://ghcr.io/girlbossceo/conduwuit)"
msgid "[continuwuation/continuwuity](https://forgejo.ellis.link/continuwuation/continuwuity)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit is a fork of Conduit."
msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. continuwuity is a continuation of conduwuit."
msgstr ""
#: ../../../docs/container-images.md
@@ -108,11 +108,11 @@ msgstr ""
msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse."
msgstr ""
#: ../../../docs/container-images.md:16
#: ../../../docs/container-images.md:33
msgid "Clients"
msgstr ""
#: ../../../docs/container-images.md:18
#: ../../../docs/container-images.md:35
msgid "Web clients for Matrix that you can host on your own domains."
msgstr ""
@@ -152,6 +152,14 @@ msgstr ""
msgid "Simple, elegant and secure web client"
msgstr ""
#: ../../../docs/container-images.md
msgid "[Sable](configuring-playbook-client-sable.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[7w1/sable](https://ghcr.io/7w1/sable)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md)"
msgstr ""
@@ -164,11 +172,11 @@ msgstr ""
msgid "Based on Element Web, with a more traditional instant messaging experience"
msgstr ""
#: ../../../docs/container-images.md:27
#: ../../../docs/container-images.md:45
msgid "Server Components"
msgstr ""
#: ../../../docs/container-images.md:29
#: ../../../docs/container-images.md:47
msgid "Services that run on the server to make the various parts of your installation work."
msgstr ""
@@ -205,7 +213,7 @@ msgid "[Traefik](https://hub.docker.com/_/traefik/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Web server, listening on ports 80, 443 and 8448 — standing in front of all the other services. Using your own webserver [is possible](configuring-playbook-own-webserver.md)"
msgid "Web server, listening on ports 80, 443 and 8448 — standing in front of all the other services. [Using your own webserver](configuring-playbook-own-webserver.md) is also possible."
msgstr ""
#: ../../../docs/container-images.md
@@ -217,7 +225,7 @@ msgid "[certbot/certbot](https://hub.docker.com/r/certbot/certbot/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "The [certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/)"
msgid "[Certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/)"
msgstr ""
#: ../../../docs/container-images.md
@@ -232,18 +240,6 @@ msgstr ""
msgid "Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[ma1sd](configuring-playbook-ma1sd.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Matrix Identity Server"
msgstr ""
#: ../../../docs/container-images.md
msgid "[ddclient](configuring-playbook-dynamic-dns.md)"
msgstr ""
@@ -256,11 +252,35 @@ msgstr ""
msgid "Update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider"
msgstr ""
#: ../../../docs/container-images.md:41
#: ../../../docs/container-images.md
msgid "[LiveKit Server](configuring-playbook-livekit-server.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[livekit/livekit-server](https://hub.docker.com/r/livekit/livekit-server/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "WebRTC server for audio/video calls"
msgstr ""
#: ../../../docs/container-images.md
msgid "[Livekit JWT Service](configuring-playbook-livekit-jwt-service.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[element-hq/lk-jwt-service](https://ghcr.io/element-hq/lk-jwt-service)"
msgstr ""
#: ../../../docs/container-images.md
msgid "JWT service for integrating [Element Call](./configuring-playbook-element-call.md) with [LiveKit Server](./configuring-playbook-livekit-server.md)"
msgstr ""
#: ../../../docs/container-images.md:60
msgid "Authentication"
msgstr ""
#: ../../../docs/container-images.md:43
#: ../../../docs/container-images.md:62
msgid "Extend and modify how users are authenticated on your homeserver."
msgstr ""
@@ -301,7 +321,7 @@ msgid "[activism.international/matrix_ldap_registration_proxy](https://gitlab.co
msgstr ""
#: ../../../docs/container-images.md
msgid "A proxy that handles Matrix registration requests and forwards them to LDAP."
msgid "Proxy that handles Matrix registration requests and forwards them to LDAP"
msgstr ""
#: ../../../docs/container-images.md
@@ -313,11 +333,11 @@ msgid "[zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-ma
msgstr ""
#: ../../../docs/container-images.md
msgid "A simple python application to have a token based Matrix registration"
msgid "Simple python application to have a token based Matrix registration"
msgstr ""
#: ../../../docs/container-images.md
msgid "[Matrix User Verification Service](configuring-playbook-user-verification-service.md) (UVS)"
msgid "[Matrix User Verification Service](configuring-playbook-user-verification-service.md)"
msgstr ""
#: ../../../docs/container-images.md
@@ -333,14 +353,14 @@ msgid "[synapse-simple-antispam](configuring-playbook-synapse-simple-antispam.md
msgstr ""
#: ../../../docs/container-images.md
msgid "A spam checker module"
msgid "Spam checker module"
msgstr ""
#: ../../../docs/container-images.md:55
#: ../../../docs/container-images.md:74
msgid "File Storage"
msgstr ""
#: ../../../docs/container-images.md:57
#: ../../../docs/container-images.md:76
msgid "Use alternative file storage to the default `media_store` folder."
msgstr ""
@@ -369,17 +389,29 @@ msgid "[t2bot/matrix-media-repo](https://ghcr.io/t2bot/matrix-media-repo)"
msgstr ""
#: ../../../docs/container-images.md
msgid "matrix-media-repo is a highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
msgid "Highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
msgstr ""
#: ../../../docs/container-images.md:65
#: ../../../docs/container-images.md:84
msgid "Bridges"
msgstr ""
#: ../../../docs/container-images.md:67
#: ../../../docs/container-images.md:86
msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
msgstr ""
#: ../../../docs/container-images.md
msgid "[mautrix-bluesky](configuring-playbook-bridge-mautrix-bluesky.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mautrix/bluesky](https://mau.dev/mautrix/bluesky/container_registry)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge to [Bluesky](https://bsky.social/about)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mautrix-discord](configuring-playbook-bridge-mautrix-discord.md)"
msgstr ""
@@ -548,14 +580,6 @@ msgstr ""
msgid "Bridge to [Discord](https://discordapp.com/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrix-hookshot](configuring-playbook-bridge-hookshot.md)"
msgstr ""
@@ -604,62 +628,6 @@ msgstr ""
msgid "Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[nodefyme/go-skype-bridge](https://hub.docker.com/r/nodefyme/go-skype-bridge)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge to [Skype](https://www.skype.com)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/container_registry)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge to [Slack](https://slack.com)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-puppet-instagram)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/container_registry)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-groupme](configuring-playbook-bridge-mx-puppet-groupme.md)"
msgstr ""
@@ -672,6 +640,18 @@ msgstr ""
msgid "Bridge to [GroupMe](https://groupme.com/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrix-steam-bridge](configuring-playbook-bridge-steam.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[jasonlaguidice/matrix-steam-bridge](https://github.com/jasonlaguidice/matrix-steam-bridge/pkgs/container/matrix-steam-bridge)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge to [Steam](https://steampowered.com/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-steam](configuring-playbook-bridge-mx-puppet-steam.md)"
msgstr ""
@@ -696,11 +676,11 @@ msgstr ""
msgid "Email to Matrix bridge"
msgstr ""
#: ../../../docs/container-images.md:99
#: ../../../docs/container-images.md:114
msgid "Bots"
msgstr ""
#: ../../../docs/container-images.md:101
#: ../../../docs/container-images.md:116
msgid "Bots provide various additional functionality to your installation."
msgstr ""
@@ -713,7 +693,7 @@ msgid "[etke.cc/baibot](https://ghcr.io/etkecc/baibot)"
msgstr ""
#: ../../../docs/container-images.md
msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
msgid "Bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
msgstr ""
#: ../../../docs/container-images.md
@@ -749,7 +729,7 @@ msgid "[dock.mau.dev/maubot/maubot](https://mau.dev/maubot/maubot/container_regi
msgstr ""
#: ../../../docs/container-images.md
msgid "A plugin-based Matrix bot system"
msgid "Plugin-based Matrix bot system"
msgstr ""
#: ../../../docs/container-images.md
@@ -761,7 +741,7 @@ msgid "[etke.cc/honoroit](https://github.com/etkecc/honoroit/container_registry)
msgstr ""
#: ../../../docs/container-images.md
msgid "A helpdesk bot"
msgid "Helpdesk bot"
msgstr ""
#: ../../../docs/container-images.md
@@ -773,7 +753,7 @@ msgid "[matrixdotorg/mjolnir](https://hub.docker.com/r/matrixdotorg/mjolnir)"
msgstr ""
#: ../../../docs/container-images.md
msgid "A moderation tool for Matrix"
msgid "Moderation tool for Matrix"
msgstr ""
#: ../../../docs/container-images.md
@@ -785,7 +765,7 @@ msgid "[gnuxie/draupnir](https://hub.docker.com/r/gnuxie/draupnir)"
msgstr ""
#: ../../../docs/container-images.md
msgid "A moderation tool for Matrix (Fork of Mjolnir)"
msgid "Moderation tool for Matrix (Fork of Mjolnir)"
msgstr ""
#: ../../../docs/container-images.md
@@ -800,11 +780,11 @@ msgstr ""
msgid "Web forms (HTTP POST) to Matrix"
msgstr ""
#: ../../../docs/container-images.md:114
#: ../../../docs/container-images.md:129
msgid "Administration"
msgstr ""
#: ../../../docs/container-images.md:116
#: ../../../docs/container-images.md:131
msgid "Services that help you in administrating and monitoring your Matrix installation."
msgstr ""
@@ -833,15 +813,15 @@ msgid "OAuth 2.0 and OpenID Provider server"
msgstr ""
#: ../../../docs/container-images.md
msgid "[synapse-admin](configuring-playbook-synapse-admin.md)"
msgid "[ketesa](configuring-playbook-ketesa.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[etke.cc/synapse-admin](https://ghcr.io/etkecc/synapse-admin)"
msgid "[etkecc/ketesa](https://ghcr.io/etkecc/ketesa)"
msgstr ""
#: ../../../docs/container-images.md
msgid "A web UI tool for administrating users and rooms on your Matrix server"
msgid "Fully-featured web UI for administrating your Matrix homeserver — users, rooms, media, sessions, and more"
msgstr ""
#: ../../../docs/container-images.md
@@ -873,7 +853,7 @@ msgid "Graphing tool that works well with the above two images. Our playbook als
msgstr ""
#: ../../../docs/container-images.md
msgid "[Metrics and Graphs](configuring-playbook-prometheus-nginxlog.md)"
msgid "[Metrics and Graphs](configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-nginx-logs-optional)"
msgstr ""
#: ../../../docs/container-images.md
@@ -892,6 +872,18 @@ msgstr ""
msgid "Backups"
msgstr ""
#: ../../../docs/container-images.md
msgid "[postgres-backup-local](configuring-playbook-postgres-backup.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[prodrigestivill/postgres-backup-local](https://hub.docker.com/r/prodrigestivill/postgres-backup-local)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Create automatic database backups"
msgstr ""
#: ../../../docs/container-images.md
msgid "[rageshake](configuring-playbook-rageshake.md)"
msgstr ""
@@ -912,44 +904,24 @@ msgstr ""
msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus."
msgstr ""
#: ../../../docs/container-images.md:131
#: ../../../docs/container-images.md:147
msgid "Misc"
msgstr ""
#: ../../../docs/container-images.md:133
#: ../../../docs/container-images.md:149
msgid "Various services that don't fit any other categories."
msgstr ""
#: ../../../docs/container-images.md
msgid "[sliding-sync](configuring-playbook-sliding-sync-proxy.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Sliding Sync support for clients which require it (like old Element X versions, before it got switched to Simplified Sliding Sync)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "A Synapse module to automatically accept invites."
msgstr ""
#: ../../../docs/container-images.md
msgid "[synapse_auto_compressor](configuring-playbook-synapse-auto-compressor.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[etke.cc/rust-synapse-compress-state](https://gitlab.com/etke.cc/rust-synapse-compress-state/container_registry)"
msgid "[mb-saces/rust-synapse-tools](https://gitlab.com/mb-saces/rust-synapse-tools/container_registry)"
msgstr ""
#: ../../../docs/container-images.md
msgid "A cli tool that automatically compresses `state_groups` database table in background."
msgid "Cli tool that automatically compresses Synapse's `state_groups` database table in background"
msgstr ""
#: ../../../docs/container-images.md
@@ -973,7 +945,7 @@ msgid "[etherpad/etherpad](https://hub.docker.com/r/etherpad/etherpad/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "An open source collaborative text editor"
msgid "Open source collaborative text editor"
msgstr ""
#: ../../../docs/container-images.md
@@ -985,7 +957,7 @@ msgid "[jitsi/web](https://hub.docker.com/r/jitsi/web)"
msgstr ""
#: ../../../docs/container-images.md
msgid "the [Jitsi](https://jitsi.org/) web UI"
msgid "[Jitsi](https://jitsi.org/) web UI"
msgstr ""
#: ../../../docs/container-images.md
@@ -993,7 +965,7 @@ msgid "[jitsi/jicofo](https://hub.docker.com/r/jitsi/jicofo)"
msgstr ""
#: ../../../docs/container-images.md
msgid "the [Jitsi](https://jitsi.org/) Focus component"
msgid "[Jitsi](https://jitsi.org/) Focus component"
msgstr ""
#: ../../../docs/container-images.md
@@ -1001,7 +973,7 @@ msgid "[jitsi/prosody](https://hub.docker.com/r/jitsi/prosody)"
msgstr ""
#: ../../../docs/container-images.md
msgid "the [Jitsi](https://jitsi.org/) Prosody XMPP server component"
msgid "[Jitsi](https://jitsi.org/) Prosody XMPP server component"
msgstr ""
#: ../../../docs/container-images.md
@@ -1009,7 +981,7 @@ msgid "[jitsi/jvb](https://hub.docker.com/r/jitsi/jvb)"
msgstr ""
#: ../../../docs/container-images.md
msgid "the [Jitsi](https://jitsi.org/) Video Bridge component"
msgid "[Jitsi](https://jitsi.org/) Video Bridge component"
msgstr ""
#: ../../../docs/container-images.md
@@ -1021,7 +993,7 @@ msgid "[cactuscomments/cactus-appservice](https://hub.docker.com/r/cactuscomment
msgstr ""
#: ../../../docs/container-images.md
msgid "A federated comment system built on Matrix"
msgid "Federated comment system built on Matrix"
msgstr ""
#: ../../../docs/container-images.md
@@ -1037,7 +1009,7 @@ msgid "[matrixdotorg/pantalaimon](https://hub.docker.com/r/matrixdotorg/pantalai
msgstr ""
#: ../../../docs/container-images.md
msgid "An E2EE aware proxy daemon"
msgid "E2EE aware proxy daemon"
msgstr ""
#: ../../../docs/container-images.md
@@ -1064,24 +1036,36 @@ msgstr ""
msgid "Self-hosted, UnifiedPush-compatible push notifications server"
msgstr ""
#: ../../../docs/container-images.md:152
#: ../../../docs/container-images.md
msgid "[Element Call](configuring-playbook-element-call.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[element-hq/element-call](https://ghcr.io/element-hq/element-call)"
msgstr ""
#: ../../../docs/container-images.md
msgid "A native Matrix video conferencing application"
msgstr ""
#: ../../../docs/container-images.md:167
msgid "Container images of deprecated / unmaintained services"
msgstr ""
#: ../../../docs/container-images.md:154
#: ../../../docs/container-images.md:169
msgid "The list of the deprecated or unmaintained services is available [here](configuring-playbook.md#deprecated--unmaintained--removed-services)."
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md)"
msgid "[conduwuit](configuring-playbook-conduwuit.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks)"
msgid "[girlbossceo/conduwuit](https://ghcr.io/girlbossceo/conduwuit)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.)"
msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit was a fork of Conduit."
msgstr ""
#: ../../../docs/container-images.md
@@ -1093,7 +1077,7 @@ msgid "[turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-di
msgstr ""
#: ../../../docs/container-images.md
msgid "An open source integration manager for Matrix clients"
msgid "Open source integration manager for Matrix clients"
msgstr ""
#: ../../../docs/container-images.md
@@ -1117,7 +1101,39 @@ msgid "[matrixdotorg/go-neb](https://hub.docker.com/r/matrixdotorg/go-neb)"
msgstr ""
#: ../../../docs/container-images.md
msgid "A multi functional bot written in Go"
msgid "Multi functional bot written in Go"
msgstr ""
#: ../../../docs/container-images.md
msgid "[ma1sd](configuring-playbook-ma1sd.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Matrix Identity Server"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.)"
msgstr ""
#: ../../../docs/container-images.md
@@ -1144,18 +1160,6 @@ msgstr ""
msgid "Bridge to [Facebook](https://facebook.com/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mautrix-hangouts](configuring-playbook-bridge-mautrix-hangouts.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mautrix/hangouts](https://mau.dev/mautrix/hangouts/container_registry)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge to [Google Hangouts](https://en.wikipedia.org/wiki/Google_Hangouts)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mautrix-instagram](configuring-playbook-bridge-mautrix-instagram.md)"
msgstr ""
@@ -1167,3 +1171,67 @@ msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge to [Instagram](https://instagram.com/)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/container_registry)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-puppet-instagram)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/container_registry)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge to [Slack](https://slack.com)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
msgstr ""
#: ../../../docs/container-images.md
msgid "[sliding-sync](configuring-playbook-sliding-sync-proxy.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Sliding Sync support for clients which require it (like old Element X versions, before it got switched to Simplified Sliding Sync)"
msgstr ""
#: ../../../docs/container-images.md
msgid "[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md)"
msgstr ""
#: ../../../docs/container-images.md
msgid "Synapse module to automatically accept invites"
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 09:54+0200\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,228 +18,225 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/registering-users.md:1
#: ../../../docs/registering-users.md:11
msgid "Registering users"
msgstr ""
#: ../../../docs/registering-users.md:3
#: ../../../docs/registering-users.md:13
msgid "This documentation page tells you how to create user accounts on your Matrix server."
msgstr ""
#: ../../../docs/registering-users.md:5
#: ../../../docs/registering-users.md:15
msgid "Table of contents:"
msgstr ""
#: ../../../docs/registering-users.md:7
#: ../../../docs/registering-users.md:16
msgid "[Registering users](#registering-users)"
msgstr ""
#: ../../../docs/registering-users.md:8
#: ../../../docs/registering-users.md:17
msgid "[Registering users manually](#registering-users-manually)"
msgstr ""
#: ../../../docs/registering-users.md:9
#: ../../../docs/registering-users.md:18
msgid "[Managing users via a Web UI](#managing-users-via-a-web-ui)"
msgstr ""
#: ../../../docs/registering-users.md:10
#: ../../../docs/registering-users.md:19
msgid "[Letting certain users register on your private server](#letting-certain-users-register-on-your-private-server)"
msgstr ""
#: ../../../docs/registering-users.md:11
#: ../../../docs/registering-users.md:20
msgid "[Enabling public user registration](#enabling-public-user-registration)"
msgstr ""
#: ../../../docs/registering-users.md:12
#: ../../../docs/registering-users.md:21
msgid "[Adding/Removing Administrator privileges to an existing user](#addingremoving-administrator-privileges-to-an-existing-user)"
msgstr ""
#: ../../../docs/registering-users.md:14
#: ../../../docs/registering-users.md:23
msgid "Registering users manually"
msgstr ""
#: ../../../docs/registering-users.md:16 ../../../docs/registering-users.md:121
#: ../../../docs/registering-users.md:25 ../../../docs/registering-users.md:127
msgid "**Notes**:"
msgstr ""
#: ../../../docs/registering-users.md:17
#: ../../../docs/registering-users.md:26
msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`"
msgstr ""
#: ../../../docs/registering-users.md:18
#: ../../../docs/registering-users.md:27
msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)"
msgstr ""
#: ../../../docs/registering-users.md:19
#: ../../../docs/registering-users.md:28
msgid "Use `admin=yes` or `admin=no` depending on whether you wish to make the user an administrator of the Matrix server"
msgstr ""
#: ../../../docs/registering-users.md:21
#: ../../../docs/registering-users.md:30
msgid "After registering a user (using one of the methods below), **you can log in with that user** via the [Element Web](configuring-playbook-client-element-web.md) service that this playbook has installed for you at a URL like this: `https://element.example.com/`."
msgstr ""
#: ../../../docs/registering-users.md:23
#: ../../../docs/registering-users.md:32
msgid "Registering users via the Ansible playbook"
msgstr ""
#: ../../../docs/registering-users.md:25
#: ../../../docs/registering-users.md:34
msgid "It's best to register users via the Ansible playbook, because it works regardless of homeserver implementation (Synapse, Dendrite, etc) or usage of [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (MAS)."
msgstr ""
#: ../../../docs/registering-users.md:27
#: ../../../docs/registering-users.md:36
msgid "To register a user via this Ansible playbook:"
msgstr ""
#: ../../../docs/registering-users.md:35
#: ../../../docs/registering-users.md:44
msgid "**or** by invoking `ansible-playbook` manually:"
msgstr ""
#: ../../../docs/registering-users.md:43
#: ../../../docs/registering-users.md:52
msgid "Feel free to register as many users (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your user account only (with `admin=yes`), and others should be created with `admin=no`."
msgstr ""
#: ../../../docs/registering-users.md:45
#: ../../../docs/registering-users.md:54
msgid "[!WARNING] If you're registering users against Matrix Authentication Service, do note that it [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information."
msgstr ""
#: ../../../docs/registering-users.md:48
#: ../../../docs/registering-users.md:57
msgid "Registering users manually for Synapse"
msgstr ""
#: ../../../docs/registering-users.md:50
#: ../../../docs/registering-users.md:59
msgid "If you're using the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default), you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
msgstr ""
#: ../../../docs/registering-users.md:58
#: ../../../docs/registering-users.md:67
msgid "Registering users manually for Dendrite"
msgstr ""
#: ../../../docs/registering-users.md:60
#: ../../../docs/registering-users.md:69
msgid "If you're using the [Dendrite](./configuring-playbook-dendrite.md) homeserver implementation, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
msgstr ""
#: ../../../docs/registering-users.md:68
#: ../../../docs/registering-users.md:77
msgid "Registering users manually for Matrix Authentication Service"
msgstr ""
#: ../../../docs/registering-users.md:70
#: ../../../docs/registering-users.md:79
msgid "If you're using the [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) and your existing homeserver (most likely [Synapse](./configuring-playbook-synapse.md)) is delegating authentication to it, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
msgstr ""
#: ../../../docs/registering-users.md:78
#: ../../../docs/registering-users.md:87
msgid "This `register-user` script actually invokes the `mas-cli manage register-user` command under the hood. If you'd like more control over the registration process, consider invoking the `mas-cli` command directly:"
msgstr ""
#: ../../../docs/registering-users.md:84
#: ../../../docs/registering-users.md:93
msgid "[!WARNING] Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information."
msgstr ""
#: ../../../docs/registering-users.md:87
#: ../../../docs/registering-users.md:96
msgid "Managing users via a Web UI"
msgstr ""
#: ../../../docs/registering-users.md:89
msgid "To manage users more easily (via a web user-interace), you can install [Synapse Admin](configuring-playbook-synapse-admin.md)."
msgstr ""
#: ../../../docs/registering-users.md:91
msgid "[!WARNING] If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information."
msgstr ""
#: ../../../docs/registering-users.md:94
msgid "Letting certain users register on your private server"
msgstr ""
#: ../../../docs/registering-users.md:96
msgid "If you'd rather **keep your server private** (public registration closed, as is the default), and **let certain people create accounts by themselves** (instead of creating user accounts manually like this), consider installing and making use of [matrix-registration](configuring-playbook-matrix-registration.md)."
msgstr ""
#: ../../../docs/registering-users.md:98
msgid "Enabling public user registration"
msgid "To manage users and your homeserver more easily (via a web interface), you can install [Ketesa](configuring-playbook-ketesa.md) — a fully-featured admin UI covering users, rooms, media, sessions, and MAS management."
msgstr ""
#: ../../../docs/registering-users.md:100
msgid "To **open up user registration publicly** (usually **not recommended**), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgid "Letting certain users register on your private server"
msgstr ""
#: ../../../docs/registering-users.md:102
msgid "For Synapse:"
msgid "If you'd rather **keep your server private** (public registration closed, as is the default), and **let certain people create accounts by themselves** (instead of creating user accounts manually like this), consider installing and making use of [matrix-registration](configuring-playbook-matrix-registration.md)."
msgstr ""
#: ../../../docs/registering-users.md:104
msgid "Enabling public user registration"
msgstr ""
#: ../../../docs/registering-users.md:106
msgid "To **open up user registration publicly** (usually **not recommended**), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/registering-users.md:108
msgid "For Dendrite:"
msgid "For Synapse:"
msgstr ""
#: ../../../docs/registering-users.md:114
msgid "For Dendrite:"
msgstr ""
#: ../../../docs/registering-users.md:120
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/registering-users.md:123
#: ../../../docs/registering-users.md:129
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/registering-users.md:125
#: ../../../docs/registering-users.md:131
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgstr ""
#: ../../../docs/registering-users.md:127
#: ../../../docs/registering-users.md:133
msgid "If you're opening up registrations publicly like this, you might also wish to [configure CAPTCHA protection](configuring-captcha.md)."
msgstr ""
#: ../../../docs/registering-users.md:129
#: ../../../docs/registering-users.md:135
msgid "Adding/Removing Administrator privileges to an existing user"
msgstr ""
#: ../../../docs/registering-users.md:131
#: ../../../docs/registering-users.md:137
msgid "Adding/Removing Administrator privileges to an existing user in Synapse"
msgstr ""
#: ../../../docs/registering-users.md:133
#: ../../../docs/registering-users.md:139
msgid "To change the admin privileges for a user in Synapse's local database, you need to run an SQL query like this against the `synapse` database:"
msgstr ""
#: ../../../docs/registering-users.md:139
#: ../../../docs/registering-users.md:145
msgid "where:"
msgstr ""
#: ../../../docs/registering-users.md:141
#: ../../../docs/registering-users.md:147
msgid "`ADMIN_VALUE` being either `0` (regular user) or `1` (admin)"
msgstr ""
#: ../../../docs/registering-users.md:142
#: ../../../docs/registering-users.md:148
msgid "`USER` and `example.com` pointing to a valid user on your server"
msgstr ""
#: ../../../docs/registering-users.md:144
#: ../../../docs/registering-users.md:150
msgid "If you're using the integrated Postgres server and not an [external Postgres server](configuring-playbook-external-postgres.md), you can launch a Postgres into the `synapse` database by:"
msgstr ""
#: ../../../docs/registering-users.md:146
#: ../../../docs/registering-users.md:152
msgid "running `/matrix/postgres/bin/cli` — to launch [`psql`](https://www.postgresql.org/docs/current/app-psql.html)"
msgstr ""
#: ../../../docs/registering-users.md:147
#: ../../../docs/registering-users.md:153
msgid "running `\\c synapse` — to change to the `synapse` database"
msgstr ""
#: ../../../docs/registering-users.md:149
#: ../../../docs/registering-users.md:155
msgid "You can then proceed to run the query above."
msgstr ""
#: ../../../docs/registering-users.md:151
#: ../../../docs/registering-users.md:157
msgid "**Note**: directly modifying the raw data of Synapse (or any other software) could cause the software to break. You've been warned!"
msgstr ""
#: ../../../docs/registering-users.md:153
#: ../../../docs/registering-users.md:159
msgid "Adding/Removing Administrator privileges to an existing user in Matrix Authentication Service"
msgstr ""
#: ../../../docs/registering-users.md:155
msgid "Promoting/demoting a user in Matrix Authentication Service cannot currently (2024-10-19) be done via the [`mas-cli` Management tool](./configuring-playbook-matrix-authentication-service.md#management)."
#: ../../../docs/registering-users.md:161
msgid "Promoting/demoting a user in Matrix Authentication Service can be done using the [`mas-cli`](./configuring-playbook-matrix-authentication-service.md#management) management tool's [`manage promote-admin`](https://element-hq.github.io/matrix-authentication-service/reference/cli/manage.html#manage-promote-admin) and [`manage demote-admin`](https://element-hq.github.io/matrix-authentication-service/reference/cli/manage.html#manage-demote-admin) commands. For example: `/matrix/matrix-authentication-service/bin/mas-cli manage promote-admin some.username`."
msgstr ""
#: ../../../docs/registering-users.md:157
msgid "You can do it via the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html)'s `POST /api/admin/v1/users/{id}/set-admin` endpoint."
#: ../../../docs/registering-users.md:163
#, python-brace-format
msgid "You can also do it via the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html)'s `POST /api/admin/v1/users/{id}/set-admin` endpoint."
msgstr ""
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-12-16 12:05+0900\n"
"POT-Creation-Date: 2026-04-03 12:09+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
@@ -18,160 +18,136 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
"Generated-By: Babel 2.18.0\n"
#: ../../../docs/self-building.md:1
#: ../../../docs/self-building.md:15
msgid "Self-building"
msgstr ""
#: ../../../docs/self-building.md:3
#: ../../../docs/self-building.md:17
msgid "**Caution: self-building does not have to be used on its own. See the [Alternative Architectures](alternative-architectures.md) page.**"
msgstr ""
#: ../../../docs/self-building.md:5
#: ../../../docs/self-building.md:19
msgid "The playbook supports self-building of various components, which don't have a container image for your architecture (see the [container images we use](container-images.md)). For `amd64`, self-building is not required."
msgstr ""
#: ../../../docs/self-building.md:7
#: ../../../docs/self-building.md:21
msgid "For other architectures (e.g. `arm32`, `arm64`), ready-made container images are used when available. If there's no ready-made image for a specific component and said component supports self-building, an image will be built on the host. Building images like this takes more time and resources (some build tools need to get installed by the playbook to assist building)."
msgstr ""
#: ../../../docs/self-building.md:9
#: ../../../docs/self-building.md:23
msgid "To make use of self-building, you don't need to do anything. If a component has an image for the specified architecture, the playbook will use it directly. If not, it will build the image on the server itself."
msgstr ""
#: ../../../docs/self-building.md:11
#: ../../../docs/self-building.md:25
msgid "Note that **not all components support self-building yet**."
msgstr ""
#: ../../../docs/self-building.md:13
#: ../../../docs/self-building.md:27
msgid "Possibly outdated list of roles where self-building the Docker image is currently possible:"
msgstr ""
#: ../../../docs/self-building.md:14
#: ../../../docs/self-building.md:28
msgid "`matrix-synapse`"
msgstr ""
#: ../../../docs/self-building.md:15
msgid "`matrix-synapse-admin`"
msgstr ""
#: ../../../docs/self-building.md:16
msgid "`matrix-client-element`"
msgstr ""
#: ../../../docs/self-building.md:17
msgid "`matrix-client-hydrogen`"
msgstr ""
#: ../../../docs/self-building.md:18
msgid "`matrix-client-cinny`"
msgstr ""
#: ../../../docs/self-building.md:19
msgid "`matrix-registration`"
msgstr ""
#: ../../../docs/self-building.md:20
msgid "`matrix-coturn`"
msgstr ""
#: ../../../docs/self-building.md:21
msgid "`matrix-corporal`"
msgstr ""
#: ../../../docs/self-building.md:22
msgid "`matrix-dimension`"
msgstr ""
#: ../../../docs/self-building.md:23
msgid "`matrix-ma1sd`"
msgstr ""
#: ../../../docs/self-building.md:24
msgid "`exim-relay`"
msgstr ""
#: ../../../docs/self-building.md:25
msgid "`matrix-bridge-hookshot`"
msgstr ""
#: ../../../docs/self-building.md:26
msgid "`matrix-bridge-appservice-irc`"
msgstr ""
#: ../../../docs/self-building.md:27
msgid "`matrix-bridge-appservice-slack`"
msgstr ""
#: ../../../docs/self-building.md:28
msgid "`matrix-bridge-appservice-webhooks`"
msgstr ""
#: ../../../docs/self-building.md:29
msgid "`matrix-bridge-beeper-linkedin`"
msgid "`matrix-ketesa`"
msgstr ""
#: ../../../docs/self-building.md:30
msgid "`matrix-bridge-mautrix-facebook`"
msgid "`matrix-client-element`"
msgstr ""
#: ../../../docs/self-building.md:31
msgid "`matrix-bridge-mautrix-hangouts`"
msgid "`hydrogen`"
msgstr ""
#: ../../../docs/self-building.md:32
msgid "`matrix-bridge-mautrix-googlechat`"
msgid "`cinny`"
msgstr ""
#: ../../../docs/self-building.md:33
msgid "`matrix-bridge-mautrix-telegram`"
msgid "`sable`"
msgstr ""
#: ../../../docs/self-building.md:34
msgid "`matrix-bridge-mautrix-signal`"
msgid "`matrix-registration`"
msgstr ""
#: ../../../docs/self-building.md:35
msgid "`matrix-bridge-mautrix-gmessages`"
msgid "`coturn`"
msgstr ""
#: ../../../docs/self-building.md:36
msgid "`matrix-bridge-mautrix-whatsapp`"
msgid "`matrix-corporal`"
msgstr ""
#: ../../../docs/self-building.md:37
msgid "`matrix-bridge-mx-puppet-steam`"
msgid "`exim-relay`"
msgstr ""
#: ../../../docs/self-building.md:38
msgid "`matrix-bot-mjolnir`"
msgid "`matrix-bridge-hookshot`"
msgstr ""
#: ../../../docs/self-building.md:39
msgid "`matrix-bot-honoroit`"
msgid "`matrix-bridge-appservice-irc`"
msgstr ""
#: ../../../docs/self-building.md:40
msgid "`matrix-bot-matrix-reminder-bot`"
msgid "`matrix-bridge-beeper-linkedin`"
msgstr ""
#: ../../../docs/self-building.md:41
msgid "`matrix-bot-maubot`"
msgid "`matrix-bridge-mautrix-googlechat`"
msgstr ""
#: ../../../docs/self-building.md:42
msgid "`matrix-email2matrix`"
msgid "`matrix-bridge-mautrix-telegram`"
msgstr ""
#: ../../../docs/self-building.md:43
msgid "`matrix-pantalaimon`"
msgid "`matrix-bridge-mautrix-signal`"
msgstr ""
#: ../../../docs/self-building.md:44
msgid "`matrix-bridge-mautrix-gmessages`"
msgstr ""
#: ../../../docs/self-building.md:45
msgid "Adding self-building support to other roles is welcome. Feel free to contribute!"
msgid "`matrix-bridge-mautrix-whatsapp`"
msgstr ""
#: ../../../docs/self-building.md:46
msgid "`matrix-bridge-mx-puppet-steam`"
msgstr ""
#: ../../../docs/self-building.md:47
msgid "`matrix-bot-mjolnir`"
msgstr ""
#: ../../../docs/self-building.md:48
msgid "`matrix-bot-honoroit`"
msgstr ""
#: ../../../docs/self-building.md:49
msgid "`matrix-bot-matrix-reminder-bot`"
msgstr ""
#: ../../../docs/self-building.md:50
msgid "`matrix-bot-maubot`"
msgstr ""
#: ../../../docs/self-building.md:51
msgid "`matrix-pantalaimon`"
msgstr ""
#: ../../../docs/self-building.md:53
msgid "Adding self-building support to other roles is welcome. Feel free to contribute!"
msgstr ""
#: ../../../docs/self-building.md:55
msgid "If you'd like **to force self-building** even if an image is available for your architecture, look into the `matrix_*_self_build` variables provided by individual roles."
msgstr ""
+8 -8
View File
@@ -1,22 +1,22 @@
alabaster==1.0.0
babel==2.18.0
certifi==2026.2.25
charset-normalizer==3.4.6
click==8.3.1
certifi==2026.4.22
charset-normalizer==3.4.7
click==8.3.3
docutils==0.22.4
idna==3.11
idna==3.13
imagesize==2.0.0
Jinja2==3.1.6
linkify-it-py==2.1.0
markdown-it-py==4.0.0
markdown-it-py==4.1.0
MarkupSafe==3.0.3
mdit-py-plugins==0.5.0
mdurl==0.1.2
myst-parser==5.0.0
packaging==26.0
Pygments==2.19.2
packaging==26.2
Pygments==2.20.0
PyYAML==6.0.3
requests==2.32.5
requests==2.33.1
setuptools==82.0.1
snowballstemmer==3.0.1
Sphinx==9.1.0
File diff suppressed because it is too large Load Diff
+67 -67
View File
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
"POT-Creation-Date: 2026-05-07 11:16+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -188,6 +188,18 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-continuwuity.md)"
msgstr ""
#: ../../../README.md:0
msgid "[Tuwunel](https://matrix-construct.github.io/tuwunel/)"
msgstr ""
#: ../../../README.md:0
msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Tuwunel is the official successor to conduwuit."
msgstr ""
#: ../../../README.md:0
msgid "[Link](docs/configuring-playbook-tuwunel.md)"
msgstr ""
#: ../../../README.md:0
msgid "[Dendrite](https://github.com/element-hq/dendrite)"
msgstr ""
@@ -200,11 +212,11 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-dendrite.md)"
msgstr ""
#: ../../../README.md:58
#: ../../../README.md:59
msgid "Clients"
msgstr ""
#: ../../../README.md:60
#: ../../../README.md:61
msgid "Web clients for Matrix that you can host on your own domains."
msgstr ""
@@ -244,6 +256,14 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-client-cinny.md)"
msgstr ""
#: ../../../README.md:0
msgid "[Sable](https://github.com/7w1/sable)"
msgstr ""
#: ../../../README.md:0
msgid "[Link](docs/configuring-playbook-client-sable.md)"
msgstr ""
#: ../../../README.md:0
msgid "[SchildiChat Web](https://schildi.chat/)"
msgstr ""
@@ -268,11 +288,11 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-client-fluffychat-web.md)"
msgstr ""
#: ../../../README.md:70
#: ../../../README.md:72
msgid "Server Components"
msgstr ""
#: ../../../README.md:72
#: ../../../README.md:74
msgid "Services that run on the server to make the various parts of your installation work."
msgstr ""
@@ -288,18 +308,6 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-external-postgres.md)"
msgstr ""
#: ../../../README.md:0
msgid "[coturn](https://github.com/coturn/coturn)"
msgstr ""
#: ../../../README.md:0
msgid "STUN/TURN server for WebRTC audio/video calls"
msgstr ""
#: ../../../README.md:0
msgid "[Link](docs/configuring-playbook-turn.md)"
msgstr ""
#: ../../../README.md:0
msgid "[Traefik](https://doc.traefik.io/traefik/)"
msgstr ""
@@ -336,6 +344,18 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-email.md)"
msgstr ""
#: ../../../README.md:0
msgid "[coturn](https://github.com/coturn/coturn)"
msgstr ""
#: ../../../README.md:0
msgid "STUN/TURN server for WebRTC audio/video calls"
msgstr ""
#: ../../../README.md:0
msgid "[Link](docs/configuring-playbook-turn.md)"
msgstr ""
#: ../../../README.md:0
msgid "[ddclient](https://github.com/linuxserver/docker-ddclient)"
msgstr ""
@@ -349,34 +369,22 @@ msgid "[Link](docs/configuring-playbook-dynamic-dns.md)"
msgstr ""
#: ../../../README.md:0
msgid "[LiveKit Server](https://github.com/livekit/livekit)"
msgid "Matrix RTC stack"
msgstr ""
#: ../../../README.md:0
msgid "WebRTC server for audio/video calls"
msgid "Supporting components ([LiveKit Server](docs/configuring-playbook-livekit-server.md) and [LiveKit JWT Service](docs/configuring-playbook-livekit-jwt-service.md)) for in-app audio/video calls for Matrix clients"
msgstr ""
#: ../../../README.md:0
msgid "[Link](docs/configuring-playbook-livekit-server.md)"
msgid "[Link](docs/configuring-playbook-matrix-rtc.md)"
msgstr ""
#: ../../../README.md:0
msgid "[Livekit JWT Service](https://github.com/livekit/livekit-jwt-service)"
msgstr ""
#: ../../../README.md:0
msgid "JWT service for integrating [Element Call](./configuring-playbook-element-call.md) with [LiveKit Server](./configuring-playbook-livekit-server.md)"
msgstr ""
#: ../../../README.md:0
msgid "[Link](docs/configuring-playbook-livekit-jwt-service.md)"
msgstr ""
#: ../../../README.md:85
#: ../../../README.md:86
msgid "Authentication"
msgstr ""
#: ../../../README.md:87
#: ../../../README.md:88
msgid "Extend and modify how users are authenticated on your homeserver."
msgstr ""
@@ -464,11 +472,11 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-synapse-simple-antispam.md)"
msgstr ""
#: ../../../README.md:99
#: ../../../README.md:100
msgid "File Storage"
msgstr ""
#: ../../../README.md:101
#: ../../../README.md:102
msgid "Use alternative file storage to the default `media_store` folder."
msgstr ""
@@ -504,11 +512,11 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-matrix-media-repo.md)"
msgstr ""
#: ../../../README.md:109
#: ../../../README.md:110
msgid "Bridges"
msgstr ""
#: ../../../README.md:111
#: ../../../README.md:112
msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
msgstr ""
@@ -692,14 +700,6 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-bridge-appservice-discord.md)"
msgstr ""
#: ../../../README.md:0
msgid "[matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack)"
msgstr ""
#: ../../../README.md:0
msgid "[Link](docs/configuring-playbook-bridge-appservice-slack.md)"
msgstr ""
#: ../../../README.md:0
msgid "[matrix-hookshot](https://github.com/matrix-org/matrix-hookshot)"
msgstr ""
@@ -760,6 +760,18 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-bridge-heisenbridge.md)"
msgstr ""
#: ../../../README.md:0
msgid "[meshtastic-matrix-relay](https://github.com/jeremiah-k/meshtastic-matrix-relay)"
msgstr ""
#: ../../../README.md:0
msgid "Bridge to [Meshtastic](https://meshtastic.org/) mesh networks"
msgstr ""
#: ../../../README.md:0
msgid "[Link](docs/configuring-playbook-bridge-meshtastic-relay.md)"
msgstr ""
#: ../../../README.md:0
msgid "[mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme)"
msgstr ""
@@ -796,11 +808,11 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-bridge-postmoogle.md)"
msgstr ""
#: ../../../README.md:140
#: ../../../README.md:141
msgid "Bots"
msgstr ""
#: ../../../README.md:142
#: ../../../README.md:143
msgid "Bots provide various additional functionality to your installation."
msgstr ""
@@ -900,11 +912,11 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-bot-buscarron.md)"
msgstr ""
#: ../../../README.md:155
#: ../../../README.md:156
msgid "Administration"
msgstr ""
#: ../../../README.md:157
#: ../../../README.md:158
msgid "Services that help you in administrating and monitoring your Matrix installation."
msgstr ""
@@ -933,15 +945,15 @@ msgid "[Link](docs/configuring-playbook-matrix-authentication-service.md)"
msgstr ""
#: ../../../README.md:0
msgid "[synapse-admin](https://github.com/etkecc/synapse-admin)"
msgid "[Ketesa](https://github.com/etkecc/ketesa)"
msgstr ""
#: ../../../README.md:0
msgid "Web UI tool for administrating users and rooms on your Matrix server"
msgid "Fully-featured web UI for administrating your Matrix homeserver — users, rooms, media, sessions, and more"
msgstr ""
#: ../../../README.md:0
msgid "[Link](docs/configuring-playbook-synapse-admin.md)"
msgid "[Link](docs/configuring-playbook-ketesa.md)"
msgstr ""
#: ../../../README.md:0
@@ -992,26 +1004,14 @@ msgstr ""
msgid "[Link](docs/configuring-playbook-synapse-usage-exporter.md)"
msgstr ""
#: ../../../README.md:169
#: ../../../README.md:170
msgid "Misc"
msgstr ""
#: ../../../README.md:171
#: ../../../README.md:172
msgid "Various services that don't fit any other categories."
msgstr ""
#: ../../../README.md:0
msgid "[synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-accept-invite)"
msgstr ""
#: ../../../README.md:0
msgid "Synapse module to automatically accept invites"
msgstr ""
#: ../../../README.md:0
msgid "[Link](docs/configuring-playbook-synapse-auto-accept-invite.md)"
msgstr ""
#: ../../../README.md:0
msgid "[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor)"
msgstr ""
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
"POT-Creation-Date: 2026-05-07 14:00+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -16,167 +16,215 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:8
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:9
msgid "Setting up Draupnir for All/D4A (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:10
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:11
msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool for you in appservice mode."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:12
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:13
msgid "Appservice mode can be used together with the regular [Draupnir bot](configuring-playbook-bot-draupnir.md) or independently. Details about the differences between the 2 modes are described below."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:14
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:15
msgid "Draupnir Appservice mode compared to Draupnir bot mode"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:16
msgid "The administrative functions for managing the appservice are alpha quality and very limited. However, the experience of using an appservice-provisioned Draupnir is on par with the experience of using Draupnir from bot mode except in the case of avatar customisation as described later on in this document."
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:17
msgid "The administrative functions for managing the appservice are alpha quality and very limited. However, the experience of using an appservice-provisioned Draupnir is on par with the experience of using Draupnir from bot mode."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:18
msgid "Draupnir for all is the way to go if you need more than 1 Draupnir instance, but you don't need access to Synapse Admin features as they are not accessible through Draupnir for All (Even though the commands do show up in help)."
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:19
msgid "Draupnir for all is the way to go if you need more than 1 Draupnir instance, but you don't need access to Synapse Admin features as they are not accessible through Draupnir for All."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:20
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:21
msgid "Draupnir for all in the playbook is rate-limit-exempt automatically as its appservice configuration file does not specify any rate limits."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:22
msgid "Normal Draupnir does come with the benefit of access to Synapse Admin features. You are also able to more easily customise your normal Draupnir than D4A as D4A even on the branch with the Avatar command (To be Upstreamed to Mainline Draupnir) that command is clunky as it requires the use of things like Element Web devtools. In normal Draupnir this is a quick operation where you login to Draupnir with a normal client and set Avatar and Display name normally."
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:23
msgid "Normal Draupnir does come with the benefit of access to Synapse Admin features. You are also able to more easily customise your normal Draupnir than D4A as the avatar command is clunky as it requires the use of things like Element Web devtools. In normal Draupnir this can be done while logged in to the Draupnir account with a normal client and set Avatar and Display name normally."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:24
msgid "Draupnir for all does not support external tooling like [MRU](https://mru.rory.gay) as it can't access Draupnir's user account."
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:25
msgid "Draupnir for all only has limited support for external tooling like [MRU](https://mru.rory.gay) as it can't access Draupnir's user account."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:26
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:27
msgid "Prerequisites"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:28
msgid "Create a main management room"
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:29
msgid "Prerequisites for Zero Touch Deployment (recommended)"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:30
msgid "The playbook does not create a management room for your Main Draupnir. You **need to create the room manually** before setting up the bot."
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:31
msgid "As of Draupnir 3.1.0, Zero Touch Deployment of Draupnir Appservice Mode (Draupnir for all) requires you to supply the following:"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:32
msgid "Note that the room must be unencrypted."
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:33
msgid "MXID of the first person who gets invited to the admin room that the bot creates for you."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:34
msgid "The management room has to be given an alias, and your bot has to be invited to the room."
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:35
msgid "That is all. The appservice manages everything on its own after you provide it with an MXID to invite."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:36
msgid "This management room is used to control who has access to your D4A deployment. The room stores this data inside of the control room state so your bot must have sufficient powerlevel to send custom state events. This is default 50 or moderator as Element clients call this powerlevel."
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:37
msgid "If proceeding with Zero Touch Deployment, skip ahead to [Adjusting the playbook configuration](#adjusting-the-playbook-configuration)."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:38
msgid "[!WARNING] Anyone in this room can control the bot so it is important that you only invite trusted users to this room."
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:39
msgid "Create an admin room (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:41
msgid "Adjusting the playbook configuration"
msgid "The playbook does not create an admin room for your Draupnir, but the appservice itself can do this for you. Alternatively, you **can create the room manually** before setting up the bot."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:43
msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ALIAS_HERE`."
msgid "Note that the room must be unencrypted."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:51
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:45
msgid "The admin room has to be given an alias, and your bot has to be invited to the room."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:47
msgid "This admin room is used to control who has access to your D4A deployment. The room stores this data in the control room state, so your bot must have sufficient power level to send custom state events. This is `50` by default (moderator, as Element clients call this power level)."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:49
msgid "[!WARNING] Anyone in this room can control the bot so it is important that you only invite trusted users to this room."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:52
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:54
msgid "When using Zero Touch Deployment, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `INITIAL_MANAGER_MXID_HERE` with the MXID of the user who should be invited to the admin room first."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:64
msgid "If opting out of Zero Touch Deployment, use the following configuration block instead. Make sure to replace `MANAGEMENT_ROOM_ALIAS_HERE` with the alias of the admin room you have created earlier."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:72
msgid "Running both bot mode and appservice mode"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:74
msgid "When running both [bot mode](./configuring-playbook-bot-draupnir.md) and appservice mode, 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-appservice-draupnir-for-all.md:78
msgid "Conditional restarts work correctly for all tags when running only one of these two operating modes."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:80
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:53
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:82
msgid "There are some additional things you may wish to configure about the component."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:55
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:84
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:57
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:86
msgid "`roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_appservice_draupnir_for_all_configuration_extension_yaml` variable"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:59
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:88
msgid "For example, to change Draupnir's `protectAllJoinedRooms` option to `true`, add the following configuration to your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:73
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:102
msgid "You can refer to the upstream [documentation](https://github.com/the-draupnir-project/Draupnir) for more configuration documentation."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:75
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:90
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:104
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:119
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:77
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:106
msgid "The playbook ships a full copy of the example config that does transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in the template directory of the role."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:79
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:108
msgid "Config extension does not affect the appservices config as this config is not extensible in current Draupnir anyway. It instead touches the config passed to the Draupnirs that your Appservice creates. So the example above (`protectAllJoinedRooms: true`) makes all provisioned Draupnirs protect all joined rooms."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:81
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:110
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:83
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:112
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:92
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:121
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:94
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:123
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:96
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:125
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:98
msgid "If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com` you have successfully installed Draupnir for All and can now start using it."
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:127
msgid "If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com`, you have successfully installed Draupnir for All and can now start using it."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:100
msgid "The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot mode."
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:129
msgid "If using Zero Touch Deployment, the flow is reversed and the success signal is the initial manager account being invited to the admin room."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:102
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:131
msgid "Draupnir for all installation via this playbook is very much Alpha quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot mode, except that protections requiring homeserver admin access are not available, and the config file is shared between all bots so legacy protections like wordlist share a single global config."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:133
msgid "Granting Users the ability to use D4A"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:104
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:135
msgid "Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recommendation. Using the chat is recommended."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:106
msgid "The bot requires a powerlevel of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297))"
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:137
msgid "The bot requires a power level of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297).) This issue is largely mitigated by the Zero Touch Deployment workflows introduced in Draupnir 3.1.0."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:108
msgid "To allow users or whole homeservers you type /plain !admin allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially."
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:139
msgid "To allow users or whole homeservers you type /plain !admin allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to provision a bot. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:110
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:141
msgid "How to provision a D4A once you are allowed to"
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:112
msgid "To provision a D4A, you need to start a chat with `@draupnir-main:example.com`. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience."
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:143
msgid "Once someone is allowed to provision a bot, simply provision them one with `!admin provision MXID`."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:114
msgid "Congratulations if you made it all the way here because you now have a fully working Draupnir for all deployment."
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:145
msgid "Self-service provisioning is disabled as a security measure because it is currently bugged. Force-provisioning (with `!admin provision`) bypasses this disabled status."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:147
msgid "Note that you should always make sure there is an allow entry matching whoever is provisioned, because once self-service is fixed, the bot of anyone who is not allowed to provision a bot will refuse to start."
msgstr ""
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:149
msgid "Congratulations if you made it all the way here, because you now have a fully working Draupnir for all deployment."
msgstr ""
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -80,369 +80,393 @@ msgstr ""
msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:78
#: ../../../docs/configuring-playbook-bot-baibot.md:42
msgid "Authentication can be configured in one of two mutually-exclusive ways:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:44
msgid "**Password authentication** (`matrix_bot_baibot_config_user_password`) - recommended for most playbook-managed setups, because it integrates with automatic user creation flow used by the playbook, and auto-creates the bot account"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:45
msgid "**Access-token authentication** (`matrix_bot_baibot_config_user_access_token` + `matrix_bot_baibot_config_user_device_id`) - useful for specific [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md)/OIDC setups where password authentication is not available or not desired"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:47
msgid "Even when [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) is enabled, password authentication is still typically the best fit for baibot if you're using a playbook-managed bot account."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:49
msgid "For upstream details, see baibot's [🔐 Authentication](https://github.com/etkecc/baibot/blob/main/docs/configuration/authentication.md) documentation."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:97
msgid "As mentioned above, **this may not be enough**. Continue with the configuration sections below."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:80
#: ../../../docs/configuring-playbook-bot-baibot.md:99
msgid "👮‍♂️ Administrator configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:82
#: ../../../docs/configuring-playbook-bot-baibot.md:106
#: ../../../docs/configuring-playbook-bot-baibot.md:101
#: ../../../docs/configuring-playbook-bot-baibot.md:125
msgid "This is an addition to the [base configuration](#base-configuration)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:84
#: ../../../docs/configuring-playbook-bot-baibot.md:103
msgid "To specify who is considered a bot [👮‍♂️ Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators), you either need to specify `matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The latter is a single variable which affects all bridges and bots."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:86
#: ../../../docs/configuring-playbook-bot-baibot.md:105
msgid "If `matrix_admin` is already configured in your `vars.yml` configuration, you can skip this section."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:88
#: ../../../docs/configuring-playbook-bot-baibot.md:117
#: ../../../docs/configuring-playbook-bot-baibot.md:107
#: ../../../docs/configuring-playbook-bot-baibot.md:136
msgid "**If necessary**, add the following configuration to your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:102
#: ../../../docs/configuring-playbook-bot-baibot.md:121
msgid "👥 Initial users configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:104
#: ../../../docs/configuring-playbook-bot-baibot.md:123
msgid "By default, **all users on your homeserver are considered allowed users**. If that's OK, you can skip this section."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:108
#: ../../../docs/configuring-playbook-bot-baibot.md:127
msgid "To specify who is considered a bot [👥 User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), you may:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:110
#: ../../../docs/configuring-playbook-bot-baibot.md:129
msgid "define an **initial** value for `matrix_bot_baibot_config_initial_global_config_user_patterns` Ansible variable, as shown below"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:111
#: ../../../docs/configuring-playbook-bot-baibot.md:130
msgid "configure the list at runtime via the bot's `!bai access set-users SPACE_SEPARATED_PATTERNS` command"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:113
#: ../../../docs/configuring-playbook-bot-baibot.md:132
msgid "Configuring `matrix_bot_baibot_config_initial_global_config_user_patterns` is optional, but it can be useful to pre-configure the bot with a list of users who should have access to the bot's features."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:115
#: ../../../docs/configuring-playbook-bot-baibot.md:134
msgid "**Note**: Once initially configured, the allowed users list **cannot be managed via Ansible anymore**. It can only be managed subsequently via bot commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:129
#: ../../../docs/configuring-playbook-bot-baibot.md:148
msgid "🤖 Configuring agents via Ansible"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:131
#: ../../../docs/configuring-playbook-bot-baibot.md:150
msgid "You are **not required** to define agents [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration) via Ansible. **To get started quickly**, you can **skip this section and define agents at runtime via chat commands** (following the bot's guidance)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:133
#: ../../../docs/configuring-playbook-bot-baibot.md:152
msgid "Privileged users (like the [👮‍♂️ Administrator](#-administrator-configuration), but potentially others too — see the upstream [🔒 access](https://github.com/etkecc/baibot/blob/main/docs/access.md) documentation) can **define agents dynamically at any time** via chat commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:135
#: ../../../docs/configuring-playbook-bot-baibot.md:154
msgid "The Ansible role includes preset variables for easily enabling some [🤖 agents](https://github.com/etkecc/baibot/blob/main/docs/agents.md) on various [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md) (e.g. OpenAI, etc)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:137
#: ../../../docs/configuring-playbook-bot-baibot.md:156
msgid "Besides the presets, the Ansible role also includes support for configuring additional statically-defined agents via the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:139
#: ../../../docs/configuring-playbook-bot-baibot.md:158
msgid "Agents defined statically and those created dynamically (via chat) are named differently, so **conflict cannot arise**."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:141
#: ../../../docs/configuring-playbook-bot-baibot.md:160
msgid "Depending on your propensity for [GitOps](https://en.wikipedia.org/wiki/DevOps#GitOps), you may prefer to define agents statically via Ansible, or you may wish to do it dynamically via chat."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:143
#: ../../../docs/configuring-playbook-bot-baibot.md:162
msgid "Before proceeding, we recommend reading the upstream documentation on [How to choose a provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#how-to-choose-a-provider). In short, it's probably best to go with [OpenAI](#openai)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:145
#: ../../../docs/configuring-playbook-bot-baibot.md:164
msgid "Anthropic"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:147
#: ../../../docs/configuring-playbook-bot-baibot.md:166
msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Anthropic provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic) with the help of the playbook's preset variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:149
#: ../../../docs/configuring-playbook-bot-baibot.md:173
#: ../../../docs/configuring-playbook-bot-baibot.md:204
#: ../../../docs/configuring-playbook-bot-baibot.md:232
#: ../../../docs/configuring-playbook-bot-baibot.md:168
#: ../../../docs/configuring-playbook-bot-baibot.md:192
#: ../../../docs/configuring-playbook-bot-baibot.md:223
#: ../../../docs/configuring-playbook-bot-baibot.md:251
msgid "Here's an example **addition** to your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:165
#: ../../../docs/configuring-playbook-bot-baibot.md:196
#: ../../../docs/configuring-playbook-bot-baibot.md:222
#: ../../../docs/configuring-playbook-bot-baibot.md:256
#: ../../../docs/configuring-playbook-bot-baibot.md:184
#: ../../../docs/configuring-playbook-bot-baibot.md:215
#: ../../../docs/configuring-playbook-bot-baibot.md:241
#: ../../../docs/configuring-playbook-bot-baibot.md:275
msgid "If you'd like to use more than one model, take a look at the [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset) section below."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:167
#: ../../../docs/configuring-playbook-bot-baibot.md:198
#: ../../../docs/configuring-playbook-bot-baibot.md:224
#: ../../../docs/configuring-playbook-bot-baibot.md:258
#: ../../../docs/configuring-playbook-bot-baibot.md:186
#: ../../../docs/configuring-playbook-bot-baibot.md:217
#: ../../../docs/configuring-playbook-bot-baibot.md:243
#: ../../../docs/configuring-playbook-bot-baibot.md:277
msgid "💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:169
#: ../../../docs/configuring-playbook-bot-baibot.md:188
msgid "Groq"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:171
#: ../../../docs/configuring-playbook-bot-baibot.md:190
msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Groq provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq) with the help of the playbook's preset variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:194
#: ../../../docs/configuring-playbook-bot-baibot.md:213
msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/groq`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:200
#: ../../../docs/configuring-playbook-bot-baibot.md:219
msgid "Mistral"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:202
#: ../../../docs/configuring-playbook-bot-baibot.md:221
msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [🇫🇷 Mistral provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral) with the help of the playbook's preset variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:220
#: ../../../docs/configuring-playbook-bot-baibot.md:239
msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/mistral`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:226
#: ../../../docs/configuring-playbook-bot-baibot.md:245
msgid "OpenAI"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:228
#: ../../../docs/configuring-playbook-bot-baibot.md:247
msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai) with the help of the playbook's preset variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:230
#: ../../../docs/configuring-playbook-bot-baibot.md:249
msgid "The OpenAI provider is **only meant to be used with OpenAI's official API** and compatibility with other services (which do not fully adhere to the OpenAI API spec completely) is limited. **If you're targeting an OpenAI-compatible service**, use the [OpenAI Compatible](#openai-compatible) provider instead."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:254
#: ../../../docs/configuring-playbook-bot-baibot.md:273
msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/openai`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:260
#: ../../../docs/configuring-playbook-bot-baibot.md:279
msgid "OpenAI Compatible"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:262
#: ../../../docs/configuring-playbook-bot-baibot.md:281
msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI Compatible provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai-compatible) with the help of the playbook's preset variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:264
#: ../../../docs/configuring-playbook-bot-baibot.md:283
msgid "This provider allows you to use OpenAI-compatible API services like [OpenRouter](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openrouter), [Together AI](https://github.com/etkecc/baibot/blob/main/docs/providers.md#together-ai), etc."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:266
#: ../../../docs/configuring-playbook-bot-baibot.md:285
msgid "Some of these popular services already have **shortcut** providers (see [supported providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md#supported-providers) leading to this one behind the scenes — this make it easier to get started."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:268
#: ../../../docs/configuring-playbook-bot-baibot.md:287
msgid "As of this moment, the playbook does not include presets for any of these services, so you'll need to [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:270
#: ../../../docs/configuring-playbook-bot-baibot.md:289
msgid "Configuring additional agents (without a preset)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:272
#: ../../../docs/configuring-playbook-bot-baibot.md:291
msgid "The Ansible role may be lacking preset variables for some [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), or you may wish to statically-define an agent on the same provider twice (or more) with different configuration."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:274
#: ../../../docs/configuring-playbook-bot-baibot.md:293
msgid "It's possible to inject your own agent configuration using the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:276
#: ../../../docs/configuring-playbook-bot-baibot.md:295
msgid "You can also define providers at runtime, by chatting with the bot, so using Ansible is not a requirement."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:278
#: ../../../docs/configuring-playbook-bot-baibot.md:297
msgid "Below is an an **example** demonstrating **statically-defining agents via Ansible without using presets**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:317
#: ../../../docs/configuring-playbook-bot-baibot.md:336
msgid "Because these are [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agents, they will be given a `static/` ID prefix and will be named `static/my-openai-gpt-3.5-turbo-agent` and `static/my-ollama-agent`, respectively."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:319
#: ../../../docs/configuring-playbook-bot-baibot.md:338
msgid "💡 To figure out what to put in the `config` section, refer to the [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md) page, which contains **sample configuration YAML for each provider**."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:321
#: ../../../docs/configuring-playbook-bot-baibot.md:340
msgid "As with any [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), defining them means they exist. To actually make use of them, they need to be configured as handlers globally or in a specific room — see [Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:323
#: ../../../docs/configuring-playbook-bot-baibot.md:342
msgid "💡 You may also wish to use these new agents for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:325
#: ../../../docs/configuring-playbook-bot-baibot.md:344
msgid "🤝 Configuring initial default handlers"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:327
#: ../../../docs/configuring-playbook-bot-baibot.md:346
msgid "This section is only useful if you're [🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible), as it lets you put these agents to use as soon as the bot starts (by adjusting the bot's **initial global configuration**)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:329
#: ../../../docs/configuring-playbook-bot-baibot.md:348
msgid "If you're not configuring agents via Ansible, you can skip this section."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:331
#: ../../../docs/configuring-playbook-bot-baibot.md:350
msgid "This section is only useful the first time around. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:333
#: ../../../docs/configuring-playbook-bot-baibot.md:352
msgid "baibot supports [various purposes](https://github.com/etkecc/baibot/blob/main/docs/features.md):"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:335
#: ../../../docs/configuring-playbook-bot-baibot.md:354
msgid "[💬 text-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-generation): communicating with you via text"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:337
#: ../../../docs/configuring-playbook-bot-baibot.md:356
msgid "[🦻 speech-to-text](https://github.com/etkecc/baibot/blob/main/docs/features.md#-speech-to-text): turning your voice messages into text"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:339
#: ../../../docs/configuring-playbook-bot-baibot.md:358
msgid "[🗣️ text-to-speech](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-to-speech): turning bot or users text messages into voice messages"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:341
#: ../../../docs/configuring-playbook-bot-baibot.md:360
msgid "[🖌️ image-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-image-generation): generating images based on instructions"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:343
#: ../../../docs/configuring-playbook-bot-baibot.md:362
msgid "❓ catch-all: special purposes, indicating use as a fallback (when no specific handler is configured)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:345
#: ../../../docs/configuring-playbook-bot-baibot.md:364
msgid "[Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models) is made possible by the bot's ability to have different [🤝 handlers](https://github.com/etkecc/baibot/blob/main/docs/configuration/handlers.md) configured for different purposes."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:347
#: ../../../docs/configuring-playbook-bot-baibot.md:366
msgid "This configuration can be done as a global fallback, or per-room. Both of these [🛠️ configurations](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md) are managed at runtime (viat chat), but **the global configuration can have some initial defaults configured via Ansible**."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:349
#: ../../../docs/configuring-playbook-bot-baibot.md:368
msgid "You can configure the **initial values** for these via Ansible, via the `matrix_bot_baibot_config_initial_global_config_handler_*` variables."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:351
#: ../../../docs/configuring-playbook-bot-baibot.md:370
msgid "Example **additional** `vars.yml` configuration:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:368
#: ../../../docs/configuring-playbook-bot-baibot.md:387
msgid "**Note**: these are initial defaults for the bot's global configuration. As such, changing any of these values subsequently has no effect on the bot's behavior. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:370
#: ../../../docs/configuring-playbook-bot-baibot.md:389
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:372
#: ../../../docs/configuring-playbook-bot-baibot.md:391
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:374
#: ../../../docs/configuring-playbook-bot-baibot.md:393
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:376
#: ../../../docs/configuring-playbook-bot-baibot.md:395
msgid "`roles/custom/matrix-bot-baibot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:377
#: ../../../docs/configuring-playbook-bot-baibot.md:396
msgid "`roles/custom/matrix-bot-baibot/templates/config.yaml.j2` for the bot's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_bot_baibot_configuration_extension_yaml` variable"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:379
#: ../../../docs/configuring-playbook-bot-baibot.md:398
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:381
#: ../../../docs/configuring-playbook-bot-baibot.md:400
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:388
#: ../../../docs/configuring-playbook-bot-baibot.md:407
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:390
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
#: ../../../docs/configuring-playbook-bot-baibot.md:409
msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account when password authentication is used."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:392
#: ../../../docs/configuring-playbook-bot-baibot.md:411
msgid "If you're using access-token authentication, the bot account must already exist and the configured token + device ID must match that account. This mode is mainly for MAS/OIDC setups where password-based bot login is not suitable."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:413
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:394
#: ../../../docs/configuring-playbook-bot-baibot.md:415
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:396
msgid "If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password."
#: ../../../docs/configuring-playbook-bot-baibot.md:417
msgid "If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password. (This note applies to password authentication mode.)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:398
#: ../../../docs/configuring-playbook-bot-baibot.md:419
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:400
#: ../../../docs/configuring-playbook-bot-baibot.md:421
msgid "To use the bot, invite it to any existing Matrix room (`/invite @baibot:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:402
#: ../../../docs/configuring-playbook-bot-baibot.md:423
msgid "If you're an allowed bot [👥 user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) (see [👥 Initial users configuration](#-initial-users-configuration)), the bot will accept your invitation and join the room."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:404
#: ../../../docs/configuring-playbook-bot-baibot.md:425
msgid "After joining, the bot will introduce itself and show information about the [✨ features](https://github.com/etkecc/baibot/blob/main/docs/features.md) that are enabled for it."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:406
#: ../../../docs/configuring-playbook-bot-baibot.md:427
msgid "If you've [🤖 configured one or more agents via Ansible](#-configuring-agents-via-ansible) and have [🤝 configured initial default handlers](#configuring-initial-default-handlers), the bot will immediately be able to make use of these agents for this new room. Otherwise, you will need to configure agents and/or handlers via chat commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:408
#: ../../../docs/configuring-playbook-bot-baibot.md:429
msgid "Send `!bai help` to the bot in the room to see the available commands."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:410
#: ../../../docs/configuring-playbook-bot-baibot.md:431
msgid "You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) project's documentation."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:412
#: ../../../docs/configuring-playbook-bot-baibot.md:433
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:414
#: ../../../docs/configuring-playbook-bot-baibot.md:435
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-baibot`."
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:416
#: ../../../docs/configuring-playbook-bot-baibot.md:437
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:418
#: ../../../docs/configuring-playbook-bot-baibot.md:439
msgid "The default logging level for this service is `info`. If you want to increase the verbosity to `debug` (or even `trace`), add the following configuration to your `vars.yml` file and re-run the playbook:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-baibot.md:432
#: ../../../docs/configuring-playbook-bot-baibot.md:453
msgid "**Alternatively**, you can use a single variable to set the logging level for all of the above (bot + all libraries):"
msgstr ""
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -113,7 +113,7 @@ msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x f
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:92
msgid "If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password."
msgid "If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-buscarron.md:94
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
"POT-Creation-Date: 2026-05-07 14:00+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -16,419 +16,487 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../../docs/configuring-playbook-bot-draupnir.md:10
#: ../../../docs/configuring-playbook-bot-draupnir.md:11
msgid "Setting up Draupnir (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:12
#: ../../../docs/configuring-playbook-bot-draupnir.md:13
msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation bot for you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:14
#: ../../../docs/configuring-playbook-bot-draupnir.md:15
msgid "See the project's [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:16
#: ../../../docs/configuring-playbook-bot-draupnir.md:17
msgid "This documentation page is about installing Draupnir in bot mode. As an alternative, you can run a multi-instance Draupnir deployment by installing [Draupnir in appservice mode](./configuring-playbook-appservice-draupnir-for-all.md) (called Draupnir-for-all) instead."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:18
#: ../../../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)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:20
#: ../../../docs/configuring-playbook-bot-draupnir.md:21
msgid "Prerequisites"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:22
msgid "Create a management room"
#: ../../../docs/configuring-playbook-bot-draupnir.md:23
msgid "Prerequisites for Zero Touch Deployment (recommended)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:24
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."
#: ../../../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:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:26
msgid "[!WARNING] Anyone in this room can control the bot so it is important that you only invite trusted users to this room."
#: ../../../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)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:29
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))."
msgid "A user account for Draupnir."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:31
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`."
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:33
msgid "End-to-End Encryption support"
msgid "Create a management room (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:35
msgid "Decide whether you want to support having an encrypted management room or not. Draupnir can still protect encrypted rooms without encryption support enabled."
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:37
msgid "[!WARNING] 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
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
msgid "E2EE support for the management room is mutually exclusive with Zero Touch Deployment of Draupnir."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:44
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
msgid "End-to-End Encryption support"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:48
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
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:39
#: ../../../docs/configuring-playbook-bot-draupnir.md:52
msgid "Disable Pantalaimon for Draupnir (since v2.0.0; optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:41
#: ../../../docs/configuring-playbook-bot-draupnir.md:54
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:43
#: ../../../docs/configuring-playbook-bot-draupnir.md:56
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:45
#: ../../../docs/configuring-playbook-bot-draupnir.md:58
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:47
#: ../../../docs/configuring-playbook-bot-draupnir.md:60
msgid "Native E2EE support"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:49
#: ../../../docs/configuring-playbook-bot-draupnir.md:62
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:51
#: ../../../docs/configuring-playbook-bot-draupnir.md:64
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:53
#: ../../../docs/configuring-playbook-bot-draupnir.md:66
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:64
#: ../../../docs/configuring-playbook-bot-draupnir.md:77
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:66
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 earlier."
#: ../../../docs/configuring-playbook-bot-draupnir.md:79
msgid "Configuration for Zero Touch Deployment (recommended)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:85
msgid "Create and invite the bot to the management room"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:87
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:93
msgid "**Note**: the `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
#: ../../../docs/configuring-playbook-bot-draupnir.md:81
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
msgid "Then, invite the bot (`@bot.draupnir:example.com`) to its management room which you have created earlier."
msgid "Configuration without Zero Touch Deployment"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:97
msgid "Make sure the account is free from rate limiting (optional, recommended)"
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:99
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.**"
#: ../../../docs/configuring-playbook-bot-draupnir.md:116
msgid "Running both bot mode and appservice mode"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:101
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:103
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:105
msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:107
msgid "Add the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:109
msgid "To expose the APIs publicly, add the following configuration to your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:115
msgid "Obtain an access token for admin account"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:117
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:119
msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
#: ../../../docs/configuring-playbook-bot-draupnir.md:118
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
msgid "Run the `curl` command"
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
msgid "To disable rate limiting, run the following command on systems that ship curl. Before running it, make sure to replace:"
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
msgid "`ADMIN_ACCESS_TOKEN_HERE` with the access token of the admin account"
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:127
msgid "`example.com` with your base domain"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:128
msgid "`@bot.draupnir:example.com` with the MXID of your Draupnir bot user"
#: ../../../docs/configuring-playbook-bot-draupnir.md:132
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:207
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:135
msgid "This does not work on outdated Windows 10 as curl is not available there."
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
msgid "Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally."
msgid "Creating a user account for the bot (when using Zero Touch Deployment)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:138
msgid "Abuse Reports"
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
msgid "Draupnir can receive reports in the management room."
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
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:"
msgid "Make sure the account is free from rate limiting (optional, recommended)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:144
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
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
msgid "Enabling synapse-http-antispam support"
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
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."
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
msgid "Add the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:154
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
msgid "These protections need to be manually activated and consulting the [enabling protections](#enabling-built-in-protections) guide can be helpful or consulting upstream documentation."
msgid "Obtain an access token for admin account"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:168
msgid "Extending the configuration"
#: ../../../docs/configuring-playbook-bot-draupnir.md:162
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:170
msgid "There are some additional things you may wish to configure about the bot."
#: ../../../docs/configuring-playbook-bot-draupnir.md:164
msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:167
msgid "Run the `curl` command"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:169
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
msgid "`ADMIN_ACCESS_TOKEN_HERE` with the access token of the admin account"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:172
msgid "Take a look at:"
msgid "`example.com` with your base domain"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:174
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"
#: ../../../docs/configuring-playbook-bot-draupnir.md:173
msgid "`@bot.draupnir:example.com` with the MXID of your Draupnir bot user"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:176
msgid "For example, to change Draupnir's `acceptInvitesFromSpace` option to `!qporfwt:example.com`, add the following configuration to your `vars.yml` file:"
#: ../../../docs/configuring-playbook-bot-draupnir.md:179
#: ../../../docs/configuring-playbook-bot-draupnir.md:254
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:190
msgid "Migrating from Mjolnir (Only required if migrating)"
#: ../../../docs/configuring-playbook-bot-draupnir.md:181
msgid "This does not work on outdated Windows 10 as curl is not available there."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:192
msgid "Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration."
#: ../../../docs/configuring-playbook-bot-draupnir.md:182
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
msgid "Abuse Reports"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:186
msgid "Draupnir can receive reports in the management room."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:188
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
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)."
msgid "Enabling synapse-http-antispam support"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:196
msgid "That is all you need to do due to that Draupnir can complete migration on its own."
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:198
msgid "Installing"
#: ../../../docs/configuring-playbook-bot-draupnir.md:206
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:200
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:209
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:211
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:213
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."
#: ../../../docs/configuring-playbook-bot-draupnir.md:208
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
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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_password` to let the bot know its new password."
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:217
msgid "Usage"
msgid "There are some additional things you may wish to configure about the bot."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:219
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."
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:221
msgid "Below is a **non-exhaustive quick-start guide** for the impatient."
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
msgid "Making Draupnir join and protect a room"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:225
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:227
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:229
msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:231
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:233
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:235
msgid "Giving Draupnir permissions to do its job"
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
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**."
msgid "Migrating from Mjolnir (Only required if migrating)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:239
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)."
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
msgid "Subscribing to a public policy list"
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
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)."
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
msgid "Policy lists are maintained in Matrix rooms. Popular ones maintained in the public are:"
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:247
msgid "`#community-moderation-effort-bl:neko.dev`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:248
msgid "`#huginn-muninn-active-threats:feline.support`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:250
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:252
msgid "Creating your own policy lists and rules"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:254
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."
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:256
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."
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
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)."
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
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."
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
msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)."
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
msgid "(ban a single user on a given homeserver): `!draupnir ban @charles:example.com my-bans Rude to others`"
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:265
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`"
#: ../../../docs/configuring-playbook-bot-draupnir.md:266
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:267
msgid "As a result of running these commands, you may observe:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:269
msgid "Draupnir creating `m.policy.rule.user` state events in the `#my-bans-bl:example.com` room on your server"
#: ../../../docs/configuring-playbook-bot-draupnir.md:268
msgid "Below is a **non-exhaustive quick-start guide** for the impatient."
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:270
msgid "applying these rules against all rooms that Draupnir is an Administrator in"
msgid "Making Draupnir join and protect a room"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:272
msgid "You can undo bans with the [unban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-unban-command)."
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
msgid "Enabling built-in protections"
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
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\")."
msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:278
msgid "To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room."
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
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`)."
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
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`)."
msgid "Giving Draupnir permissions to do its job"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:284
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`)."
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
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
msgid "Subscribing to a public policy list"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:290
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
msgid "Policy lists are maintained in Matrix rooms. Popular ones maintained in the public are:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:294
msgid "`#community-moderation-effort-bl:neko.dev`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:295
msgid "`#huginn-muninn-active-threats:feline.support`"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:297
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
msgid "Creating your own policy lists and rules"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:301
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
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
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
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
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
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
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
msgid "As a result of running these commands, you may observe:"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:316
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
msgid "applying these rules against all rooms that Draupnir is an Administrator in"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:319
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
msgid "Enabling built-in protections"
msgstr ""
#: ../../../docs/configuring-playbook-bot-draupnir.md:323
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
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
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
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
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
msgid "To **disable a given protection**, send a command like this: `!draupnir protections disable PROTECTION_NAME` (e.g. `!draupnir protections disable JoinWaveShortCircuitProtection`)."
msgstr ""
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -113,7 +113,7 @@ msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x f
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:81
msgid "If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password."
msgid "If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-honoroit.md:83
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -89,7 +89,7 @@ msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x f
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:74
msgid "If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password."
msgid "If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:76
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -85,7 +85,7 @@ msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x f
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:60
msgid "If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password."
msgid "If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:62
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -138,7 +138,7 @@ msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x f
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:106
msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password."
msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password."
msgstr ""
#: ../../../docs/configuring-playbook-bot-maubot.md:108
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
"POT-Creation-Date: 2026-04-03 11:56+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -82,7 +82,7 @@ msgid "**Note**: access to the APIs is restricted with a valid access token, so
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:49
msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)."
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
@@ -251,7 +251,7 @@ msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x f
msgstr ""
#: ../../../docs/configuring-playbook-bot-mjolnir.md:201
msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password."
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
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
"POT-Creation-Date: 2026-04-15 09:10+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -16,242 +16,22 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:12
msgid "Setting up Appservice Slack bridging (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:14
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:15
msgid "Bridging to [Slack](https://slack.com) can also happen via the [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridge supported by the playbook."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:16
msgid "Currently (as of November, 2024) **this component is not available for new installation unless you have already created a classic Slack application** (which the bridge makes use of in order to enable bridging between Slack and Matrix), because the creation of classic Slack applications has been discontinued since June 4 2024. The author of the bridge claims [here](https://github.com/matrix-org/matrix-appservice-slack/issues/789#issuecomment-2172947787) that he plans to support the modern Slack application and until then \"the best (and only) option for new installations is to use the webhook bridging\"."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:18
msgid "The playbook can install and configure [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) for you."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:20
msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-slack/blob/master/README.md) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:22
msgid "Prerequisites"
msgid "Setting up Appservice Slack bridging (optional, removed)"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:24
msgid "Create a Classic Slack App"
msgid "🪦 The playbook used to be able to install and configure [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack), but no longer includes this component, as it had been unavailable for new installation since 2024, and was finally abandoned because the public Matrix.org Slack bridge has been decommissioned on January 14th, 2026."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:26
msgid "First, you need to create a Classic Slack App [here](https://api.slack.com/apps?new_classic_app=1)."
msgid "**Note**: Bridging to [Slack](https://slack.com) can also happen via the [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridge supported by the playbook."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:28
msgid "Name the app \"matrixbot\" (or anything else you'll remember). Select the team/workspace this app will belong to. Click on bot users and add a new bot user. We will use this account to bridge the the rooms."
msgid "Uninstalling the component manually"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:30
msgid "Then, click on Event Subscriptions and enable them and use the request url: `https://matrix.example.com/appservice-slack`."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:32
msgid "Add the following events as `Bot User Events` and save:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:34
msgid "team_domain_change"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:35
msgid "message.channels"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:36
msgid "message.groups (if you want to bridge private channels)"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:37
msgid "reaction_added"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:38
msgid "reaction_removed"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:40
msgid "Next, click on \"OAuth & Permissions\" and add the following scopes:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:42
msgid "chat:write:bot"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:43
msgid "users:read"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:44
msgid "reactions:write"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:45
msgid "files:write:user (if you want to bridge files)"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:47
msgid "**Note**: In order to make Slack files visible to Matrix users, this bridge will make Slack files visible to anyone with the url (including files in private channels). This is different than the current behavior in Slack, which only allows authenticated access to media posted in private channels. See MSC701 for details."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:49
msgid "Click on \"Install App\" and \"Install App to Workspace\". Note the access tokens shown. You will need the Bot User OAuth Access Token and if you want to bridge files, the OAuth Access Token whenever you link a room."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:51
msgid "Create an administration control room on Matrix"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:53
msgid "Create a new Matrix room to act as the administration control room."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:55
msgid "Note its internal room ID. This can be done in Element Web by sending a message, opening the options for that message and choosing \"view source\". The room ID will be displayed near the top."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:57
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:59
msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:75
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:77
msgid "There are some additional things you may wish to configure about the bridge."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:79
msgid "Take a look at:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:81
msgid "`roles/custom/matrix-bridge-appservice-slack/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:82
msgid "`roles/custom/matrix-bridge-appservice-slack/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_appservice_slack_configuration_extension_yaml` variable"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:84
msgid "For example, to change the bot's username from `slackbot`, add the following configuration to your `vars.yml` file. Replace `examplebot` with your own."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:91
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:93
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:100
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:102
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:104
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:106
msgid "To use the bridge, you need to send `/invite @slackbot:example.com` to invite the bridge bot user into the admin room."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:108
msgid "If Team Sync is not enabled, for each channel you would like to bridge, perform the following steps:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:110
msgid "Create a Matrix room in the usual manner for your client. Take a note of its Matrix room ID — it will look something like `!qporfwt:example.com`."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:111
msgid "Invite the bot user to both the Slack and Matrix channels you would like to bridge using `/invite @matrixbot` for Slack and `/invite @slackbot:example.com` for Matrix."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:112
msgid "Determine the \"channel ID\" that Slack uses to identify the channel. You can see it when you open a given Slack channel in a browser. The URL reads like this: `https://app.slack.com/client/XXX/<the channel ID>/details/`."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:113
msgid "Issue a link command in the administration control room with these collected values as arguments:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:115
msgid "with file bridging:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:121
msgid "without file bridging:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:127
msgid "These arguments can be shortened to single-letter forms:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:133
msgid "Unlinking"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:135
msgid "Channels can be unlinked again by sending this:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:141
msgid "Unlinking doesn't only disconnect the bridge, but also makes the slackbot leave the bridged Matrix room. So in case you want to re-link later, don't forget to re-invite the slackbot into this room again."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:143
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:145
msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-appservice-slack`."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:147
msgid "Linking: \"Room is now pending-name\""
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:149
msgid "This typically means that you haven't used the correct Slack channel ID. Unlink the room and recheck 'Determine the \"channel ID\"' from above."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:151
msgid "Messages work from Matrix to Slack, but not the other way around"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:153
msgid "Check the logs, and if you find the message like below, unlink your room, reinvite the bot and re-link it again."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:155
msgid "`WARN SlackEventHandler Ignoring message from unrecognised Slack channel ID : %s (%s) <the channel ID> <some other ID>`"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:157
msgid "This may particularly hit you, if you tried to unsuccessfully link your room multiple times without unlinking it after each failed attempt."
msgid "If you still have matrix-appservice-slack installed on your Matrix server, the playbook can no longer help you uninstall it and you will need to do it manually. To uninstall manually, run these commands on the server:"
msgstr ""
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
"POT-Creation-Date: 2026-04-15 09:10+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -28,130 +28,146 @@ msgstr ""
msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md) bridge supported by the playbook."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:18
msgid "For using as a Bot we recommend the [Appservice Discord](configuring-playbook-bridge-appservice-discord.md), because it supports plumbing."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:19
msgid "For personal use with a discord account we recommend the `mautrix-discord` bridge (the one being discussed here), because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:21
msgid "The playbook can install and configure [mautrix-discord](https://github.com/mautrix/discord) for you."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:23
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:21
msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/discord/index.html) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:25
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:23
msgid "Prerequisites"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:25
msgid "There are 3 ways to login to discord using this bridge, either by [scanning a QR code](https://docs.mau.fi/bridges/go/discord/authentication.html#qr-login) using the Discord mobile app, by using a [Discord token](https://docs.mau.fi/bridges/go/discord/authentication.html#token-login), **or** by using a [Discord bot token](https://docs.mau.fi/bridges/go/discord/authentication.html#bot-token-login)."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:27
msgid "There are 2 ways to login to discord using this bridge, either by [scanning a QR code](#method-1-login-using-qr-code-recommended) using the Discord mobile app **or** by using a [Discord token](#method-2-login-using-discord-token-not-recommended)."
msgid "⚠️ QR code login is considered a self-bot and is forbidden by Discord. It can result in an account termination. See the [Discord policy](https://support.discord.com/hc/en-us/articles/115002192352-Automated-User-Accounts-Self-Bots)."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:29
msgid "If this is a dealbreaker for you, consider using [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md). This comes with its own complexity and limitations, however, so we recommend that you proceed with this one if possible."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:31
msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:33
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:31
msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:35
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:33
msgid "See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:37
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:35
msgid "**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:39
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:37
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:41
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:39
msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:47
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:45
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:49
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:47
msgid "There are some additional things you may wish to configure about the bridge."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:52
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:50
msgid "See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:54
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:52
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:56
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:54
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:63
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:61
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:65
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:63
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:67
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:65
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:69
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:67
msgid "To use the bridge, you need to start a chat with `@discordbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:71
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:69
msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/discord/authentication.html)."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:73
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:71
msgid "After logging in, the bridge will create portal rooms for some recent direct messages."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:75
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:73
msgid "Bridge guilds"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:77
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:75
msgid "If you'd like to bridge guilds, send `guilds status` to see the list of guilds, then send `guilds bridge GUILD_ID_HERE` for each guild that you'd like bridged. Make sure to replace `GUILD_ID_HERE` with the guild's ID."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:79
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:77
msgid "After bridging, spaces will be created automatically, and rooms will be created if necessary when messages are received. You can also pass `--entire` to the bridge command to immediately create all rooms."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:81
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:79
msgid "If you want to manually bridge channels, invite the bot to the room you want to bridge, and run `!discord bridge CHANNEL_ID_HERE` to bridge the room. Make sure to replace `CHANNEL_ID_HERE` with the channel's ID."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:81
msgid "Enable relay"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:83
msgid "Troubleshooting"
msgid "The bridge supports using Discord's webhook feature to relay messages from Matrix users who haven't logged into the bridge."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:85
msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-discord`."
msgid "In a room that has already been bridged, run `!discord set-relay --create`. The bridge will then create a webhook in the bridged discord channel and begin relaying messages. If the discord user does not have access to manage webhooks, run `!discord set-relay --url <url>` with the url of an already created webhook. (See Discords [Intro to webhooks](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks))"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:87
msgid "Increase logging verbosity"
msgid "More information on relaying is available on the [official documentation](https://docs.mau.fi/bridges/go/discord/relay.html)."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:89
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:91
msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-discord`."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:93
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:95
msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:102
msgid "Command requires room admin rights when user is creator"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:104
msgid "[MSC4289](https://github.com/matrix-org/matrix-spec-proposals/blob/main/proposals/4289-privilege-creators.md), introduced in [room version 12](https://spec.matrix.org/unstable/rooms/v12/), gives creators an infinitley high powerlevel. At the time of implementation, mautrix-discord and similar applications may not identify creators as or above admins. Either a separate admin user will need to manage the bridge or the room version should be less than version 12."
msgstr ""
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
"POT-Creation-Date: 2026-04-15 09:10+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -25,117 +25,105 @@ msgid "<sup>Refer the common guide for configuring mautrix bridges: [Setting up
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:14
msgid "**Note**: bridging to [Slack](https://slack.com/) can also happen via the [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) bridge supported by the playbook."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:15
msgid "For using as a Bot we recommend the [Appservice Slack](configuring-playbook-bridge-appservice-slack.md), because it supports plumbing. Note that it is not available for new installation unless you have already created a classic Slack application, because the creation of classic Slack applications, which this bridge makes use of, has been discontinued."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:16
msgid "For personal use with a slack account we recommend the `mautrix-slack` bridge (the one being discussed here), because it is the most fully-featured and stable of the 3 Slack bridges supported by the playbook."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:18
msgid "The playbook can install and configure [mautrix-slack](https://github.com/mautrix/slack) for you."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:20
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:16
msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/slack/index.html) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:22
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:18
msgid "See the [features and roadmap](https://github.com/mautrix/slack/blob/main/ROADMAP.md) for more information."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:24
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:20
msgid "Prerequisites"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:26
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:22
msgid "For using this bridge, you would need to authenticate by **providing your username and password** (legacy) or by using a **token login**. See more information in the [docs](https://docs.mau.fi/bridges/go/slack/authentication.html)."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:28
msgid "Note that neither of these methods are officially supported by Slack. [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) uses a Slack bot account which is the only officially supported method for bridging a Slack channel."
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:24
msgid "Note that neither of these methods are officially supported by Slack."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:30
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:26
msgid "Enable Appservice Double Puppet (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:32
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:28
msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:34
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:30
msgid "See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:36
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:32
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:38
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:34
msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:44
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:40
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:46
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:42
msgid "There are some additional things you may wish to configure about the bridge."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:48
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:44
msgid "See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:50
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:46
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:52
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:48
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:59
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:55
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:61
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:57
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:63
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:59
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:65
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:61
msgid "To use the bridge, you need to start a chat with `@slackbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:67
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:63
msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/slack/authentication.html)."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:69
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:65
msgid "If you authenticated using a token, the recent chats will be bridged automatically (depending on the `conversation_count` setting). Otherwise (i.e. logging with the Discord application), the chats the bot is in will be bridged automatically."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:71
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:67
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:73
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:69
msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-slack`."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:75
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:71
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:77
#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:73
msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
msgstr ""
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
"POT-Creation-Date: 2026-05-07 11:16+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -29,7 +29,7 @@ msgid "The playbook can install and configure [mautrix-telegram](https://github.
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:20
msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/telegram/index.html) to learn what it does and why it might be useful to you."
msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/telegram/index.html) to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:22
@@ -45,11 +45,11 @@ msgid "To use the bridge, you'd need to obtain an API key from [https://my.teleg
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:28
msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)"
msgid "Enable Appservice Double Puppet (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:30
msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook."
msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:32
@@ -57,113 +57,85 @@ msgid "See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:34
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:36
msgid "Double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:38
msgid "If you decided to enable Double Puppeting manually, send `login-matrix` to the bot in order to receive an instruction about how to send an access token to it."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:40
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:42
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:36
msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `YOUR_TELEGRAM_APP_ID` and `YOUR_TELEGRAM_API_HASH`."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:50
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:44
msgid "Relaying"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:52
msgid "Enable relay-bot (optional)"
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:46
msgid "This bridge supports the common [mautrix bridge relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional). Once enabled, any authenticated user can be turned into a relaybot for a chat by sending `!tg set-relay` in that chat."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:54
msgid "If you want to use the relay-bot feature ([relay bot documentation](https://docs.mau.fi/bridges/python/telegram/relay-bot.html)), which allows anonymous user to chat with telegram users, add the following configuration to your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:64
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:48
msgid "Configure a user as an administrator of the bridge (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:66
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:50
msgid "You might also want to give permissions to a user to administrate the bot. See [this section](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional) on the common guide for details about it."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:68
msgid "More details about permissions in this example: https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-config.yaml#L410"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:70
msgid "Use the bridge for direct chats only (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:72
msgid "If you want to exclude all groups from syncing and use the Telegram-Bridge only for direct chats, add the following configuration to your `vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:78
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:52
msgid "Extending the configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:80
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:54
msgid "There are some additional things you may wish to configure about the bridge."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:83
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:56
msgid "See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:85
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:58
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:87
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:60
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:94
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:67
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:96
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:69
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:98
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:71
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:100
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:73
msgid "To use the bridge, you need to start a chat with `@telegrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:102
msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/telegram/authentication.html)."
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:75
msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/telegram/authentication.html)."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:104
msgid "After logging in, the bridge will create portal rooms for all of your Telegram groups and invite you to them. Note that the bridge won't automatically create rooms for private chats."
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:77
msgid "After logging in, the bridge will create portal rooms for all of your Telegram groups and invite you to them."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:106
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:79
msgid "Troubleshooting"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:108
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:81
msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-telegram`."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:110
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:83
msgid "Increase logging verbosity"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:112
msgid "The default logging level for this component is `WARNING`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:85
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 ""

Some files were not shown because too many files have changed in this diff Show More