diff --git a/i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po b/i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po index b348f5623..0c45bab0f 100644 --- a/i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po +++ b/i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po @@ -8,283 +8,283 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2026-02-13 10:32+0000\n" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../YEAR-IN-REVIEW.md:8 +#: ../../../YEAR-IN-REVIEW.md:1 msgid "2023" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:10 +#: ../../../YEAR-IN-REVIEW.md:3 msgid "2023 was a year filled with many changes for matrix-docker-ansible-deploy. In this post, we're looking backward at some of the major changes that happened this year, as well as taking a glimpse of what's ahead in 2024." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:12 +#: ../../../YEAR-IN-REVIEW.md:5 msgid "2023 is probably [the year of AI](https://journal.everypixel.com/2023-the-year-of-ai), with millions of people jumping aboard [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/chatgpt) train. matrix-docker-ansible-deploy is no stranger to this and 2023 began with a PR from [bertybuttface](https://github.com/bertybuttface) who added support for [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#chatgpt-support)). While OpenAI's chat GPT website was frequently overloaded in the past, their API was up which made using this bot both convenient and more reliable." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:14 -msgid "AI aside, with the playbook's focus being containers, we're **doubling down on being \"container native\"** and becoming more interoperable for people hosting other containers on the Matrix server. In [2022](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/YEAR-IN-REVIEW.md#2022), we've announced a few sibling Ansible playbooks, their use of [Traefik](https://doc.traefik.io/traefik/) and the possibility of matrix-docker-ansible-deploy also switching to this reverse-proxy. This prediction materialized quickly. The **largest change** in the playbook in 2023 happened way back in February - matrix-docker-ansible-deploy [starting the switch from nginx to Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support) and then quickly [making Treafik the default reverse-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#traefik-is-the-default-reverse-proxy-now). As noted in the changelog entries, we envisioned a quick and complete elimination of `matrix-nginx-proxy`, but at the end of 2023, it hasn't happened yet. The playbook is already using Traefik as the front-most reverse-proxy, but nginx (via `matrix-nginx-proxy`) is still around - it has taken a step back and is only used internally for new setups. Work got to a stall due to:" +#: ../../../YEAR-IN-REVIEW.md:7 +msgid "AI aside, with the playbook's focus being containers, we're **doubling down on being \"container native\"** and becoming more interoperable for people hosting other containers on the Matrix server. In [2022](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/YEAR-IN-REVIEW.md#2022), we've announced a few sibling Ansible playbooks, their use of [Traefik](https://doc.traefik.io/traefik/) and the possiblity of matrix-docker-ansible-deploy also switching to this reverse-proxy. This prediction materialized quickly. The **largest change** in the playbook in 2023 happened way back in February - matrix-docker-ansible-deploy [starting the switch from nginx to Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support) and then quickly [making Treafik the default reverse-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#traefik-is-the-default-reverse-proxy-now). As noted in the changelog entries, we envisioned a quick and complete elimination of `matrix-nginx-proxy`, but at the end of 2023, it hasn't happened yet. The playbook is already using Traefik as the front-most reverse-proxy, but nginx (via `matrix-nginx-proxy`) is still around - it has taken a step back and is only used internally for new setups. Work got to a stall due to:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:16 +#: ../../../YEAR-IN-REVIEW.md:9 msgid "complexity: untangling the overly large and messy `matrix-nginx-proxy` component is difficult" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:17 +#: ../../../YEAR-IN-REVIEW.md:10 msgid "the current setup became \"good enough\" because nginx has become an internal implementation detail for those who have migrated to Traefik. Traefik is already the default public reverse-proxy and gives better possibilities to people wishing to run other web-exposed containers on their Matrix server via [Docker Compose](https://docs.docker.com/compose/), other Ansible playbooks like [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) (more about this one, below) or any other way." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:19 +#: ../../../YEAR-IN-REVIEW.md:12 msgid "`matrix-nginx-proxy` is no longer in the way of us being interoperable, but its ugly internal details are still there. It is one more proxy in the long chain of reverse-proxies we have and we'd like to cut it out. This would both make things simpler and also boost performance." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:21 +#: ../../../YEAR-IN-REVIEW.md:14 msgid "The delay in eliminating `matrix-nginx-proxy` has probably been welcome by many existing users who decided to postpone the Traefik migration a bit longer. In 2024, work on eliminating `matrix-nginx-proxy` will continue with rapid pace. People who are still using `matrix-nginx-proxy` as their front-most reverse-proxy will need to rework their setup. About a year of putting it off has been long enough." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:23 +#: ../../../YEAR-IN-REVIEW.md:16 msgid "This large Traefik reverse-proxy change was also accompanied by another internal change which began in 2022, but continued in 2023 - **moving non-Matrix-related roles from being internal to the playbook to living their own life outside of it**. Various roles were made more decoupled and moved outside of the playbook, so that other projects (like the [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook or other Ansible playbooks) could benefit from them. This led to the **death of a few sibling playbooks** ([gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy), [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), [peertube-docker-ansible-deploy](https://github.com/spantaleev/peertube-docker-ansible-deploy), [vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy)), but brought life to something better, which supports all these services and more." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:25 +#: ../../../YEAR-IN-REVIEW.md:18 msgid "[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) is a new Ansible playbook that a few of us (matrix-docker-ansible-deploy contributors) have launched in 2023. It has quickly grown to supports [60+ services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md) and aims to do the same for [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) service hosting, as matrix-docker-ansible-deploy has done for Matrix - providing a clean and secure way to run a bunch of services in containers on a regular server (that is to say, without Kubernetes, etc.). Thanks to Traefik and Ansible role reuse, it's easy to host both mash-playbook services and matrix-docker-ansible-deploy services on the same server - see mash-playbook's [interoperability](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md) documentation page. If you've been looking for a holiday project or your New Year's Resolutions list contains \"self-hosting more services\", then you're welcome to give this new playbook a try and join its Matrix room ([#mash-playbook:devture.com](https://matrix.to/#/#mash-playbook:devture.com))." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:27 +#: ../../../YEAR-IN-REVIEW.md:20 msgid "Because many of the roles are now external to this playbook (defined in the [requirements.yml](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/da27655ef34999fa924bc0a5e641dbd9ba06f133/requirements.yml) file), running `make roles` (or better yet `just roles` via the [just tool](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#support-for-running-commands-via-just)) becomes a necessity each time one pulls playbook updates (`git pull`). Pulling external roles happens via the [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) command-line tool, but if available, the playbook would also use the much faster [agru](https://github.com/etkecc/agru) tool (developed by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) this year)." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:29 +#: ../../../YEAR-IN-REVIEW.md:22 msgid "With the internal (but important) details out of the way, we can now talk more about **new features that landed in matrix-docker-ansible-deploy in 2023**." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:31 +#: ../../../YEAR-IN-REVIEW.md:24 msgid "The following **new** **bridges** were added to the playbook in 2023:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:33 +#: ../../../YEAR-IN-REVIEW.md:26 msgid "(2023-01-11) [mautrix-slack](https://mau.dev/mautrix/slack), thanks to a PR by [Cody Neiman](https://github.com/xangelix) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#mautrix-slack-support))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:34 +#: ../../../YEAR-IN-REVIEW.md:27 msgid "(2023-07-21) [mautrix-gmessages](https://github.com/mautrix/gmessages), thanks to a PR by [Shreyas Ajjarapu](https://github.com/shreyasajj) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#mautrix-gmessages-support))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:35 +#: ../../../YEAR-IN-REVIEW.md:28 msgid "(2023-08-23) [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for Apple iMessage bridging (when combined with the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android phone), thanks to a PR by [Johan Swetzén](https://github.com/jswetzen)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:37 +#: ../../../YEAR-IN-REVIEW.md:30 msgid "This brings the total number of **[bridges that the playbook supports](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/docs/configuring-playbook.md#bridging-other-networks) up to 30**. There are alternative bridge implementations for various networks and protocols, so the number of \"unique bridged networks\" is surely much smaller." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:39 +#: ../../../YEAR-IN-REVIEW.md:32 msgid "A few other **major components and changes** landed in 2023:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:41 +#: ../../../YEAR-IN-REVIEW.md:34 msgid "(2023-02-10) The [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (successor to [Mjolnir](https://github.com/matrix-org/mjolnir)), thanks to a PR by [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#draupnir-moderation-tool-bot-support))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:42 +#: ../../../YEAR-IN-REVIEW.md:35 msgid "(2023-02-10) [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) to add Matrix Authentication Support to our Jitsi setup, thanks to a PR by [Jakob S.](https://github.com/jakicoll) from [zakk gGmbH](https://github.com/zakk-it) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-authentication-support-for-jitsi))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:43 +#: ../../../YEAR-IN-REVIEW.md:36 msgid "(2023-02-25) The [rageshake](https://github.com/matrix-org/rageshake) bug report server, thanks to a PR by [Benjamin Kampmann](https://github.com/gnunicorn) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#rageshake-support))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:44 +#: ../../../YEAR-IN-REVIEW.md:37 msgid "(2023-03-07) [Sliding Sync proxy](https://github.com/matrix-org/sliding-sync) (currently a necessary component for [Element X](https://element.io/labs/element-x) to work), thanks to: [Benjamin Kampmann](https://github.com/gnunicorn) and [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#sliding-sync-proxy-element-x-support))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:45 +#: ../../../YEAR-IN-REVIEW.md:38 msgid "(2023-03-12) synapse-auto-compressor to periodically and automatically run [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#synapse-auto-compressor-support))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:46 +#: ../../../YEAR-IN-REVIEW.md:39 msgid "(2023-07-17) [matrix-media-repo](https://github.com/turt2live/matrix-media-repo),  thanks to a PR by [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-media-repo-support))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:47 +#: ../../../YEAR-IN-REVIEW.md:40 msgid "(2023-08-31) [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client app (fork of [Element Web)](https://github.com/element-hq/element-web), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#schildichat-support))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:48 +#: ../../../YEAR-IN-REVIEW.md:41 msgid "(2023-10-18) Postgres parameters auto-tuning, thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#postgres-parameters-are-automatically-tuned-now))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:49 +#: ../../../YEAR-IN-REVIEW.md:42 msgid "(2023-10-23) Enabling federation of the room directory for Synapse (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#enabling-allow_public_rooms_over_federation-by-default-for-synapse))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:51 +#: ../../../YEAR-IN-REVIEW.md:44 msgid "The most recent change in the list above (Enabling federation of the room directory for Synapse) has been somewhat **controversial** as it goes against upstream defaults for Synapse. Nevertheless, we believe it **promotes the well-being of the Matrix Federation by improving room discovery**." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:53 +#: ../../../YEAR-IN-REVIEW.md:46 msgid "**Matrix Federation Stats** (containing the percentage of servers publishing their room directory publicly) are posted to [TWIM](https://matrix.org/category/this-week-in-matrix/) each week by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/). The number of servers which [currently published their room directory publicly](https://matrix.org/blog/2023/12/2/this-week-in-matrix-2023-12-22/#matrix-federation-stats) stands at `26.6%`, which is:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:55 +#: ../../../YEAR-IN-REVIEW.md:48 msgid "**2.4% more** than when it was when [first published to TWIM](https://matrix.org/blog/2023/11/03/this-week-in-matrix-2023-11-03/#matrix-federation-stats) (1 month earlier, in November)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:56 +#: ../../../YEAR-IN-REVIEW.md:49 msgid "likely about **15+% more** than from before we flipped the switch (in October)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:58 +#: ../../../YEAR-IN-REVIEW.md:51 msgid "Hopefully, Synapse defaults would also change the same way and we'd see the number of servers publicly listing their room directory grow faster." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:60 +#: ../../../YEAR-IN-REVIEW.md:53 msgid "With this configuration change in place, projects like [MatrixRooms.info](https://matrixrooms.info/) (made by [etke.cc](https://etke.cc/)) and potentially others in the future, can discover, index the metadata (room address, title, topic, number of users, etc.) and make public rooms browsable & searchable across the whole Matrix Federation. It'd be great if users joining Matrix could more easily find interesting communities that match their interests!" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:62 +#: ../../../YEAR-IN-REVIEW.md:55 msgid "On the **media side of things**, besides Jitsi getting better Matrix integration (via the aforementioned Matrix User Verification Service), we've also had some [coturn security tightening](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues) as well as [performance optimizations](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#coturn-can-now-use-host-networking) for configurations exposing lots of network ports." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:64 +#: ../../../YEAR-IN-REVIEW.md:57 msgid "[Element Call](https://github.com/element-hq/element-call) seems to have become a nice and polished product lately (as proclaimed in [The Matrix Holiday Update 2023](https://matrix.org/blog/2023/12/25/the-matrix-holiday-update-2023/)), so 2024 is likely the year we'll see support for it in the playbook. Element Call depends on the [LiveKit](https://livekit.io/) streaming server (which is also useful to developers even by itself), so the first step is likely to see LiveKit support in mash-playbook via a reusable Ansible role. Such a LiveKit Ansible role could later easily land in matrix-docker-ansible-deploy and an Element Call static website could be hooked to it." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:66 +#: ../../../YEAR-IN-REVIEW.md:59 msgid "Besides these highlights, there were many other relatively large changes announced in our [CHANGELOG](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md) and hundreds of other more minor (but still important) playbook changes that didn't get a mention." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:68 +#: ../../../YEAR-IN-REVIEW.md:61 msgid "We have **hundreds of contributors to thank for their hard work** on making Matrix self-hosting better for all of us! It should be noted that **support comes in many shapes**, not only in raw code commits and financial help (via [donations](https://liberapay.com/s.pantaleev) or using the [etke.cc managed Matrix hosting service](https://etke.cc/) which is based on matrix-docker-ansible-deploy). It also comes in the shape of code reviews, helping others with [issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues), reporting new issues, participating in our support room on Matrix ([#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)), etc. To everyone who has been there to make matrix-docker-ansible-deploy better in 2023, thank you! 🙇‍♂️" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:71 +#: ../../../YEAR-IN-REVIEW.md:64 msgid "2022" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:73 +#: ../../../YEAR-IN-REVIEW.md:66 msgid "For [matrix-docker-ansible-deploy](https://github.com/spantaleev/matrix-docker-ansible-deploy/), 2022 started with **breaking the** [**Synapse**](https://github.com/element-hq/synapse) **monopoly** by [adding support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#dendrite-support) for the [Dendrite](https://github.com/matrix-org/dendrite) Matrix homeserver in early January. This required various internal changes so that the [Ansible](https://www.ansible.com/) playbook would not be Synapse-centric anymore. This groundwork paved the way for continuing in this direction and we [added support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#conduit-support) for [Conduit](https://conduit.rs/) in August." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:75 +#: ../../../YEAR-IN-REVIEW.md:68 msgid "When it comes to the `matrix-docker-ansible-deploy` Ansible playbook, 2022 was the year of the non-Synapse homeserver implementation. In practice, none of these homeserver implementations seem ready for prime-time yet and there is no migration path when coming from Synapse. Having done our job of adding support for these alternative homeserver implementations, we can say that we're not getting in the way of future progress. It's time for the Dendrite developers to push harder (development-wise) and for the Synapse developers to take a well-deserved long (infinite) break, and we may get to see more people migrating away from Synapse in the next year(s)." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:77 +#: ../../../YEAR-IN-REVIEW.md:70 msgid "Support for the following new **bridges** was added:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:79 +#: ../../../YEAR-IN-REVIEW.md:72 msgid "[Postmoogle](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#postmoogle-email-bridge-support) for bi-directional email bridging, which supersedes my old and simplistic [Email2Matrix](https://github.com/devture/email2matrix) one-way bridge-bot" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:80 +#: ../../../YEAR-IN-REVIEW.md:73 msgid "[mautrix-discord](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#mautrix-discord-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:81 +#: ../../../YEAR-IN-REVIEW.md:74 msgid "[go-skype-bridge](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#go-skype-bridge-bridging-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:82 +#: ../../../YEAR-IN-REVIEW.md:75 msgid "[matrix-appservice-kakaotalk](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-appservice-kakaotalk-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:84 +#: ../../../YEAR-IN-REVIEW.md:77 msgid "Support for the following new **bots** was added:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:86 +#: ../../../YEAR-IN-REVIEW.md:79 msgid "[buscarron bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#buscarron-bot-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:87 +#: ../../../YEAR-IN-REVIEW.md:80 msgid "[Honoroit bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#honoroit-bot-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:88 +#: ../../../YEAR-IN-REVIEW.md:81 msgid "[matrix-registration-bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-registration-bot-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:89 +#: ../../../YEAR-IN-REVIEW.md:82 msgid "[matrix-hookshot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-hookshot-bridging-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:90 +#: ../../../YEAR-IN-REVIEW.md:83 msgid "[maubot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#maubot-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:92 +#: ../../../YEAR-IN-REVIEW.md:85 msgid "Support for the following new **components and services** was added:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:94 +#: ../../../YEAR-IN-REVIEW.md:87 msgid "[BorgBackup](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#borg-backup-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:95 +#: ../../../YEAR-IN-REVIEW.md:88 msgid "[Cactus Comments](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cactus-comments-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:96 +#: ../../../YEAR-IN-REVIEW.md:89 msgid "[Cinny](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cinny-support) client support" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:97 +#: ../../../YEAR-IN-REVIEW.md:90 msgid "[ntfy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#ntfy-push-notifications-support) notifications" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:98 +#: ../../../YEAR-IN-REVIEW.md:91 msgid "[matrix-ldap-registration-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-ldap-registration-proxy-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:99 +#: ../../../YEAR-IN-REVIEW.md:92 msgid "[matrix\\_encryption\\_disabler support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix_encryption_disabler-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:100 +#: ../../../YEAR-IN-REVIEW.md:93 msgid "[synapse-s3-storage-provider](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-s3-storage-provider-support) to stop the Synapse media store from being a scalability problem. This brought along [another feature](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-container-image-customization-support) - an easier way to customize the Synapse container image without having to fork and self-build all of it from scratch" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:102 +#: ../../../YEAR-IN-REVIEW.md:95 msgid "Besides these major user-visible changes, a lot of work also happened **under the hood**:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:104 +#: ../../../YEAR-IN-REVIEW.md:97 msgid "we made [major improvements to Synapse workers](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#potential-backward-compatibility-break-major-improvements-to-synapse-workers) - adding support for stream writers and for running multiple workers of various kinds (federation senders, pushers, background task processing workers, etc.)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:105 +#: ../../../YEAR-IN-REVIEW.md:98 msgid "we [improved the compatibility of (Synapse + workers) with the rest of the playbook](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#backward-compatibility-break-changing-how-reverse-proxying-to-synapse-works---now-via-a-matrix-synapse-reverse-proxy-companion-service) by introducing a new `matrix-synapse-reverse-proxy-companion-service` service" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:106 +#: ../../../YEAR-IN-REVIEW.md:99 msgid "we started [splitting various Ansible roles out of the Matrix playbook and into independent roles](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#the-playbook-now-uses-external-roles-for-some-things) (e.g. `matrix-postgres` -> [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres)), which could be included in other Ansible playbooks. In fact, these roles already power a few **interesting other sibling playbooks**:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:107 +#: ../../../YEAR-IN-REVIEW.md:100 msgid "[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy), for deploying a [Gitea](https://gitea.io/) (self-hosted [Git](https://git-scm.com/) service) server" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:108 +#: ../../../YEAR-IN-REVIEW.md:101 msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), for deploying a [Nextcloud](https://nextcloud.com/) groupware server" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:109 +#: ../../../YEAR-IN-REVIEW.md:102 msgid "[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy), for deploying a [Vaultwarden](https://github.com/dani-garcia/vaultwarden) password manager server (unofficial [Bitwarden](https://bitwarden.com/) compatible server)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:111 +#: ../../../YEAR-IN-REVIEW.md:104 msgid "These sibling playbooks co-exist nicely with one another due to using [Traefik](https://traefik.io/) for reverse-proxying, instead of trying to overtake the whole server by running their own [nginx](https://nginx.org/) reverse-proxy. Hopefully soon, the Matrix playbook will follow suit and be powered by Traefik by default." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:113 +#: ../../../YEAR-IN-REVIEW.md:106 msgid "Last, but not least, to optimize our [etke.cc managed Matrix hosting service](https://etke.cc/)'s performance (but also individual Ansible playbook runs for people self-hosting by themselves using the playbook), we've [improved playbook runtime 2-5x](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) by employing various Ansible tricks." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/ansible.po b/i18n/locales/bg/LC_MESSAGES/docs/ansible.po index 98c385622..c4b38de2d 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/ansible.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/ansible.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,176 +19,164 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/ansible.md:11 -msgid "Using Ansible for the playbook" +#: ../../../docs/ansible.md:2 +msgid "Running this playbook" msgstr "" -#: ../../../docs/ansible.md:13 +#: ../../../docs/ansible.md:4 msgid "This playbook is meant to be run using [Ansible](https://www.ansible.com/)." msgstr "" -#: ../../../docs/ansible.md:15 +#: ../../../docs/ansible.md:6 msgid "Ansible typically runs on your local computer and carries out tasks on a remote server. If your local computer cannot run Ansible, you can also run Ansible on some server somewhere (including the server you wish to install to)." msgstr "" -#: ../../../docs/ansible.md:17 +#: ../../../docs/ansible.md:8 msgid "Supported Ansible versions" msgstr "" -#: ../../../docs/ansible.md:19 +#: ../../../docs/ansible.md:10 msgid "To manually check which version of Ansible you're on, run: `ansible --version`." msgstr "" -#: ../../../docs/ansible.md:21 +#: ../../../docs/ansible.md:12 msgid "For the **best experience**, we recommend getting the **latest version of Ansible available**." msgstr "" -#: ../../../docs/ansible.md:23 -msgid "We're not sure what's the minimum version of Ansible that can run this playbook successfully. The lowest version that we suspect (on 2025-09-03) to be working fine is: `ansible-core` (`2.15.1`)." +#: ../../../docs/ansible.md:14 +msgid "We're not sure what's the minimum version of Ansible that can run this playbook successfully. The lowest version that we've confirmed (on 2022-11-26) to be working fine is: `ansible-core` (`2.11.7`) combined with `ansible` (`4.10.0`)." msgstr "" -#: ../../../docs/ansible.md:25 +#: ../../../docs/ansible.md:16 msgid "If your distro ships with an Ansible version older than this, you may run into issues. Consider [Upgrading Ansible](#upgrading-ansible) or [using Ansible via Docker](#using-ansible-via-docker)." msgstr "" -#: ../../../docs/ansible.md:27 -msgid "[!WARNING] One reason for the version requirement being as such is that the playbook by default installs Docker for you using [this Docker role](https://github.com/geerlingguy/ansible-role-docker) which [has a hard requirement on Ansible v2.15.1](https://github.com/geerlingguy/ansible-role-docker/commit/7f44a1d9ad8132819ea9852918bca5dab8757cd0). If you install Docker yourself another way, you can tell the playbook to skip running this role (by adding `matrix_playbook_docker_installation_enabled: false` to your `vars.yml` configuration). It may then be possible to get the playbook running on an older version of Ansible. Still, this is a complication and your mileage may vary. We recommend [upgrading Ansible](#upgrading-ansible) instead of going into uncharted territory." -msgstr "" - -#: ../../../docs/ansible.md:30 +#: ../../../docs/ansible.md:18 msgid "Upgrading Ansible" msgstr "" -#: ../../../docs/ansible.md:32 +#: ../../../docs/ansible.md:20 msgid "Depending on your distribution, you may be able to upgrade Ansible in a few different ways:" msgstr "" -#: ../../../docs/ansible.md:34 +#: ../../../docs/ansible.md:22 msgid "by using an additional repository (PPA, etc.), which provides newer Ansible versions. See instructions for [CentOS](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-rhel-centos-or-fedora), [Debian](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-debian), or [Ubuntu](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-ubuntu) on the Ansible website." msgstr "" -#: ../../../docs/ansible.md:36 +#: ../../../docs/ansible.md:24 msgid "by removing the Ansible package (`yum remove ansible` or `apt-get remove ansible`) and installing via [pip](https://pip.pypa.io/en/stable/installation/) (`pip install ansible`)." msgstr "" -#: ../../../docs/ansible.md:38 +#: ../../../docs/ansible.md:26 msgid "If using the `pip` method, do note that the `ansible-playbook` binary may not be on the `$PATH` (https://linuxconfig.org/linux-path-environment-variable), but in some more special location like `/usr/local/bin/ansible-playbook`. You may need to invoke it using the full path." msgstr "" -#: ../../../docs/ansible.md:40 +#: ../../../docs/ansible.md:28 msgid "**Note**: Both of the above methods are a bad way to run system software such as Ansible. If you find yourself needing to resort to such hacks, please consider reporting a bug to your distribution and/or switching to a sane distribution, which provides up-to-date software." msgstr "" -#: ../../../docs/ansible.md:42 +#: ../../../docs/ansible.md:30 msgid "Using Ansible via Docker" msgstr "" -#: ../../../docs/ansible.md:44 -msgid "Alternatively, you can run Ansible inside a Docker container (powered by the [ghcr.io/devture/ansible](https://github.com/devture/docker-ansible/pkgs/container/ansible) Docker image)." -msgstr "" - -#: ../../../docs/ansible.md:46 -msgid "This ensures that:" -msgstr "" - -#: ../../../docs/ansible.md:48 -msgid "you're using a very recent Ansible version, which is less likely to be incompatible with the playbook" +#: ../../../docs/ansible.md:32 +msgid "Alternatively, you can run Ansible inside a Docker container (powered by the [devture/ansible](https://hub.docker.com/r/devture/ansible/) Docker image)." msgstr "" -#: ../../../docs/ansible.md:49 -msgid "you also get access to the [agru](https://github.com/etkecc/agru) tool for quicker Ansible role installation (when running `just roles`) compared to `ansible-galaxy`" +#: ../../../docs/ansible.md:34 +msgid "This ensures that you're using a very recent Ansible version, which is less likely to be incompatible with the playbook." msgstr "" -#: ../../../docs/ansible.md:51 +#: ../../../docs/ansible.md:36 msgid "You can either [run Ansible in a container on the Matrix server itself](#running-ansible-in-a-container-on-the-matrix-server-itself) or [run Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)." msgstr "" -#: ../../../docs/ansible.md:53 +#: ../../../docs/ansible.md:38 msgid "Running Ansible in a container on the Matrix server itself" msgstr "" -#: ../../../docs/ansible.md:55 +#: ../../../docs/ansible.md:40 msgid "To run Ansible in a (Docker) container on the Matrix server itself, you need to have a working Docker installation. Docker is normally installed by the playbook, so this may be a bit of a chicken and egg problem. To solve it:" msgstr "" -#: ../../../docs/ansible.md:57 +#: ../../../docs/ansible.md:42 msgid "you **either** need to install Docker manually first. Follow [the upstream instructions](https://docs.docker.com/engine/install/) for your distribution and consider setting `matrix_playbook_docker_installation_enabled: false` in your `vars.yml` file, to prevent the playbook from installing Docker" msgstr "" -#: ../../../docs/ansible.md:58 +#: ../../../docs/ansible.md:43 msgid "**or** you need to run the playbook in another way (e.g. [Running Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)) at least the first time around" msgstr "" -#: ../../../docs/ansible.md:60 +#: ../../../docs/ansible.md:45 msgid "Once you have a working Docker installation on the server, **clone the playbook** somewhere on the server and configure it as per usual (`inventory/hosts`, `inventory/host_vars/…`, etc.), as described in [configuring the playbook](configuring-playbook.md)." msgstr "" -#: ../../../docs/ansible.md:62 +#: ../../../docs/ansible.md:47 msgid "You would then need to add `ansible_connection=community.docker.nsenter` to the host line in `inventory/hosts`. This tells Ansible to connect to the \"remote\" machine by switching Linux namespaces with [nsenter](https://man7.org/linux/man-pages/man1/nsenter.1.html), instead of using SSH." msgstr "" -#: ../../../docs/ansible.md:64 -msgid "Alternatively, you can leave your `inventory/hosts` as is and specify the connection type in **each** `ansible-playbook` call you do later, like this: `just install-all --connection=community.docker.nsenter` (or `ansible-playbook --connection=community.docker.nsenter …`)." +#: ../../../docs/ansible.md:49 +msgid "Alternatively, you can leave your `inventory/hosts` as is and specify the connection type in **each** `ansible-playbook` call you do later, like this: `ansible-playbook --connection=community.docker.nsenter …`" msgstr "" -#: ../../../docs/ansible.md:66 ../../../docs/ansible.md:88 +#: ../../../docs/ansible.md:51 ../../../docs/ansible.md:71 msgid "Run this from the playbook's directory:" msgstr "" -#: ../../../docs/ansible.md:80 ../../../docs/ansible.md:103 +#: ../../../docs/ansible.md:63 ../../../docs/ansible.md:84 msgid "Once you execute the above command, you'll be dropped into a `/work` directory inside a Docker container. The `/work` directory contains the playbook's code." msgstr "" -#: ../../../docs/ansible.md:82 ../../../docs/ansible.md:105 +#: ../../../docs/ansible.md:65 ../../../docs/ansible.md:86 msgid "First, consider running `git config --global --add safe.directory /work` to [resolve directory ownership issues](#resolve-directory-ownership-issues)." msgstr "" -#: ../../../docs/ansible.md:84 -msgid "Finally, you can execute `just` or `ansible-playbook …` (e.g. `ansible-playbook --connection=community.docker.nsenter …`) commands as per normal now." +#: ../../../docs/ansible.md:67 +msgid "Finally, you can execute `ansible-playbook …` (or `ansible-playbook --connection=community.docker.nsenter …`) commands as per normal now." msgstr "" -#: ../../../docs/ansible.md:86 +#: ../../../docs/ansible.md:69 msgid "Running Ansible in a container on another computer (not the Matrix server)" msgstr "" -#: ../../../docs/ansible.md:101 -msgid "The above command tries to mount an SSH key (`$HOME/.ssh/id_ed25519`) into the container (at `/root/.ssh/id_ed25519`). If your SSH key is at a different path (not in `$HOME/.ssh/id_ed25519`), adjust that part." +#: ../../../docs/ansible.md:82 +msgid "The above command tries to mount an SSH key (`$HOME/.ssh/id_rsa`) into the container (at `/root/.ssh/id_rsa`). If your SSH key is at a different path (not in `$HOME/.ssh/id_rsa`), adjust that part." msgstr "" -#: ../../../docs/ansible.md:107 -msgid "Finally, you execute `just` or `ansible-playbook …` commands as per normal now." +#: ../../../docs/ansible.md:88 +msgid "Finally, you execute `ansible-playbook …` commands as per normal now." msgstr "" -#: ../../../docs/ansible.md:109 +#: ../../../docs/ansible.md:90 msgid "If you don't use SSH keys for authentication" msgstr "" -#: ../../../docs/ansible.md:111 -msgid "If you don't use SSH keys for authentication, simply remove that whole line (`--mount type=bind,src$HOME/.ssh/id_ed25519,dst=/root/.ssh/id_ed25519,ro`)." +#: ../../../docs/ansible.md:92 +msgid "If you don't use SSH keys for authentication, simply remove that whole line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`)." msgstr "" -#: ../../../docs/ansible.md:113 +#: ../../../docs/ansible.md:94 msgid "To authenticate at your server using a password, you need to add a package. So, when you are in the shell of the ansible docker container (the previously used `docker run -it …` command), run:" msgstr "" -#: ../../../docs/ansible.md:119 -msgid "Then, to be asked for the password whenever running an `ansible-playbook` command add `--ask-pass` to the arguments of the command." +#: ../../../docs/ansible.md:100 +msgid "Then, to be asked for the password whenever running an `ansible-playbook` command add `--ask-pass` to the arguments of the command." msgstr "" -#: ../../../docs/ansible.md:121 +#: ../../../docs/ansible.md:102 msgid "Resolve directory ownership issues" msgstr "" -#: ../../../docs/ansible.md:123 -msgid "Because you're `root` in the container running Ansible and this likely differs from the owner (your regular user account) of the playbook directory outside of the container, certain playbook features which use `git` locally may report warnings such as:" +#: ../../../docs/ansible.md:104 +msgid "Because you're `root` in the container running Ansible and this likely differs fom the owner (your regular user account) of the playbook directory outside of the container, certain playbook features which use `git` locally may report warnings such as:" msgstr "" -#: ../../../docs/ansible.md:125 +#: ../../../docs/ansible.md:106 msgid "fatal: unsafe repository ('/work' is owned by someone else) To add an exception for this directory, call: git config --global --add safe.directory /work" msgstr "" -#: ../../../docs/ansible.md:129 +#: ../../../docs/ansible.md:110 msgid "These errors can be resolved by making `git` trust the playbook directory by running `git config --global --add safe.directory /work`" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-dns.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-dns.po index 751c4925e..11c89fd6e 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-dns.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-dns.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,25 +19,25 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-dns.md:18 -msgid "Configuring DNS settings" +#: ../../../docs/configuring-dns.md:1 +msgid "Configuring your DNS settings" msgstr "" -#: ../../../docs/configuring-dns.md:20 -msgid "[Prerequisites](prerequisites.md) > Configuring DNS settings > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)" +#: ../../../docs/configuring-dns.md:3 +msgid "[Prerequisites](prerequisites.md) > Configuring your DNS settings > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)" msgstr "" -#: ../../../docs/configuring-dns.md:22 +#: ../../../docs/configuring-dns.md:5 msgid "To set up Matrix on your domain, you'd need to do some DNS configuration." msgstr "" -#: ../../../docs/configuring-dns.md:24 +#: ../../../docs/configuring-dns.md:7 msgid "DNS settings for services enabled by default" msgstr "" -#: ../../../docs/configuring-dns.md:26 +#: ../../../docs/configuring-dns.md:9 msgid "To serve the base domain (`example.com`) and [Element Web](configuring-playbook-client-element-web.md) with the default subdomain, adjust DNS records as below." msgstr "" @@ -78,15 +78,7 @@ msgid "-" msgstr "" #: ../../../docs/configuring-dns.md -msgid "`matrix-server-IPv4`" -msgstr "" - -#: ../../../docs/configuring-dns.md -msgid "AAAA" -msgstr "" - -#: ../../../docs/configuring-dns.md -msgid "`matrix-server-IPv6`" +msgid "`matrix-server-IP`" msgstr "" #: ../../../docs/configuring-dns.md @@ -101,62 +93,58 @@ msgstr "" msgid "`matrix.example.com`" msgstr "" -#: ../../../docs/configuring-dns.md:34 -msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IPv4/IPv6 address." +#: ../../../docs/configuring-dns.md:16 +msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)." msgstr "" -#: ../../../docs/configuring-dns.md:36 -msgid "If you don't have IPv6 connectivity yet, you can skip the `AAAA` record. For more details about IPv6, see the [Configuring IPv6](./configuring-ipv6.md) documentation page." -msgstr "" - -#: ../../../docs/configuring-dns.md:38 +#: ../../../docs/configuring-dns.md:18 msgid "The `element.example.com` subdomain is necessary, because this playbook installs the [Element Web](https://github.com/element-hq/element-web) client for you by default. If you'd rather instruct the playbook not to install Element Web (`matrix_client_element_enabled: false` when [Configuring the playbook](configuring-playbook.md) later), feel free to skip the `element.example.com` DNS record." msgstr "" -#: ../../../docs/configuring-dns.md:40 +#: ../../../docs/configuring-dns.md:20 msgid "Be mindful as to how long it will take for the DNS records to propagate." msgstr "" -#: ../../../docs/configuring-dns.md:42 +#: ../../../docs/configuring-dns.md:22 msgid "**Note**: if you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\". Otherwise, fetching certificates will fail." msgstr "" -#: ../../../docs/configuring-dns.md:44 +#: ../../../docs/configuring-dns.md:24 msgid "DNS setting for server delegation (optional)" msgstr "" -#: ../../../docs/configuring-dns.md:46 +#: ../../../docs/configuring-dns.md:26 msgid "In the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com`." msgstr "" -#: ../../../docs/configuring-dns.md:48 +#: ../../../docs/configuring-dns.md:28 msgid "To use such an ID, you don't need to install anything on the actual `example.com` server. Instead, you need to instruct the Matrix network that Matrix services for `example.com` are redirected over to `matrix.example.com`. This redirection is also known as \"delegation\"." msgstr "" -#: ../../../docs/configuring-dns.md:50 +#: ../../../docs/configuring-dns.md:30 msgid "As we discuss in [Server Delegation](howto-server-delegation.md), server delegation can be configured in either of these ways:" msgstr "" -#: ../../../docs/configuring-dns.md:52 +#: ../../../docs/configuring-dns.md:32 msgid "Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)" msgstr "" -#: ../../../docs/configuring-dns.md:53 +#: ../../../docs/configuring-dns.md:33 msgid "Setting up a `_matrix._tcp` DNS SRV record" msgstr "" -#: ../../../docs/configuring-dns.md:55 +#: ../../../docs/configuring-dns.md:35 msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file, instead of using a DNS SRV record." msgstr "" -#: ../../../docs/configuring-dns.md:57 +#: ../../../docs/configuring-dns.md:37 msgid "If you choose the recommended method (file-based delegation), you do not need to configure the DNS record to enable server delegation. You will need to add a necessary configuration later, when you [finalize the installation](installing.md#finalize-the-installation) after installing and starting Matrix services." msgstr "" -#: ../../../docs/configuring-dns.md:59 +#: ../../../docs/configuring-dns.md:39 msgid "On the other hand, if you choose this method (setting up a DNS SRV record), you need to configure the additional DNS record as well as adjust SSL certificate handling. Take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)" msgstr "" -#: ../../../docs/configuring-dns.md:63 +#: ../../../docs/configuring-dns.md:43 msgid "[▶️](getting-the-playbook.md) When you're done with the DNS configuration and ready to proceed, continue with [Getting the playbook](getting-the-playbook.md)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-ipv6.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-ipv6.po deleted file mode 100644 index 652389147..000000000 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-ipv6.po +++ /dev/null @@ -1,367 +0,0 @@ -# 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 , 2026. -# -#, fuzzy -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" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: bg\n" -"Language-Team: bg \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-ipv6.md:6 -msgid "Configuring IPv6" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:8 -msgid "Since 2025-03-08, the [default example configuration](../examples/vars.yml) for the playbook recommends enabling [IPv6](https://en.wikipedia.org/wiki/IPv6) support for Docker's container networks." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:10 -msgid "**If you have IPv6 support on your server/network** (see [How do I check if my server has IPv6 connectivity?](#how-do-i-check-if-my-server-has-ipv6-connectivity)), then [enabling IPv6 support for the playbook](#enabling-ipv6-support-for-the-playbook) would give you:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:12 -msgid "📥 incoming IPv6 connectivity to the server via the server's IPv6 address/addresses (containers won't have their own individual publicly accessible IPs)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:13 -msgid "📤 outgoing IPv6 connectivity from the server via the server's IPv6 address/addresses (containers won't exit via their own individual IPv6 address)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:14 -msgid "🔄 IPv6 connectivity for cross-container communication" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:16 -msgid "**If you still don't have IPv6 support on your server/network**, then enabling IPv6 support for the playbook will only enable IPv6 connectivity for cross-container communication and shouldn't affect your server's incoming/outgoing communication. You may also be interested in reading if [there's a performance penalty to enabling IPv6 if the server/network doesn't support IPv6 connectivity?](#is-there-a-performance-penalty-to-enabling-ipv6-if-the-server-network-doesn-t-support-ipv6-connectivity)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:18 -msgid "As such, **we recommend that you follow the default example configuration and leave IPv6 support for Docker enabled in all cases**." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:20 -msgid "Enabling IPv6 consists of 2 steps:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:22 -msgid "[Enabling IPv6 support for the playbook](#enabling-ipv6-support-for-the-playbook)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:23 -msgid "[Configuring DNS records for IPv6](#configuring-dns-records-for-ipv6)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:25 -msgid "💡 If you've followed a recent version of our documentation, you would have already done these steps, so there's nothing else to do." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:27 -msgid "Enabling IPv6 support for the playbook" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:29 -msgid "You can enable IPv6 support for all components' Docker container networks by using the following `vars.yml` configuration:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:50 -msgid "Doing this:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:52 -msgid "all container networks will be IPv6-enabled" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:54 -msgid "NAT66 will be used, so that:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:55 -msgid "containers will get [Unique Local Addresses (ULA)](https://en.wikipedia.org/wiki/Unique_local_address)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:56 -msgid "the outgoing IPv6 address for containers will be the same as the one on the server" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:57 -msgid "traffic destined for the IPv6 address of the server will be forwarded to the containers that handle (and publish) that specific port" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:59 -msgid "[!WARNING] Without enabling this and assuming you have IPv6 `AAAA` DNS records pointing to the server (see [Configuring DNS records for IPv6](#configuring-dns-records-for-ipv6)), IPv6 traffic will still be handled, but NAT64 will be used instead of NAT66. As such, containers will only have an IPv4 address and all IPv6 traffic that reaches them will seem to originate from a local IP. Containers also won't be able to make outgoing (even cross-container) IPv6 requests." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:63 -msgid "To confirm connectivity, see the following other resources:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:65 -msgid "[How do I check if my server has IPv6 connectivity?](#how-do-i-check-if-my-server-has-ipv6-connectivity)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:66 -msgid "[How do I check outgoing IPv6 connectivity for containers?](#how-do-i-check-outgoing-ipv6-connectivity-for-containers)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:67 -msgid "[How do I check incoming IPv6 connectivity for containers?](#how-do-i-check-incoming-ipv6-connectivity-for-containers)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:68 -msgid "[How do I confirm if my container networks are IPv6-enabled?](#how-do-i-confirm-if-my-container-networks-are-ipv6-enabled)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:69 -msgid "Ensure that the [Federation Tester](https://federationtester.matrix.org/) reports that your server is reachable over IPv6." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:71 -msgid "Configuring DNS records for IPv6" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:73 -msgid "[Enabling IPv6 support for the playbook](#enabling-ipv6-support-for-the-playbook) tells you how to prepare for IPv6 on the container (Docker) side." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:75 -msgid "For full public IPv6 connectivity (and not just IPv6 connectivity for containers inside the container networks) you also need to **ensure that your domain names** (e.g. `matrix.example.com` and others) have IPv6 (`AAAA`) DNS records pointing to the server's IPv6 address." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:77 -msgid "Also see the [Configuring DNS settings](configuring-dns.md) documentation page for more details." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:79 -msgid "A note about old Docker" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:81 -msgid "With our [default example configuration](../examples/vars.yml), the playbook manages Docker for you and installs a modern-enough version." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:83 -msgid "Docker versions newer than 27.0.1 enable IPv6 integration at the Docker daemon level out of the box. This still requires that networks are created with IPv6 support as described in the [Enabling IPv6 support for the playbook](#enabling-ipv6-support-for-the-playbook) section above." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:85 -msgid "**If you're on an old Docker version** (Docker 27.0.0 or older) for some reason, it's likely that your Docker installation is not enabled for IPv6 at all. In such a case:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:87 -msgid "if Docker is managed by the playbook, you can tell it to force-enable IPv6 via `devture_systemd_docker_base_ipv6_daemon_options_changing_enabled: true`" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:89 -#, python-brace-format -msgid "if Docker is managed by you manually, you can add `{\"experimental\": true, \"ip6tables\": true}` to the Docker daemon options and restart the Docker service (`docker.service`)." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:91 -msgid "Frequently Asked Questions" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:93 -msgid "How do I check if my server has IPv6 connectivity?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:95 -msgid "With curl" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:97 -msgid "You can run `curl https://icanhazip.com` and see if it returns an [IPv6 address](https://en.wikipedia.org/wiki/IPv6_address) (an address with `:` characters in it, like `2001:db8:1234:5678::1`). If it does, then your server has IPv6 connectivity and prefers it over using IPv4. This is common." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:99 -msgid "If you see an IPv4 address instead (e.g. `1.2.3.4`), it may be that your server prefers IPv4 over IPv6 or that your network does not support IPv6. You can try forcing `curl` to use IPv6 by running `curl -6 https://icanhazip.com` and see if it returns an IPv6 address." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:101 -msgid "With other network utilities" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:103 -msgid "You can run `ip -6 addr` to see if you have any IPv6 addresses assigned to your server, besides the link-local (`fe80::*`) addresses that everyone has (unless they have force-disabled IPv6 support on their system)." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:105 -msgid "If you do have an IPv6 address, it's still worth [using curl](#with-curl) to confirm that your server can successfully make outgoing requests over IPv6." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:107 -msgid "What does the `devture_systemd_docker_base_ipv6_enabled` setting actually do?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:109 -msgid "The `devture_systemd_docker_base_ipv6_enabled` setting controls whether container networks will be created with IPv6 support." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:111 -msgid "Changing this setting subsequently requires manual work (deleting all container networks). See [I've changed the `devture_systemd_docker_base_ipv6_enabled` setting, but it doesn't seem to have any effect](#i-ve-changed-the-devture_systemd_docker_base_ipv6_enabled-setting-but-it-doesn-t-seem-to-have-any-effect)." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:114 -msgid "I've changed the `devture_systemd_docker_base_ipv6_enabled` setting, but it doesn't seem to have any effect." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:116 -msgid "If you're using an older Docker version (Docker 27.0.0 or older), see [A note about old Docker](#a-note-about-old-docker)." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:118 -msgid "If you've previously installed with one `devture_systemd_docker_base_ipv6_enabled` value and then changed it to another, you need to:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:120 -msgid "stop all services (`just stop-all`)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:121 -msgid "delete all container networks on the server: `docker network rm $(docker network ls -q)`" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:122 -msgid "re-run the playbook fully: `just install-all`" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:124 -msgid "How do I confirm if my container networks are IPv6-enabled?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:126 -msgid "You can list container networks by running `docker network ls` on the server." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:128 -msgid "For each container network (e.g. `matrix-homeserver`), you can check if it has IPv6 connectivity by running a command like this: `docker network inspect matrix-homeserver`." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:130 -msgid "Ensure that there's an IPv6 subnet/gateway in the `IPAM.Config` section. If yes, you may wish to proceed with [How do I check outgoing IPv6 connectivity for containers?](#how-do-i-check-outgoing-ipv6-connectivity-for-containers)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:132 -msgid "If there's no IPv6 subnet/gateway in the `IPAM.Config` section, this container network was not created with IPv6 support. See [I've changed the `devture_systemd_docker_base_ipv6_enabled` setting, but it doesn't seem to have any effect](#i-ve-changed-the-devture_systemd_docker_base_ipv6_enabled-setting-but-it-doesn-t-seem-to-have-any-effect)." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:135 -msgid "How do I check outgoing IPv6 connectivity for containers?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:141 -msgid "💡 This one-off container is connected to the `matrix-homeserver` container network, not to the default Docker bridge network. The default Docker `bridge` network does not have IPv6 connectivity by default (yet) and is not influenced by the `devture_systemd_docker_base_ipv6_enabled` setting, so using that network (by omitting `--network=..` from the command above) will not show an IPv6 address" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:143 -msgid "✅ If this command returns an IPv6 address, you're all good." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:145 -msgid "❌ If this command doesn't return an IPv6 address, it may be that:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:147 -msgid "your container network does not have IPv6 connectivity. See [How do I confirm if my container networks are IPv6-enabled?](#how-do-i-confirm-if-my-container-networks-are-ipv6-enabled) for more details." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:149 -msgid "your server does not have IPv6 connectivity. See [How do I check if my server has IPv6 connectivity?](#how-do-i-check-if-my-server-has-ipv6-connectivity) for more details. If you do have IPv6 connectivity, then the issue is with Docker's IPv6 configuration. Otherwise, you need to check your server's network configuration/firewall/routing and get back to configuring the playbook later on." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:151 -msgid "How do I check incoming IPv6 connectivity for containers?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:153 -msgid "Only containers that publish ports will be exposed (reachable) publicly on the server's own IPv6 address. Containers will not get their own individual public IPv6 address." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:155 -msgid "For this playbook, a commonly exposed container is the Traefik reverse-proxy container (unless [you're using your own webserver](./configuring-playbook-own-webserver.md))." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:157 -msgid "You can either do something like `curl -6 https://matrix.example.com` from an IPv6-enabled host (including the server itself) and see if it works." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:159 -msgid "An alternative is to use the [IPv6 Port Checker](https://port.tools/port-checker-ipv6/) with a hostname of `matrix.example.com` and a port of `443`." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:161 -msgid "💡 Trying to connect to `matrix.example.com` via IPv6 requires that you have already [configured the DNS records for IPv6](#configuring-dns-records-for-ipv6) as described above. If you wish to eliminate DNS as a potential issue, you can also try connecting to the server's own IPv6 address directly: `curl -6 -H 'Host: matrix.example.com' https://[2001:db8:1234:5678::1]` (we pass a `Host` header to tell Traefik which host we'd like it to serve)." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:163 -msgid "Why enable IPv6 if my network doesn't support it yet?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:165 -msgid "Because when your network does get support for IPv6 later on (even if that's 5 years away), you won't have to change anything besides [configuring the DNS records for IPv6](#configuring-dns-records-for-ipv6)." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:167 -msgid "Can I use a custom subnet for IPv6?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:169 -msgid "Not easily." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:171 -msgid "The playbook and the various roles only support passing an `enable_ipv6` flag (`true` or `false` value depending on the `devture_systemd_docker_base_ipv6_enabled` Ansible variable) when creating the Docker container networks." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:173 -msgid "There's no support for passing a custom subnet for IPv4 and IPv6. We let Docker auto-generate the subnets for us." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:175 -msgid "You can either create a Pull Request that adds support for this to the various playbook roles, or you can manually recreate the networks from the command-line (e.g. `docker network rm matrix-homeserver && docker network create --ipv6 --subnet=2001:db8:1234:5678::/64 matrix-homeserver`)." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:177 -msgid "Can I use Global Unicast Addresses (GUA) for IPv6?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:179 -msgid "No. You cannot have GUA addresses where each container is individually addressable over the public internet." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:181 -msgid "The playbook only supports NAT66, which should be good enough for most use cases." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:183 -msgid "Having containers get IPv6 addresses from your own GUA subnet requires complex configuration (ndp-proxy, etc.) and is not supported." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:185 -msgid "You may find [this Reddit post](https://www.reddit.com/r/ipv6/comments/1alpzmb/comment/kphpw11/) interesting." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:187 -msgid "Is there a performance penalty to enabling IPv6 if the server/network doesn't support IPv6 connectivity?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:189 -msgid "Probably a tiny one, as services may try to make (unsuccessful) outgoing requests over IPv6." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:191 -msgid "In practice, it's probably negligible." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po index b47e7633f..03bd88dfa 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,176 +19,184 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:9 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:1 msgid "Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver (optional)" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:11 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:3 msgid "The playbook can install and configure the [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver) service for you. It's a [client](https://prometheus.io/docs/alerting/latest/clients/) for Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/), allowing you to deliver alerts to Matrix rooms." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:13 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:5 msgid "See the project's [documentation](https://github.com/metio/matrix-alertmanager-receiver/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:15 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:7 msgid "This service is meant to be used with an external [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) instance. It's **not** meant to be integrated with the [Prometheus & Grafana stack](./configuring-playbook-prometheus-grafana.md) installed by this playbook, because the Alertmanager component is not installed by it." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:17 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:9 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:19 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:11 msgid "Register the bot account" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:21 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:13 msgid "This service uses a bot (with a username specified in `matrix_alertmanager_receiver_config_matrix_user_id_localpart`) for delivering messages." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:23 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:15 msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:25 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:17 msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:27 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:19 msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:33 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:25 msgid "Obtain an access token" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:35 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:27 msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:37 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:29 msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:40 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:32 msgid "Join to rooms as the bot manually" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:42 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:34 msgid "ℹ️ **This bot does not accept room invitations automatically**. To deliver messages to rooms, the bot must be joined to all rooms manually." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:44 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:36 msgid "For each new room you would like the bot to deliver alerts to, invite the bot to the room." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:46 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:38 msgid "Then, log in as the bot using any Matrix client of your choosing, accept the room invitation from the bot's account, and log out." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:48 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:40 msgid "Adjusting DNS records (optional)" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:50 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:42 msgid "By default, this playbook installs matrix-alertmanager-receiver on the `matrix.` subdomain, at the `/matrix-alertmanager-receiver` path (https://matrix.example.com/matrix-alertmanager-receiver). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:52 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:44 msgid "If you wish to adjust it, see the section [below](#adjusting-the-matrix-alertmanager-receiver-url-optional) for details about DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:54 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:46 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:56 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:48 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:77 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:69 msgid "Adjusting the matrix-alertmanager-receiver URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:79 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:71 msgid "By tweaking the `matrix_alertmanager_receiver_hostname` and `matrix_alertmanager_receiver_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:81 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:73 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:89 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:81 msgid "If you've changed the default hostname, you may need to create a CNAME record for the matrix-alertmanager-receiver domain (`alertmanager.example.com`), which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:91 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:83 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:93 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:85 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:95 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:87 msgid "There are some additional things you may wish to configure about the component." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:97 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:89 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:99 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:91 msgid "`roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:100 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:92 msgid "`roles/custom/matrix-alertmanager-receiver/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_alertmanager_receiver_configuration_extension_yaml` variable" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:102 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:94 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:104 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:96 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:111 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:103 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:105 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:107 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:113 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:109 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:115 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:111 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:117 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:113 msgid "Configure your Prometheus Alertmanager with configuration like this:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:136 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:132 msgid "where `URL_HERE` looks like `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/some-room-name` or `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/!qporfwt:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:138 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:134 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:140 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:136 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-alertmanager-receiver`." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:142 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:138 msgid "Increase logging verbosity" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:144 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:140 msgid "The default logging level for this component is `info`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po index 93283a16b..a7ab6557f 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,68 +19,76 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:8 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:1 msgid "Setting up Appservice Double Puppet (optional)" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:10 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:3 msgid "The playbook can install and configure the Appservice Double Puppet service for you. It is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver." msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:12 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:5 msgid "This is useful for performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via the appservice method. The service is an implementation of this approach." msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:14 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:7 msgid "Previously, bridges supported performing double-puppeting with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but this old and hacky solution has been superseded by this Appservice Double Puppet method." msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:16 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:9 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:18 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:11 msgid "To enable the Appservice Double Puppet service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:24 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:17 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:26 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:19 msgid "There are some additional things you may wish to configure about the service." msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:28 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:21 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:30 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:23 msgid "`roles/custom/matrix-appservice-double-puppet/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_appservice_double_puppet_registration_configuration_extension_yaml` variable" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:32 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:25 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:34 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:27 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:41 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:34 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:36 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:38 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:43 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:40 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:45 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:42 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:47 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:44 msgid "Installing the service will automatically enable double puppeting for all bridges that support double puppeting via the appservice method." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po index 4716bb7b7..cf34a967b 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,169 +19,169 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:8 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:1 msgid "Setting up Draupnir for All/D4A (optional)" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:10 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:3 msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool for you in appservice mode." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:12 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:5 msgid "Appservice mode can be used together with the regular [Draupnir bot](configuring-playbook-bot-draupnir.md) or independently. Details about the differences between the 2 modes are described below." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:14 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:7 msgid "Draupnir Appservice mode compared to Draupnir bot mode" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:16 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:9 msgid "The administrative functions for managing the appservice are alpha quality and very limited. However, the experience of using an appservice-provisioned Draupnir is on par with the experience of using Draupnir from bot mode except in the case of avatar customisation as described later on in this document." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:18 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:11 msgid "Draupnir for all is the way to go if you need more than 1 Draupnir instance, but you don't need access to Synapse Admin features as they are not accessible through Draupnir for All (Even though the commands do show up in help)." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:20 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:13 msgid "Draupnir for all in the playbook is rate-limit-exempt automatically as its appservice configuration file does not specify any rate limits." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:22 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:15 msgid "Normal Draupnir does come with the benefit of access to Synapse Admin features. You are also able to more easily customise your normal Draupnir than D4A as D4A even on the branch with the Avatar command (To be Upstreamed to Mainline Draupnir) that command is clunky as it requires the use of things like Element Web devtools. In normal Draupnir this is a quick operation where you login to Draupnir with a normal client and set Avatar and Display name normally." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:24 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:17 msgid "Draupnir for all does not support external tooling like [MRU](https://mru.rory.gay) as it can't access Draupnir's user account." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:26 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:19 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:28 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:21 msgid "Create a main management room" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:30 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:23 msgid "The playbook does not create a management room for your Main Draupnir. You **need to create the room manually** before setting up the bot." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:32 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:25 msgid "Note that the room must be unencrypted." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:34 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:27 msgid "The management 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:36 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:29 msgid "This management room is used to control who has access to your D4A deployment. The room stores this data inside of the control room state so your bot must have sufficient powerlevel to send custom state events. This is default 50 or moderator as Element clients call this powerlevel." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:38 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:31 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:41 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:34 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:43 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:36 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ALIAS_HERE`." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:51 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:44 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:53 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:46 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:48 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:57 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:50 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:52 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:66 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:68 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:83 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:77 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:70 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:72 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:74 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:83 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:76 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:85 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:94 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:87 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:96 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:89 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:91 +msgid "If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com` you have succesfully installed Draupnir for All and can now start using it." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:100 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:93 msgid "The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot mode." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:102 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:95 msgid "Granting Users the ability to use D4A" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:104 -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." +#: ../../../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." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:106 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:99 msgid "The bot requires a powerlevel of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297))" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:108 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:101 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." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:110 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:103 msgid "How to provision a D4A once you are allowed to" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:112 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:105 msgid "To provision a D4A, you need to start a chat with `@draupnir-main:example.com`. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:114 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:107 msgid "Congratulations if you made it all the way here because you now have a fully working Draupnir for all deployment." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-backup-borg.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-backup-borg.po index 6c875ec97..5cb3570f2 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-backup-borg.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-backup-borg.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,28 +19,176 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-backup-borg.md:11 +#: ../../../docs/configuring-playbook-backup-borg.md:1 msgid "Setting up BorgBackup (optional)" msgstr "" -#: ../../../docs/configuring-playbook-backup-borg.md:13 +#: ../../../docs/configuring-playbook-backup-borg.md:3 msgid "The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) (short: Borg) with [borgmatic](https://torsion.org/borgmatic/) for you." msgstr "" -#: ../../../docs/configuring-playbook-backup-borg.md:15 +#: ../../../docs/configuring-playbook-backup-borg.md:5 msgid "BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service." msgstr "" -#: ../../../docs/configuring-playbook-backup-borg.md:17 -msgid "The [Ansible role for BorgBackup](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring BorgBackup, you can check them via:" +#: ../../../docs/configuring-playbook-backup-borg.md:7 +msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-backup-borg.md:18 -msgid "🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/docs/configuring-backup-borg.md) online" +#: ../../../docs/configuring-playbook-backup-borg.md:9 +msgid "Set up a remote server for storing backups" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:11 +msgid "You will need a remote server where BorgBackup will store the backups. There are hosted, BorgBackup compatible solutions available, such as [BorgBase](https://www.borgbase.com)." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:13 +msgid "Check the Postgres version" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:15 +msgid "By default, if you're using the integrated Postgres database server (as opposed to [an external Postgres server](configuring-playbook-external-postgres.md)), backups with BorgBackup will also include dumps of your Postgres database." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:17 +msgid "Unless you disable the Postgres-backup support, make sure that the Postgres version of your homeserver's database is compatible with borgmatic. You can check the compatible versions [here](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:19 -msgid "📁 `roles/galaxy/backup_borg/docs/configuring-backup-borg.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" +msgid "An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md). If you decide to go with another solution, you can disable Postgres-backup support for BorgBackup using the `backup_borg_postgresql_enabled` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:21 +msgid "Create a new SSH key" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:23 +msgid "Run the command below on any machine to create a new SSH key:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:29 +msgid "You don't need to place the key in the `.ssh` folder." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:31 +msgid "Add the public key" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:33 +msgid "Next, add the **public** part of this SSH key (the `matrix-borg-backup.pub` file) to your BorgBackup provider/server." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:35 +msgid "If you are using a hosted solution, follow their instructions. If you have your own server, copy the key to it with the command like below:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:45 +msgid "The **private** key needs to be added to `backup_borg_ssh_key_private` on your `inventory/host_vars/matrix.example.com/vars.yml` file as below." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:47 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:49 +msgid "To enable BorgBackup, add the following configuration to your `vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:76 +msgid "**Note**: `REPO` will be initialized on backup start, for example: `matrix`. See [Remote repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html#repository-urls) for the syntax." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:78 +msgid "Set backup archive name (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:80 +msgid "You can specify the backup archive name format. To set it, add the following configuration to your `vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:86 +msgid "Configure retention policy (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:88 +msgid "It is also possible to configure a retention strategy. To configure it, add the following configuration to your `vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:98 +msgid "Edit the backup schedule (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:100 +msgid "By default the backup will run 4 a.m. every day based on the `backup_borg_schedule` variable. It is defined in the format of systemd timer calendar." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:102 +msgid "To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:108 +msgid "**Note**: the actual job may run with a delay. See `backup_borg_schedule_randomized_delay_sec` [here](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/f5d5b473d48c6504be10b3d946255ef5c186c2a6/defaults/main.yml#L50) for its default value." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:110 +msgid "Set include and/or exclude directories (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:112 +msgid "`backup_borg_location_source_directories` defines the list of directories to back up. It's set to `{{ matrix_base_data_path }}` by default, which is the base directory for every service's data, such as Synapse, Postgres and the bridges." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:114 +msgid "You might also want to exclude certain directories or file patterns from the backup using the `backup_borg_location_exclude_patterns` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:116 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:118 +msgid "There are some additional things you may wish to configure about the component." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:120 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:122 +msgid "[backup_borg role](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml) for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `backup_borg_configuration_extension_yaml` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:124 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:126 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:133 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:135 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:137 +msgid "Manually start a backup" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:139 +msgid "Sometimes it can be helpful to run the backup as you'd like, avoiding to wait until 4 a.m., like when you test your configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:141 +msgid "If you want to run it immediately, log in to the server with SSH and run `systemctl start matrix-backup-borg`." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:143 +msgid "This will not return until the backup is done, so it can possibly take a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po index ce7928bea..f6026ed18 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,24 +19,112 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:1 +msgid "Setting up matrix-bot-chatgpt (optional, unmaintained)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:3 +msgid "**Note**: [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) is now an archived (**unmaintained**) project. Talking to ChatGPT (and many other LLM providers) can happen via the much more featureful [baibot](https://github.com/etkecc/baibot), which can be installed using [this playbook](configuring-playbook-bot-baibot.md). Consider using that bot instead of this one." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:5 +msgid "The playbook can install and configure [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:7 +msgid "Talk to [ChatGPT](https://openai.com/blog/chatgpt/) via your favourite Matrix client!" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:9 +msgid "Prerequisites" +msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:11 -msgid "Setting up matrix-chatgpt-bot (optional, removed)" +msgid "Obtain an OpenAI API key" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:13 -msgid "🪦 The playbook used to be able to install and configure [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot), but no longer includes this component." +msgid "To use the bot, you'd need to obtain an API key from [https://platform.openai.com/account/api-keys](https://platform.openai.com/account/api-keys)." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:15 -msgid "While not a 1:1 replacement, the bot'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)." +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:17 -msgid "Uninstalling matrix-chatgpt-bot manually" +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:19 -msgid "If you still have the matrix-chatgpt-bot component 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:" +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:21 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:27 +msgid "Obtain an access token and create encryption keys" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:29 +msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:31 +msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:34 +msgid "To make sure the bot can read encrypted messages, it will need an encryption key, just like any other new user. While obtaining the access token, follow the prompts to setup a backup key. More information can be found in the [Element documentation](https://element.io/help#encryption6)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:36 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:38 +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `API_KEY_HERE` with the API key retrieved [here](#obtain-an-openai-api-key) and `ACCESS_TOKEN_HERE` with the access token created [here](#obtain-an-access-token-and-create-encryption-keys), respectively." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:55 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:57 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:64 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:66 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:68 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:70 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:72 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:74 +msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.chatgpt:example.com` where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:76 +msgid "After the bot joins the room, you can send a message to it. When you do so, use the prefix if you configured it or mention the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:78 +msgid "You can also refer to the upstream [documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po index 43a785f97..edfaf144d 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po @@ -8,167 +8,147 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2026-02-13 10:32+0000\n" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bot-go-neb.md:11 +#: ../../../docs/configuring-playbook-bot-go-neb.md:1 msgid "Setting up Go-NEB (optional, unmaintained)" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:13 -msgid "**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an archived (**unmaintained**) project. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be [installed using this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bot instead of this one." +#: ../../../docs/configuring-playbook-bot-go-neb.md:3 +msgid "**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an archived (**unmaintained**) project. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bot instead of this one." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:15 +#: ../../../docs/configuring-playbook-bot-go-neb.md:5 msgid "The playbook can install and configure [Go-NEB](https://github.com/matrix-org/go-neb) for you." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:17 +#: ../../../docs/configuring-playbook-bot-go-neb.md:7 msgid "Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, the original Matrix bot written in Python." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:19 +#: ../../../docs/configuring-playbook-bot-go-neb.md:9 msgid "See the project's [documentation](https://github.com/matrix-org/go-neb/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:21 +#: ../../../docs/configuring-playbook-bot-go-neb.md:11 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:23 +#: ../../../docs/configuring-playbook-bot-go-neb.md:13 msgid "Register the bot account" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:25 +#: ../../../docs/configuring-playbook-bot-go-neb.md:15 msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:27 +#: ../../../docs/configuring-playbook-bot-go-neb.md:17 msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:29 +#: ../../../docs/configuring-playbook-bot-go-neb.md:19 msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:35 +#: ../../../docs/configuring-playbook-bot-go-neb.md:25 msgid "Obtain an access token" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:37 +#: ../../../docs/configuring-playbook-bot-go-neb.md:27 msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:39 +#: ../../../docs/configuring-playbook-bot-go-neb.md:29 msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:42 +#: ../../../docs/configuring-playbook-bot-go-neb.md:32 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:44 +#: ../../../docs/configuring-playbook-bot-go-neb.md:34 msgid "By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to create a CNAME record for `goneb`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:46 +#: ../../../docs/configuring-playbook-bot-go-neb.md:36 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:48 +#: ../../../docs/configuring-playbook-bot-go-neb.md:38 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:50 +#: ../../../docs/configuring-playbook-bot-go-neb.md:40 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_GONEB_HERE` and `ACCESS_TOKEN_FOR_ANOTHER_GONEB_HERE` with the ones created [above](#obtain-an-access-token)." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:214 +#: ../../../docs/configuring-playbook-bot-go-neb.md:204 msgid "Adjusting the Go-NEB URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:216 +#: ../../../docs/configuring-playbook-bot-go-neb.md:206 msgid "By tweaking the `matrix_bot_go_neb_hostname` and `matrix_bot_go_neb_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:218 +#: ../../../docs/configuring-playbook-bot-go-neb.md:208 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:229 +#: ../../../docs/configuring-playbook-bot-go-neb.md:219 msgid "After changing the domain, **you may need to adjust your DNS** records to point the Go-NEB domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:231 +#: ../../../docs/configuring-playbook-bot-go-neb.md:221 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:233 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-go-neb.md:235 -msgid "There are some additional things you may wish to configure about the bot." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-go-neb.md:237 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-go-neb.md:239 -msgid "`roles/custom/matrix-bot-go-neb/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +#: ../../../docs/configuring-playbook-bot-go-neb.md:223 +msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:240 -msgid "`roles/custom/matrix-bot-go-neb/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_go_neb_configuration_extension_yaml` variable" +#: ../../../docs/configuring-playbook-bot-go-neb.md:225 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:242 -msgid "Installing" +#: ../../../docs/configuring-playbook-bot-go-neb.md:232 +msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:244 -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:" +#: ../../../docs/configuring-playbook-bot-go-neb.md:234 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:251 +#: ../../../docs/configuring-playbook-bot-go-neb.md:236 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:253 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-bot-go-neb.md:238 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:255 +#: ../../../docs/configuring-playbook-bot-go-neb.md:240 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:257 +#: ../../../docs/configuring-playbook-bot-go-neb.md:242 msgid "To use the bot, invite it to any existing Matrix room (`/invite @bot.go-neb:example.com` where `example.com` is your base domain, not the `matrix.` domain). Make sure you are granted with the sufficient permission if you are not the room owner." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:259 +#: ../../../docs/configuring-playbook-bot-go-neb.md:244 msgid "Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy matrix`" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:261 +#: ../../../docs/configuring-playbook-bot-go-neb.md:246 msgid "If you enabled the github_cmd service, send `!github help` to the bot in the room to see the available commands." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:263 +#: ../../../docs/configuring-playbook-bot-go-neb.md:248 msgid "You can also refer to the upstream [Documentation](https://github.com/matrix-org/go-neb)." msgstr "" - -#: ../../../docs/configuring-playbook-bot-go-neb.md:265 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-go-neb.md:267 -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-go-neb`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po index 55b300444..d01bea0f4 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,181 +19,153 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:10 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:1 msgid "Setting up Appservice Discord bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:12 -msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge supported by the playbook." +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:3 +msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:13 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:4 msgid "For using as a Bot we are recommend the Appservice Discord bridge (the one being discussed here), because it supports plumbing." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:14 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:5 msgid "For personal use we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:16 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:7 msgid "The playbook can install and configure [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:18 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:9 msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-discord/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:20 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:11 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:22 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:13 msgid "Create a Discord Application [here](https://discordapp.com/developers/applications). Then retrieve Client ID, and create a bot from the Bot tab and retrieve the Bot token." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:24 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:15 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:26 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:17 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:40 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:42 -msgid "There are some additional things you may wish to configure about the bridge." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:44 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:46 -msgid "`roles/custom/matrix-bridge-appservice-discord/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:31 +msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:47 -msgid "`roles/custom/matrix-bridge-appservice-discord/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_appservice_discord_configuration_extension_yaml` variable" +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:33 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:49 -msgid "Installing" +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:40 +msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:51 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:42 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:58 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:44 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:60 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:46 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:63 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:48 msgid "Self-Service Bridging (Manual)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:65 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:50 msgid "Self-service bridging allows you to bridge specific and existing Matrix rooms to specific Discord rooms. To enable it, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:71 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:56 msgid "**Note**: If self-service bridging is not enabled, `!discord help` commands will return no results." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:73 -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:97 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:58 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:82 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:75 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:60 msgid "Once self-service is enabled, start a chat with `@_discord_bot:example.com` and say `!discord help bridge`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:77 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:62 msgid "Then, follow the instructions in the help output message." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:79 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:64 msgid "If the bot is not already in the Discord server, follow the provided invite link. This may require you to be a administrator of the Discord server." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:81 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:66 msgid "On the Discord side, send `!matrix help` to the bot to see the available commands for managing the bridge and Matrix users." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:83 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:68 msgid "**Note**: Encrypted Matrix rooms are not supported as of writing." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:85 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:70 msgid "Portal Bridging (Automatic)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:87 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:72 msgid "Through portal bridging, Matrix rooms will automatically be created by the bot and bridged to the relevant Discord room. This is done by simply joining a room with a specific name pattern (`#_discord__`)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:89 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:74 msgid "All Matrix rooms created this way are **listed publicly** by default, and you will not have admin permissions to change this. To get more control, [make yourself a room Administrator](#getting-administrator-access-in-a-portal-bridged-room). You can then unlist the room from the directory and change the join rules." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:91 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:76 msgid "To disable portal bridging, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:99 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:84 msgid "To get started with Portal Bridging:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:101 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:86 msgid "To invite the bot to Discord, retrieve the invite link from the `{{ matrix_appservice_discord_config_path }}/invite_link` file on the server (this defaults to `/matrix/appservice-discord/config/invite_link`). You need to peek at the file on the server via SSH, etc., because it's not available via HTTP(S)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:102 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:87 msgid "Room addresses follow this syntax: `#_discord__`. You can easily find the guild and channel IDs by logging into Discord in a browser and opening the desired channel. The URL will have this format: `discord.com/channels//`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:103 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:88 msgid "Once you have figured out the appropriate room address, you can join by doing `/join #_discord__` in your Matrix client." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:105 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:90 msgid "Getting Administrator access in a portal bridged room" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:107 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:92 msgid "By default, you won't have Administrator access in rooms created by the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:109 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:94 msgid "To adjust room access privileges or do various other things (change the room name subsequently, etc.), you'd wish to become an Administrator." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:111 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:96 msgid "There's the Discord bridge's guide for [setting privileges on bridge managed rooms](https://github.com/matrix-org/matrix-appservice-discord/blob/master/docs/howto.md#set-privileges-on-bridge-managed-rooms). To do the same with our container setup, run the following command on the server:" msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:118 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:120 -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-discord`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:122 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:124 -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 (adapt to your needs) and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po index 36f8baa22..f4723b399 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,88 +19,60 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:10 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:1 msgid "Setting up Appservice IRC bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:12 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:3 msgid "**Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [Heisenbridge](configuring-playbook-bridge-heisenbridge.md) bridge supported by the playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:14 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:5 msgid "The playbook can install and configure the [matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc) bridge for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:16 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:7 msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-irc/blob/master/HOWTO.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:18 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:9 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:20 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:11 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:72 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:74 -msgid "There are some additional things you may wish to configure about the bridge." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:76 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:78 -msgid "`roles/custom/matrix-bridge-appservice-irc/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:63 +msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:79 -msgid "`roles/custom/matrix-bridge-appservice-irc/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_irc_configuration_extension_yaml` variable" +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:65 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:81 -msgid "Installing" +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:72 +msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:83 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:74 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:90 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:76 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:92 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:78 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:94 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:80 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:96 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:82 msgid "To use the bridge, you need to start a chat with `@irc_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:98 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:100 -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-irc`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:102 -msgid "Configuring for logging" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:104 -msgid "The default logging level for this component is `debug`, and the log is output to the console only. If you want to change the verbosity or enable logging to a file, add the following configuration to your `vars.yml` file (adapt to your needs) and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po index 0e49b34b7..71073c449 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,112 +19,104 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:10 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:1 msgid "Setting up Appservice Kakaotalk bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:12 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:3 msgid "The playbook can install and configure [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) for you, for bridging to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG). This bridge is based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:14 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:5 msgid "See the project's [documentation](https://src.miscworks.net/fair/matrix-appservice-kakaotalk/src/branch/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:16 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:7 msgid "[!WARNING] There have been recent reports (~2022-09-16) that **using this bridge may get your account banned**." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:19 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:10 msgid "Prerequisite (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:21 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:12 msgid "Enable Shared Secret Auth" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:23 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:14 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:25 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:16 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-appservice-kakaotalk.md:27 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:18 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-appservice-kakaotalk.md:29 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:20 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:31 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:22 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:37 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:28 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:39 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:30 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:41 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:32 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:43 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:34 msgid "`roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:44 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:35 msgid "`roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_appservice_kakaotalk_configuration_extension_yaml` variable" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:46 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:37 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:48 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:39 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.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-appservice-kakaotalk.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-appservice-kakaotalk.md:59 -msgid "Usage" +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:46 +msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:61 -msgid "To use the bridge, you need to start a chat with `@kakaotalkbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:48 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:63 -msgid "You then need to send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable bridging for your Kakaotalk account. The `--save` flag may be omitted, if you'd rather not save your password." +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:50 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:65 -msgid "Troubleshooting" +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:52 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:67 -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-kakaotalk`." +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:54 +msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:69 -msgid "Increase logging verbosity" +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:56 +msgid "To use the bridge, you need to start a chat with `@kakaotalkbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:71 -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-appservice-kakaotalk.md:58 +msgid "You then need to send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable bridging for your Kakaotalk account. The `--save` flag may be omitted, if you'd rather not save your password." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po index e557a4ce9..0a6f24be3 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,24 +19,250 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:22 -msgid "Setting up Appservice Slack bridging (optional, removed)" +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:1 +msgid "Setting up Appservice Slack bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:3 +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:89 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:4 +msgid "Bridging to [Slack](https://slack.com) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:5 +msgid "Currently (as of November, 2024) **this component is not available for new installation unless you have already created a classic Slack application** (which the bridge makes use of in order to enable bridging between Slack and Matrix), because the creation of classic Slack applications has been discontinued since June 4 2024. The author of the bridge claims [here](https://github.com/matrix-org/matrix-appservice-slack/issues/789#issuecomment-2172947787) that he plans to support the modern Slack application and until then \"the best (and only) option for new installations is to use the webhook bridging\"." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:7 +msgid "The playbook can install and configure [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:9 +msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-slack/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:13 +msgid "Create a Classic Slack App" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:15 +msgid "First, you need to create a Classic Slack App [here](https://api.slack.com/apps?new_classic_app=1)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:17 +msgid "Name the app \"matrixbot\" (or anything else you'll remember). Select the team/workspace this app will belong to. Click on bot users and add a new bot user. We will use this account to bridge the the rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:19 +msgid "Then, click on Event Subscriptions and enable them and use the request url: `https://matrix.example.com/appservice-slack`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:21 +msgid "Add the following events as `Bot User Events` and save:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:23 +msgid "team_domain_change" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:24 -msgid "🪦 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." +msgid "message.channels" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:25 +msgid "message.groups (if you want to bridge private channels)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:26 -msgid "**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." +msgid "reaction_added" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:27 +msgid "reaction_removed" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:29 +msgid "Next, click on \"OAuth & Permissions\" and add the following scopes:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:31 +msgid "chat:write:bot" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:32 +msgid "users:read" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:33 +msgid "reactions:write" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:34 +msgid "files:write:user (if you want to bridge files)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:36 +msgid "**Note**: In order to make Slack files visible to Matrix users, this bridge will make Slack files visible to anyone with the url (including files in private channels). This is different than the current behavior in Slack, which only allows authenticated access to media posted in private channels. See MSC701 for details." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:38 +msgid "Click on \"Install App\" and \"Install App to Workspace\". Note the access tokens shown. You will need the Bot User OAuth Access Token and if you want to bridge files, the OAuth Access Token whenever you link a room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:40 +msgid "Create an administration control room on Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:42 +msgid "Create a new Matrix room to act as the administration control room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:44 +msgid "Note its internal room ID. This can be done in Element Web by sending a message, opening the options for that message and choosing \"view source\". The room ID will be displayed near the top." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:46 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:48 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:64 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:66 +msgid "There are some additional things you may wish to configure about the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:68 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:70 +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:71 +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:73 +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:80 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:82 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:91 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:93 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:95 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:97 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:99 +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:101 +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:103 +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:104 +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:105 +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//details/`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:106 +msgid "Issue a link command in the administration control room with these collected values as arguments:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:108 +msgid "with file bridging:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:114 +msgid "without file bridging:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:120 +msgid "These arguments can be shortened to single-letter forms:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:126 +msgid "Unlinking" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:128 +msgid "Channels can be unlinked again by sending this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:134 +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:136 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:138 +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:140 +msgid "Linking: \"Room is now pending-name\"" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:142 +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:144 +msgid "Messages work from Matrix to Slack, but not the other way around" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:146 +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:28 -msgid "Uninstalling the component manually" +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:148 +#, python-format +msgid "`WARN SlackEventHandler Ignoring message from unrecognised Slack channel ID : %s (%s) `" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:30 -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:" +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:150 +msgid "This may particularly hit you, if you tried to unsuccessfully link your room multiple times without unlinking it after each failed attempt." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po index 4e23378b0..f9a42b739 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,24 +19,96 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:16 -msgid "Setting up Appservice Webhooks bridging (optional, removed)" +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:1 +msgid "Setting up Appservice Webhooks bridging (optional, deprecated)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:18 -msgid "🪦 The playbook used to be able to install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks), but no longer includes this component, as it has been deprecated since more than several years." +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:3 +msgid "**Note**: This bridge has been deprecated. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bridge instead of this one." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:20 -msgid "You may wish to use [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) instead." +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:5 +msgid "The playbook can install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:22 -msgid "Uninstalling the bridge manually" +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:7 +msgid "See the project's [documentation](https://github.com/turt2live/matrix-appservice-webhooks/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:24 -msgid "If you still have matrix-appservice-webhooks 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:" +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:11 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:27 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:29 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:36 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:38 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:40 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:42 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:44 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:46 +msgid "To use the bridge, you need to invite the bridge bot user to your room in either way." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:48 +msgid "Send `/invite @_webhook:example.com` (**Note**: Make sure you have administration permissions in your room)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:49 +msgid "Add the bridge bot to a private channel (personal channels imply you being an administrator)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:51 +msgid "You then need to send a message to the bridge bot to receive a private message including the webhook link:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:57 +msgid "The JSON body for posting messages will have to look like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:68 +msgid "You can test this via curl like so:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:81 +msgid "Setting Webhooks with Dimension integration manager" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:83 +msgid "If you're using the [Dimension integration manager](configuring-playbook-dimension.md), you can configure the Webhooks bridge with it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:85 +msgid "To configure it, open the Dimension integration manager, and go to \"Settings\" and \"Bridges\", then select edit action for \"Webhook Bridge\"." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:87 +msgid "On the UI, press \"Add self-hosted Bridge\" button and populate \"Provisioning URL\" and \"Shared Secret\" values from `/matrix/appservice-webhooks/config/config.yaml` file's homeserver URL value and provisioning secret value, respectively." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po index 626134a23..f33b5ad94 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,112 +19,108 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:11 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:1 msgid "Setting up Beeper Linkedin bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:13 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:3 msgid "The playbook can install and configure [beeper-linkedin](https://github.com/beeper/linkedin) for you, for bridging to [LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on the mautrix-python framework and can be configured in a similar way to the mautrix bridges." msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:15 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:5 msgid "See the project's [documentation](https://github.com/beeper/linkedin/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:17 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:7 msgid "Prerequisite" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:19 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:9 msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:21 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:11 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [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-beeper-linkedin.md:23 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:13 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-beeper-linkedin.md:25 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:15 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-beeper-linkedin.md:27 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:29 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:19 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:35 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:25 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:37 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:27 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:39 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:29 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-beeper-linkedin.md:41 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:31 msgid "**Note**: when following the guide to configure the bridge, make sure to replace `_mautrix_SERVICENAME_` in the variable names with `_beeper_linkedin_`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:43 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:33 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:45 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:35 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:52 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:42 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:44 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:46 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:54 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:48 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:56 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:50 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:58 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:52 msgid "To use the bridge, you need to start a chat with `@linkedinbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:60 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:54 msgid "You then need to send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to enable bridging for your LinkedIn account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:62 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:56 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:64 -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-beeper-linkedin`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:66 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:68 -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 "" - -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:74 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:58 msgid "Bridge asking for 2FA even if you don't have 2FA enabled" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:76 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:60 msgid "If you don't have 2FA enabled and are logging in from a strange IP for the first time, LinkedIn will send an email with a one-time code. You can use this code to authorize the bridge session. In my experience, once the IP is authorized, you will not be asked again." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po index 4877daa61..2efd86e84 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,20 +19,92 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:12 -msgid "Setting up Go Skype Bridge bridging (optional, removed)" +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:1 +msgid "Setting up Go Skype Bridge bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:14 -msgid "🪦 The playbook used to be able to install and configure [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge), but no longer includes this component, as Skype has been discontinued since May 2025." +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:3 +msgid "The playbook can install and configure [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) for you, for bridging to [Skype](https://www.skype.com/). This bridge was created based on [mautrix-whatsapp](https://github.com/mautrix/whatsapp) and can be configured in a similar way to it." msgstr "" -#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:16 -msgid "Uninstalling the bridge manually" +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:5 +msgid "See the project's [documentation](https://github.com/kelaresg/go-skype-bridge/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:18 -msgid "If you still have the Go Skype bridge 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:" +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:7 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:9 +msgid "Enable Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:11 +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:13 +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-go-skype-bridge.md:15 +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-go-skype-bridge.md:17 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:19 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:25 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:27 +msgid "There are some additional things you may wish to configure about the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:29 +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-go-skype-bridge.md:31 +msgid "**Note**: when following the guide to configure the bridge, make sure to replace `_mautrix_SERVICENAME_` in the variable names with `_go_skype_bridge_`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:33 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:35 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:42 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:44 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:46 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:48 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:50 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:52 +msgid "To use the bridge, you need to start a chat with `@skypebridgebot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po index 31b992951..5b68c9267 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,120 +19,104 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:9 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:1 msgid "Setting up Heisenbridge bouncer-style IRC bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:11 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:3 msgid "**Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md) bridge supported by the playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:13 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:5 msgid "The playbook can install and configure [Heisenbridge](https://github.com/hifi/heisenbridge) — the bouncer-style [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) bridge for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:15 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:7 msgid "See the project's [documentation](https://github.com/hifi/heisenbridge/blob/master/README.md) to learn what it does and why it might be useful to you. You can also take a look at [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:17 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:9 msgid "Adjusting DNS records (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:19 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:11 msgid "By default, this playbook installs Heisenbridge on the `matrix.` subdomain, at the `/heisenbridge` path (https://matrix.example.com/heisenbridge). It would handle media requests there (see the [release notes for Heisenbridge v1.15.0](https://github.com/hifi/heisenbridge/releases/tag/v1.15.0)). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:21 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:13 msgid "If you wish to adjust it, see the section [below](#adjusting-the-heisenbridge-url-optional) for details about DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:23 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:15 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:25 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:17 msgid "To enable Heisenbridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:38 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:30 msgid "Adjusting the Heisenbridge URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:40 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:32 msgid "By tweaking the `matrix_heisenbridge_hostname` and `matrix_heisenbridge_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:42 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:34 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:50 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:42 msgid "If you've changed the default hostname, you may need to create a CNAME record for the Heisenbridge domain (`heisenbridge.example.com`), which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:52 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:44 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:54 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:56 -msgid "There are some additional things you may wish to configure about the bridge." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:58 -msgid "Take a look at:" +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:46 +msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:60 -msgid "`roles/custom/matrix-bridge-heisenbridge/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:48 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:62 -msgid "Installing" +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:55 +msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:64 -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:" +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:57 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:71 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:59 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:73 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:61 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:75 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:63 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:77 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:65 msgid "To use the bridge, you need to start a chat with `@heisenbridge:example.com` (where `example.com` is your base domain, not the `matrix.` domain). If the bridge ignores you and a DM is not accepted then the owner setting may be wrong." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:79 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:67 msgid "Help is available for all commands with the `-h` switch." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:81 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:69 msgid "You can also learn the basics by watching [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:83 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:71 msgid "If you encounter issues or feel lost you can join the project room at [#heisenbridge:vi.fi](https://matrix.to/#/#heisenbridge:vi.fi) for help." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:85 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:87 -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-heisenbridge`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po index d7fd5b8cb..902850478 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,137 +19,141 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:11 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:1 msgid "Setting up matrix-hookshot (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:13 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:3 msgid "The playbook can install and configure [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:15 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:5 msgid "Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) from software project management services such as GitHub, GitLab, Jira, and Figma, as well as generic webhooks." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:17 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:7 msgid "See the project's [documentation](https://matrix-org.github.io/matrix-hookshot/latest/hookshot.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:19 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:9 +msgid "**Note**: the playbook also supports [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), which however was deprecated by its author." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:11 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:21 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:13 msgid "Download GitHub app private key (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:23 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:15 msgid "If you're setting up the GitHub bridge, you need to create your GitHub app, and generate a private key file of it." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:25 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:17 msgid "You need to download the private key file, if you will install the file manually or with the `aux` role. For details, see [the section below](#manage-github-private-key-with-aux-role)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:27 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:19 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:29 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:21 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `GITHUB_PRIVATE_KEY_HERE` with the one created [above](#download-github-app-private-key)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:43 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:35 msgid "For each of the services (GitHub, GitLab, Jira, Figma, and generic webhooks) fill in the respective variables `matrix_hookshot_service_*` listed in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) as required." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:45 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:37 msgid "Take special note of the `matrix_hookshot_*_enabled` variables. Services that need no further configuration are enabled by default (GitLab and generic webhooks), while you must first add the required configuration and enable the others (GitHub, Jira, and Figma)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:47 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:39 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:49 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:41 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:51 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:43 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:53 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:45 msgid "`roles/custom/matrix-bridge-hookshot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:54 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:46 msgid "`roles/custom/matrix-bridge-hookshot/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_hookshot_configuration_extension_yaml` and `matrix_hookshot_registration_extension_yaml` variables" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:56 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:48 msgid "Refer the [official instructions](https://matrix-org.github.io/matrix-hookshot/latest/setup.html) and the comments in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) to learn what the individual options do." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:58 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:50 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:60 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:52 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:67 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:59 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service hookshot` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:69 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:61 msgid "`just install-service hookshot` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:71 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:63 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:73 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:65 msgid "To use the bridge, you need to create a room and invite the Hookshot bot (`@hookshot:example.com`) to it." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:75 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:67 msgid "Make sure the bot is able to send state events (usually the Moderator power level in clients)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:77 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:69 msgid "Send `!hookshot help` to the bot to see the available commands." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:79 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:71 msgid "Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-hookshot/latest/usage.html) for more details about using the bridge's various features." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:81 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:73 msgid "💡 **Note**: the different listeners are bound to certain paths which might differ from those assumed by the hookshot documentation. See [URLs for bridges setup](#urls-for-bridges-setup) below." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:83 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:75 msgid "Reset crypto store" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:85 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:77 msgid "Should the crypto store be corrupted, you can reset it by executing this Ansible playbook with the tag `reset-hookshot-encryption` added:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:91 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:83 msgid "More setup documentation" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:93 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:85 msgid "URLs for bridges setup" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:95 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:87 msgid "Unless indicated otherwise, the following endpoints are reachable on your `matrix.` subdomain (if the feature is enabled)." msgstr "" @@ -249,6 +253,22 @@ msgstr "" msgid "Figma" msgstr "" +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "provisioning" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/v1/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_provisioning_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Dimension [provisioning](#provisioning-api)" +msgstr "" + #: ../../../docs/configuring-playbook-bridge-hookshot.md msgid "appservice" msgstr "" @@ -281,98 +301,114 @@ msgstr "" msgid "Widgets" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:107 +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "metrics" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/metrics/hookshot`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_metrics_enabled` and exposure enabled via `matrix_hookshot_metrics_proxying_enabled` or `matrix_metrics_exposure_enabled`. Read more in the [Metrics section](#metrics) below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Prometheus" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:101 msgid "Also see the various `matrix_hookshot_container_labels_*` variables in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), which expose URLs publicly." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:109 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:103 msgid "The different listeners are also reachable *internally* in the docker-network via the container's name (configured by `matrix_hookshot_container_url`) and on different ports (e.g. `matrix_hookshot_appservice_port`). Read [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) in detail for more info." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:111 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:105 msgid "Manage GitHub Private Key with aux role" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:113 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:107 msgid "The GitHub bridge requires you to install a private key file. This can be done in multiple ways:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:115 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:109 msgid "copy the *contents* of the downloaded file and set the variable `matrix_hookshot_github_private_key` to the contents (see example in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml))." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:116 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:110 msgid "somehow copy the file to the path `{{ matrix_hookshot_base_path }}/{{ matrix_hookshot_github_private_key_file }}` (default: `/matrix/hookshot/private-key.pem`) on the server manually." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:117 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:111 msgid "use the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) to copy the file from an arbitrary path on your ansible client to the correct path on the server." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:119 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:113 msgid "To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:130 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:124 msgid "For more information, see the documentation in the [default configuration of the aux role](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:132 -msgid "Enable metrics" +#: ../../../docs/configuring-playbook-bridge-hookshot.md:126 +msgid "Provisioning API" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:134 -msgid "The playbook can enable and configure the metrics of the service for you." +#: ../../../docs/configuring-playbook-bridge-hookshot.md:128 +msgid "The provisioning API will be enabled automatically if you set `matrix_dimension_enabled: true` and provided a `matrix_hookshot_provisioning_secret`, unless you override it either way. To use hookshot with dimension, you will need to enter as \"Provisioning URL\": `http://matrix-hookshot:9002`, which is made up of the variables `matrix_hookshot_container_url` and `matrix_hookshot_provisioning_port`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:136 -msgid "Metrics are **only enabled by default** if the builtin [Prometheus](configuring-playbook-prometheus-grafana.md) is enabled (by default, Prometheus isn't enabled). If so, metrics will automatically be collected by Prometheus and made available in Grafana. You will, however, need to set up your own Dashboard for displaying them." +#: ../../../docs/configuring-playbook-bridge-hookshot.md:130 +msgid "Metrics" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:138 -msgid "To enable the metrics, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-bridge-hookshot.md:132 +msgid "Metrics are **only enabled by default** if the builtin [Prometheus](configuring-playbook-prometheus-grafana.md) is enabled (by default, Prometheus isn't enabled). If so, metrics will automatically be collected by Prometheus and made available in Grafana. You will, however, need to set up your own Dashboard for displaying them." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:145 -msgid "**To collect metrics from an external Prometheus server**, besides enabling metrics as described above, you will also need to enable metrics exposure on `https://matrix.example.com/metrics/hookshot` by adding the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-bridge-hookshot.md:134 +msgid "To explicitly enable metrics, use `matrix_hookshot_metrics_enabled: true`. This only exposes metrics over the container network, however." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:151 -msgid "By default metrics are exposed publicly **without** password-protection. To password-protect the metrics with dedicated credentials, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-bridge-hookshot.md:136 +msgid "**To collect metrics from an external Prometheus server**, besides enabling metrics as described above, you will also need to enable metrics exposure on `https://matrix.example.com/metrics/hookshot` by:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:158 -msgid "To `matrix_hookshot_container_labels_metrics_middleware_basic_auth_users`, set the Basic Authentication credentials (raw `htpasswd` file content) used to protect the endpoint. See https://doc.traefik.io/traefik/middlewares/http/basicauth/#users for details about it." +#: ../../../docs/configuring-playbook-bridge-hookshot.md:138 +msgid "either enabling metrics exposure for Hookshot via `matrix_hookshot_metrics_proxying_enabled: true`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:160 -msgid "**Note**: alternatively, you can use `matrix_metrics_exposure_enabled` to expose all services on this `/metrics/*` feature, and you can use `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users` to password-protect the metrics of them. See [this section](configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) for more information." +#: ../../../docs/configuring-playbook-bridge-hookshot.md:139 +msgid "or enabling metrics exposure for all services via `matrix_metrics_exposure_enabled: true`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:162 -msgid "Enable Grafana (optional)" +#: ../../../docs/configuring-playbook-bridge-hookshot.md:141 +msgid "Whichever one you go with, by default metrics are exposed publicly **without** password-protection. See [the Prometheus and Grafana docs](configuring-playbook-prometheus-grafana.md) for details about password-protection for metrics." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:164 -msgid "Probably you wish to enable Grafana along with Prometheus for generating graphs of the metrics." +#: ../../../docs/configuring-playbook-bridge-hookshot.md:143 +msgid "Collision with matrix-appservice-webhooks" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:166 -msgid "To enable Grafana, see [this section](configuring-playbook-prometheus-grafana.md#adjusting-the-playbook-configuration-grafana) for instructions." +#: ../../../docs/configuring-playbook-bridge-hookshot.md:145 +msgid "If you are also running [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), it reserves its namespace by the default setting `matrix_appservice_webhooks_user_prefix: '_webhook_'`. You should take care if you modify its or hookshot's prefix that they do not collide with each other's namespace (default `matrix_hookshot_generic_userIdPrefix: '_webhooks_'`)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:168 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:147 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:170 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-hookshot`." +#: ../../../docs/configuring-playbook-bridge-hookshot.md:149 +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-bridge-hookshot`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:172 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:151 msgid "Increase logging verbosity" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:174 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:153 msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po index 7be5b37be..60066e3b7 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,80 +19,64 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:9 +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:1 msgid "Setting up Matrix SMS bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:11 +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:3 msgid "The playbook can install and configure [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:13 +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:5 msgid "See the project's [documentation](https://github.com/benkuly/matrix-sms-bridge/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:15 +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:7 msgid "Prerequisite" msgstr "" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:17 +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:9 msgid "The bridge uses [android-sms-gateway-server](https://github.com/RebekkaMa/android-sms-gateway-server). You need to configure it first." msgstr "" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:19 +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:11 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:21 +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:13 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:43 -msgid "Extending the configuration" +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:36 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:38 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:45 -msgid "There are some additional things you may wish to configure about the bridge." +msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:47 -msgid "Take a look at:" +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:49 -msgid "`roles/custom/matrix-bridge-sms/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_sms_bridge_configuration_extension_yaml` variable" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:51 -msgid "Installing" +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:53 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:60 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:62 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:64 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:66 +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:55 msgid "Read the [user guide](https://github.com/benkuly/matrix-sms-bridge/blob/master/README.md#user-guide) to see how this bridge works." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:68 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:70 -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-sms-bridge`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-bluesky.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-bluesky.po deleted file mode 100644 index b5f31f175..000000000 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-bluesky.po +++ /dev/null @@ -1,126 +0,0 @@ -# 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 , 2026. -# -#, fuzzy -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" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: bg\n" -"Language-Team: bg \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-bridge-mautrix-bluesky.md:9 -msgid "Setting up Mautrix Bluesky bridging (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:11 -msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:13 -msgid "The playbook can install and configure [mautrix-bluesky](https://github.com/mautrix/bluesky) for you, which provides a bridge to [Bluesky](https://bsky.social/about)." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:15 -msgid "See the project's [documentation](https://github.com/mautrix/bluesky/blob/master/README.md) to learn what it does and why it might be useful to you." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:17 -msgid "Prerequisite (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:19 -msgid "Enable Appservice Double Puppet" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:21 -msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:23 -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-bluesky.md:25 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:27 -msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:33 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:35 -msgid "There are some additional things you may wish to configure about the bridge." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:38 -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-bluesky.md:40 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:42 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:49 -msgid "**Notes**:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:51 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:53 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:55 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:57 -msgid "To use the bridge, you need to start a chat with `@blueskybot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:59 -msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/bluesky/authentication.html)." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:61 -msgid "After logging in, the bridge will create portal rooms for recent chats. Portal rooms for other chats will be created as you receive messages." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:63 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:65 -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-bluesky`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:67 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:69 -msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-bridges.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-bridges.po index bfc926488..88288e08b 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-bridges.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-bridges.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,281 +19,286 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:10 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:1 msgid "Setting up a Generic Mautrix Bridge (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:12 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:3 msgid "The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, discord, signal, googlechat, etc.), as well as many other (non-mautrix) bridges. This is a common guide for configuring mautrix bridges." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:14 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:5 msgid "The author of the bridges maintains [the official docs](https://docs.mau.fi/bridges/index.html), whose source code is available at [mautrix/docs](https://github.com/mautrix/docs) repository on GitHub. You may as well to refer it while configuring them." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:16 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:7 msgid "You can see each bridge's features on the `ROADMAP.md` file in its corresponding mautrix repository." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:18 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:9 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:20 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:11 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:27 -msgid "**Note**: for bridging to Meta's Messenger or Instagram, you would need to add `meta` with an underscore symbol (`_`) or hyphen (`-`) based on the context as prefix to each `SERVICENAME`; add `_` to variables (as in `matrix_mautrix_meta_messenger_configuration_extension_yaml` for example) and `-` to paths of the configuration files (as in `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2`), respectively." +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:18 +msgid "**Note**: for bridging to Meta's Messenger or Instagram, you would need to add `meta` with an underscore symbol (`_`) or hyphen (`-`) based on the context as prefix to each `SERVICENAME`; add `_` to variables (as in `matrix_mautrix_meta_messenger_configuration_extension_yaml` for example) and `-` to paths of the configuration files (as in `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2`), respectively. **`matrix_mautrix_facebook_*` and `matrix_mautrix_instagram_*` variables belong to the deprecated components and do not control the new bridge** ([mautrix-meta](https://github.com/mautrix/meta)), which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:29 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:20 msgid "There are some additional things you may wish to configure about the bridge before you continue. Each bridge may have additional requirements besides `_enabled: true`. For example, the mautrix-telegram bridge (our documentation page about it is [here](configuring-playbook-bridge-mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and `matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each bridge's individual documentation page for details about enabling bridges." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:31 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:22 msgid "Configure bridge permissions (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:33 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:24 msgid "By default any user on your homeserver will be able to use the mautrix bridges. To limit who can use them you would need to configure their permissions settings." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:35 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:26 msgid "Different levels of permission can be granted to users. For example, to **configure a user as an administrator for all bridges**, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:41 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:32 msgid "If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:43 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:34 msgid "**Alternatively** (more verbose, but allows multiple admins to be configured), you can do the same on a per-bridge basis with:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:52 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:43 msgid "This will add the admin permission to the specific user, while keeping the default permissions." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:54 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:45 msgid "You could also redefine the default permissions settings completely, rather than adding extra permissions. You may wish to look at `roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` to find information on the permission settings and other options you would like to configure." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:56 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:47 msgid "Enable encryption (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:58 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:49 msgid "[Encryption (End-to-Bridge Encryption, E2BE) support](https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html) is off by default. If you would like to enable encryption, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:60 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:51 msgid "**for all bridges with encryption support**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:67 -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:86 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:58 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:77 msgid "**Alternatively**, for a specific bridge:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:74 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:65 msgid "Enable relay mode (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:76 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:67 msgid "[Relay mode](https://docs.mau.fi/bridges/general/relay-mode.html) is off by default. Check [the table on the official documentation](https://docs.mau.fi/bridges/general/relay-mode.html#support-table) for bridges which support relay mode." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:78 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:69 msgid "If you would like to enable it, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:80 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:71 msgid "**for all bridges with relay mode support**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:95 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:86 msgid "You can only have one `matrix_mautrix_SERVICENAME_configuration_extension_yaml` definition in `vars.yml` per bridge, so if you need multiple pieces of configuration there, just merge them like this:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:109 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:100 msgid "If you want to activate the relaybot in a room, send `!prefix set-relay` in the rooms where you want to use the bot (replace `!prefix` with the appropriate command prefix for the bridge, like `!signal` or `!wa`). To deactivate, send `!prefix unset-relay`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:111 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:102 msgid "Use `!prefix set-pl 100` to be able for the bot to modify room settings and invite others." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:113 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:104 msgid "Allow anyone on the homeserver to become a relay user (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:115 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:106 msgid "By default, only admins are allowed to set themselves as relay users. To allow anyone on your homeserver to set themselves as relay users, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:121 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:112 msgid "Set the bot's username (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:123 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:114 msgid "To set the bot's username, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:129 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:120 msgid "Configure the logging level (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:131 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:122 msgid "To specify the logging level, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:137 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:128 msgid "Replace `warn` with one of the following to control the verbosity of the logs generated: `trace`, `debug`, `info`, `warn`, `error` or `fatal`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:139 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:130 msgid "If you have issues with a service, and are requesting support, the higher levels of logging (those that appear earlier in the list, like `trace`) will generally be more helpful." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:141 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:132 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:143 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:134 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:145 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:136 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:147 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:138 msgid "`roles/custom/matrix-bridge-mautrix-SERVICENAME/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:148 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:139 msgid "`roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_mautrix_SERVICENAME_configuration_extension_yaml` variable" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:150 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:141 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:152 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:143 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:159 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:150 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:190 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:152 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:154 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-bridges.md:161 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:156 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:163 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:158 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:165 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:160 msgid "To use the bridge, you need to start a chat with `@SERVICENAMEbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:167 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:162 msgid "For details about the next steps, refer to each bridge's individual documentation page." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:169 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:164 msgid "Send `help` to the bot to see the available commands." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:171 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:166 msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:173 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:168 msgid "Set up Double Puppeting (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:175 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:170 msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:177 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:172 msgid "To set it up, you have 2 ways of going about it." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:179 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:174 msgid "Method 1: automatically, by enabling Appservice Double Puppet (recommended)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:181 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:176 msgid "To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html), you could enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:183 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:178 msgid "Appservice Double Puppet is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:185 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:180 msgid "To enable the Appservice Double Puppet service, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:191 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:186 msgid "When enabled, double puppeting will automatically be enabled for all bridges that support double puppeting via the appservice method." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:193 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:188 msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:195 -msgid "**Notes**:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:197 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:192 msgid "Previously there were multiple different automatic double puppeting methods like one with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but they have been superseded by this Appservice Double Puppet method. Double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future as the older methods were completely removed in the megabridge rewrites on [the upstream project](https://docs.mau.fi/bridges/general/double-puppeting.html#automatically)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:200 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:195 msgid "Some bridges like [the deprecated Facebook mautrix bridge](configuring-playbook-bridge-mautrix-facebook.md) and [matrix-appservice-kakaotalk](configuring-playbook-bridge-appservice-kakaotalk.md), which is partially based on the Facebook bridge, are compatible with the Shared Secret Auth service only. These bridges automatically perform Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:202 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:197 msgid "Method 2: manually, by asking each user to provide a working access token" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:204 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:199 msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:206 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:201 msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:208 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:203 msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:210 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:205 msgid "make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:212 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:207 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:214 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:209 msgid "For troubleshooting information with a specific bridge, please see the playbook documentation about it (some other document in in `docs/`) and the upstream ([mautrix](https://github.com/mautrix)) bridge documentation for that specific bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:216 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:211 msgid "If the bridge's bot doesn't accept the invite to a chat, refer [the official troubleshooting page](https://docs.mau.fi/bridges/general/troubleshooting.html) as well." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:218 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:213 msgid "If you found bugs in mautrix bridges, they should be reported to the upstream project, in the corresponding mautrix repository, not to us." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po index 3adb58a71..c1dcab03c 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:13 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:1 msgid "Setting up Mautrix Discord bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:15 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:17 -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." +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:5 +msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md) bridges supported by the playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:19 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:6 +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:7 +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:9 msgid "The playbook can install and configure [mautrix-discord](https://github.com/mautrix/discord) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:21 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:11 msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/discord/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:23 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:13 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)." +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:15 +msgid "There are 2 ways to login to discord using this bridge, either by [scanning a QR code](#method-1-login-using-qr-code-recommended) using the Discord mobile app **or** by using a [Discord token](#method-2-login-using-discord-token-not-recommended)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:27 -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)." +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:17 +msgid "If this is a dealbreaker for you, consider using one of the other Discord bridges supported by the playbook: [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) or [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md). These come with their own complexity and limitations, however, so we recommend that you proceed with this one if possible." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:29 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:19 msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:31 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:21 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:33 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:23 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:35 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:25 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:37 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:27 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:39 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:29 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:45 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:35 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:47 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:37 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:50 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:40 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:52 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:42 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:54 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:44 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:61 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:51 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:53 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:55 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md: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." +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:57 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:65 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:59 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:67 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:61 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:69 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:63 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:71 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:65 msgid "After logging in, the bridge will create portal rooms for some recent direct messages." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:73 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:67 msgid "Bridge guilds" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:75 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:69 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:77 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:71 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:79 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:73 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 "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 "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 ` 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 "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 "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po index 6018ba5a4..a754a7611 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,24 +19,144 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:16 -msgid "Setting up Mautrix Facebook bridging (optional, removed)" +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:1 +msgid "Setting up Mautrix Facebook bridging (optional, deprecated)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:18 -msgid "🪦 The playbook used to be able to install and configure [mautrix-facebook](https://github.com/mautrix/facebook), but no longer includes this component, as it has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge." +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:3 +msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:20 -msgid "The mautrix-meta bridge can be [installed using this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md)." +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:5 +msgid "**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md). Consider using that bridge instead of this one." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:22 -msgid "Uninstalling the bridge manually" +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:7 +msgid "The playbook can install and configure [mautrix-facebook](https://github.com/mautrix/facebook) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:24 -msgid "If you still have the bridge 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:" +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:9 +msgid "See the project's [documentation](https://github.com/mautrix/facebook/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:11 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:13 +msgid "Enable Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:15 +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:17 +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-facebook.md:19 +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-facebook.md:21 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:23 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:29 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:31 +msgid "There are some additional things you may wish to configure about the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:33 +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-facebook.md:35 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:37 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:44 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:46 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:48 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:50 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:52 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:54 +msgid "To use the bridge, you need to start a chat with `@facebookbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:56 +msgid "You then need to send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable bridging for your Facebook Messenger account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:58 +msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:60 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:62 +msgid "Facebook rejecting login attempts and forcing you to change password" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:64 +msgid "If your Matrix server is in a wildly different location than where you usually use your Facebook account from, the bridge's login attempts may be outright rejected by Facebook. Along with that, Facebook may even force you to change the account's password." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:66 +msgid "If you happen to run into this problem while [setting up bridging](#usage), try to first get a successful session up by logging in to Facebook through the Matrix server's IP address." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:68 +msgid "The easiest way to do this may be to use [sshuttle](https://sshuttle.readthedocs.io/) to proxy your traffic through the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:70 +msgid "Example command for proxying your traffic through the Matrix server:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:76 +msgid "Once connected, you should be able to verify that you're browsing the web through the Matrix server's IP by checking [icanhazip](https://icanhazip.com/)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:78 +msgid "Then proceed to log in to [Facebook/Messenger](https://www.facebook.com/)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:80 +msgid "Once logged in, proceed to [set up bridging](#usage)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:82 +msgid "If that doesn't work, enable 2FA (see: [Facebook help page on enabling 2FA](https://www.facebook.com/help/148233965247823)) and try to login again with a new password, and entering the 2FA code when prompted, it may take more then one try, in between attempts, check facebook.com to see if they are requiring another password change" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po index bb4604c9e..020d2ce6f 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,104 +19,96 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:9 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:1 msgid "Setting up Mautrix Google Messages bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:11 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:13 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:5 msgid "The playbook can install and configure [mautrix-gmessages](https://github.com/mautrix/gmessages) for you, for bridging to [Google Messages](https://messages.google.com/)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:15 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:7 msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/gmessages/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:17 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:9 msgid "Prerequisite (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:19 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:11 msgid "Enable Appservice Double Puppet" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:21 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:13 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:23 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:15 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-gmessages.md:25 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:27 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:19 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:33 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:25 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:35 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:27 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:38 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:30 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-gmessages.md:40 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:32 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:42 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:34 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:49 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:41 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:43 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md: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-bridge-mautrix-gmessages.md:51 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.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-bridge-mautrix-gmessages.md:53 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:49 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:55 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:51 msgid "To use the bridge, you need to start a chat with `@gmessagesbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:57 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:53 msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/gmessages/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:59 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:55 msgid "After logging in, the bridge will create portal rooms for recent chats." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:61 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:63 -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-gmessages`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:65 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:67 -msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po index 7ac196a0a..100f63349 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,108 +19,100 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:10 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:1 msgid "Setting up Mautrix Google Chat bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:12 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:14 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:5 msgid "The playbook can install and configure [mautrix-googlechat](https://github.com/mautrix/googlechat) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:16 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:7 msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/googlechat/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:18 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:9 msgid "Prerequisite (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:20 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:11 msgid "Enable Appservice Double Puppet or Shared Secret Auth" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:22 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:13 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:24 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:15 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-googlechat.md:26 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:17 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-googlechat.md:28 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:19 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:30 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:21 msgid "To enable the [Google Chat](https://chat.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:36 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:27 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:38 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:29 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:41 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:32 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-googlechat.md:43 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:34 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:45 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:36 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:52 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:54 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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-googlechat.md:56 -msgid "Usage" +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:43 +msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:58 -msgid "To use the bridge, you need to start a chat with `@googlechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:45 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:60 -msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html)." +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:47 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:62 -msgid "After logging in, the bridge will create portal rooms for recent chats. Portal rooms for other chats will be created as you receive messages." +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:49 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:64 -msgid "Troubleshooting" +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:51 +msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:66 -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-googlechat`." +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:53 +msgid "To use the bridge, you need to start a chat with `@googlechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:68 -msgid "Increase logging verbosity" +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:55 +msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:70 -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-googlechat.md:57 +msgid "After logging in, the bridge will create portal rooms for some recent chats. Portal rooms for other chats will be created as you receive messages." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po index 14ae29f2c..94a7ef2fe 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,24 +19,104 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:1 +msgid "Setting up Mautrix Hangouts bridging (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:3 +msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:5 +msgid "💡 **Note**: This bridge has been deprecated in favor of [Google Chat bridge](https://github.com/mautrix/googlechat), which can be installed using [this playbook](configuring-playbook-bridge-mautrix-googlechat.md). Installing the mautrix-hangouts bridge is **no longer possible**. For now, this documentation page remains here for historical purposes." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:7 +msgid "The playbook can install and configure [mautrix-hangouts](https://github.com/mautrix/hangouts) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:9 +msgid "Prerequisite (optional)" +msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:11 -msgid "Setting up Mautrix Hangouts bridging (optional, removed)" +msgid "Enable Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:13 -msgid "🪦 The playbook used to be able to install and configure [mautrix-hangouts](https://github.com/mautrix/hangouts), but no longer includes this component, because Google Hangouts has been discontinued since the 1st of November 2022." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:15 -msgid "You may wish to use the [Google Chat bridge](https://github.com/mautrix/googlechat) instead." +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-hangouts.md:17 -msgid "Uninstalling the bridge manually" +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-hangouts.md:19 -msgid "If you still have the Hangouts bridge 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:" +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:21 +msgid "To enable the [Google Hangouts](https://hangouts.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:27 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:29 +msgid "There are some additional things you may wish to configure about the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:31 +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-hangouts.md:33 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:35 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:42 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:44 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:46 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:48 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:50 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:52 +msgid "To use the bridge, you need to start a chat with `@hangoutsbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:54 +msgid "You then need to send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:56 +msgid "Automatic login may not work. If it does not, reload the page and select the \"Manual login\" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:58 +msgid "Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po index 9980996b8..5aaa43c3f 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,24 +19,80 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:17 -msgid "Setting up Mautrix Instagram bridging (optional, removed)" +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:1 +msgid "Setting up Mautrix Instagram bridging (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:3 +msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:5 +msgid "**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-instagram.md). Consider using that bridge instead of this one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:7 +msgid "The playbook can install and configure [mautrix-instagram](https://github.com/mautrix/instagram) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:9 +msgid "See the project's [documentation](https://github.com/mautrix/instagram/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:13 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:19 -msgid "🪦 The playbook used to be able to install and configure [mautrix-instagram](https://github.com/mautrix/instagram), but no longer includes this component, as it has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge." +msgid "Extending the configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:21 -msgid "The mautrix-meta bridge can be [installed using this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md)." +msgid "There are some additional things you may wish to configure about the bridge." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:23 -msgid "Uninstalling the bridge manually" +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-instagram.md:25 -msgid "If you still have the bridge 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:" +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:27 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:34 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:36 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:38 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:40 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:42 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:44 +msgid "To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:46 +msgid "You then need to send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the bridge bot to enable bridging for your instagram/Messenger account." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po index d41e4bec6..1a8b08caf 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,140 +19,132 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:8 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:1 msgid "Setting up Instagram bridging via Mautrix Meta (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:10 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:12 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:5 msgid "The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:14 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:7 msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/meta/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:16 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:9 msgid "Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:18 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:11 msgid "This documentation page only deals with the bridge's ability to bridge to Instagram. For bridging to Facebook/Messenger, see [Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:20 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:13 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:22 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:15 msgid "Migrating from the old mautrix-instagram bridge" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:24 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:17 msgid "If you've been using the [mautrix-instagram](./configuring-playbook-bridge-mautrix-instagram.md) bridge, **you'd better get rid of it first** or the 2 bridges will be in conflict:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:26 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:19 msgid "both trying to use `@instagrambot:example.com` as their username. This conflict may be resolved by adjusting `matrix_mautrix_instagram_appservice_bot_username` or `matrix_mautrix_meta_instagram_appservice_username`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:27 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:20 msgid "both trying to bridge the same DMs" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:29 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:22 msgid "To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@instagrambot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:31 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:24 msgid "Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:33 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:26 msgid "Enable Appservice Double Puppet (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:35 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.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-meta-instagram.md:37 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.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-meta-instagram.md:39 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:32 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:41 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.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-meta-instagram.md:47 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:40 msgid "Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:49 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:42 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:51 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:44 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:53 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:46 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-meta-instagram.md:55 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:48 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:57 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:50 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:64 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:57 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:59 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md: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-meta-instagram.md:66 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:63 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:68 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:65 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:70 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:67 msgid "To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:72 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:69 msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/meta/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:74 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:71 msgid "After logging in, the bridge will sync recent chats." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:76 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:78 -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-meta-instagram`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:80 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:82 -msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po index 88a537600..649c08c4c 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,172 +19,164 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:9 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:1 msgid "Setting up Messenger bridging via Mautrix Meta (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:11 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:13 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:5 msgid "The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:15 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:7 msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/meta/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:17 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:9 msgid "Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:19 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:11 msgid "This documentation page only deals with the bridge's ability to bridge to Facebook Messenger. For bridging to Instagram, see [Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:21 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:13 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:23 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:15 msgid "Migrating from the old mautrix-facebook bridge" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:25 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:17 msgid "If you've been using the [mautrix-facebook](./configuring-playbook-bridge-mautrix-facebook.md) bridge, it's possible to migrate the database using [instructions from the bridge documentation](https://docs.mau.fi/bridges/go/meta/facebook-migration.html) (advanced)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:27 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:19 msgid "Then you may wish to get rid of the Facebook bridge. To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@facebookbot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:29 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:21 msgid "Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:31 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:23 msgid "**Note**: the user ID of the new bridge bot is `@messengerbot:example.com`, not `@facebookbot:example.com`. After disabling the old bridge, its bot user will stop responding to a command." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:33 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:25 msgid "Enable Appservice Double Puppet (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:35 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:27 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:37 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:29 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-meta-messenger.md:39 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:31 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:41 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:33 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:47 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:39 msgid "Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:49 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:41 msgid "Bridge mode" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:51 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:43 msgid "As mentioned above, the [mautrix-meta](https://github.com/mautrix/meta) bridge supports multiple modes of operation." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:53 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:45 msgid "The bridge can pull your Messenger messages via 3 different methods:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:55 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:47 msgid "(`facebook`) Facebook via `facebook.com`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:56 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:48 msgid "(`facebook-tor`) Facebook via `facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion` ([Tor](https://www.torproject.org/)) — does not currently proxy media downloads" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:57 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:49 msgid "(default) (`messenger`) Messenger via `messenger.com` — usable even without a Facebook account" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:59 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:51 msgid "You may switch the mode via the `matrix_mautrix_meta_messenger_meta_mode` variable. The playbook defaults to the `messenger` mode, because it's most universal (every Facebook user has a Messenger account, but the opposite is not true)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:61 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:53 msgid "Note that switching the mode (especially between `facebook*` and `messenger`) will intentionally make the bridge use another database (`matrix_mautrix_meta_facebook` or `matrix_mautrix_meta_messenger`) to isolate the 2 instances. Switching between Tor and non-Tor may be possible without dataloss, but your mileage may vary. Before switching to a new mode, you may wish to de-configure the old one (send `help` to the bridge bot and unbridge your portals, etc.)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:63 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:55 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:65 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:57 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:67 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:59 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-meta-messenger.md:69 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:61 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:71 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:63 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:78 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:70 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:72 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:74 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:80 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:76 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:82 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:78 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:84 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:80 msgid "To use the bridge, you need to start a chat with `@messengerbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). Note that the user ID of the bridge's bot is not `@facebookbot:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:86 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:82 msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/meta/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:88 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:84 msgid "After logging in, the bridge will sync recent chats." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:90 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:86 msgid "**Note**: given that the bot is configured in `messenger` [bridge mode](#bridge-mode) by default, you will need to log in to [messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain the cookies from there." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:92 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.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-mautrix-meta-messenger`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:96 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:98 -msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po index e127b0bcd..b847e16f6 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,120 +19,112 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:17 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:1 msgid "Setting up Mautrix Signal bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:19 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:21 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:5 msgid "The playbook can install and configure [mautrix-signal](https://github.com/mautrix/signal) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:23 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:7 msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/signal/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:25 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:9 msgid "Prerequisites (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:27 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:11 msgid "Prepare Postgres database on external Postgres server" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:29 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:13 msgid "If you're running with the Postgres database server integrated by the playbook (which is the default), you don't need to do anything special and can easily proceed with installing." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:31 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:15 msgid "However, if you're [using an external Postgres server](configuring-playbook-external-postgres.md), you'd need to manually prepare a Postgres database for this bridge and adjust the variables related to that (`matrix_mautrix_signal_database_*`)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:33 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:17 msgid "Enable Appservice Double Puppet" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:35 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:19 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:37 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:21 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-signal.md:39 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:23 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:41 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:25 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:47 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:31 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:49 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:33 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:51 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:35 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-signal.md:53 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:37 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:55 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:39 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:62 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:46 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:48 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:50 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:64 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:52 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:66 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:54 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:68 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:56 msgid "To use the bridge, you need to start a chat with `@signalbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:70 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:58 msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/signal/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:72 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:60 msgid "After logging in, the bridge will bridge chats as you receive messages." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:74 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:62 msgid "**Note**: Signal does not support any kind of message history (even on official apps), so the bridge won't backfill any messages." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:76 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:78 -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-signal`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:80 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:82 -msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po index 13e34157a..0d278fc45 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,86 +19,106 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:10 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:1 msgid "Setting up Mautrix Slack bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:12 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:14 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:5 +msgid "**Note**: bridging to [Slack](https://slack.com/) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:6 +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:7 +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:9 msgid "The playbook can install and configure [mautrix-slack](https://github.com/mautrix/slack) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:16 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:11 msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/slack/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:18 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:13 msgid "See the [features and roadmap](https://github.com/mautrix/slack/blob/main/ROADMAP.md) for more information." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:20 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:15 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:22 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:17 msgid "For using this bridge, you would need to authenticate by **providing your username and password** (legacy) or by using a **token login**. See more information in the [docs](https://docs.mau.fi/bridges/go/slack/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:24 -msgid "Note that neither of these methods are officially supported by Slack." +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:19 +msgid "Note that neither of these methods are officially supported by Slack. [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) uses a Slack bot account which is the only officially supported method for bridging a Slack channel." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:26 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:21 msgid "Enable Appservice Double Puppet (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:28 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:23 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:30 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:25 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:32 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:27 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:34 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:29 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:40 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:35 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:42 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:37 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../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." +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:40 +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-slack.md:46 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:42 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:48 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:44 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:51 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:53 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + #: ../../../docs/configuring-playbook-bridge-mautrix-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: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." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:59 @@ -116,19 +136,3 @@ msgstr "" #: ../../../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:67 -msgid "Troubleshooting" -msgstr "" - -#: ../../../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:71 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../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 "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po index 9e8a46992..96b9a5961 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,156 +19,145 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:14 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:1 msgid "Setting up Mautrix Telegram bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:16 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:18 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:5 msgid "The playbook can install and configure [mautrix-telegram](https://github.com/mautrix/telegram) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:20 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:7 msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/telegram/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:22 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:9 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:24 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:11 msgid "Obtain a Telegram API key" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:26 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:13 msgid "To use the bridge, you'd need to obtain an API key from [https://my.telegram.org/apps](https://my.telegram.org/apps)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:28 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:15 msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:30 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:17 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:32 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:19 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-telegram.md:34 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:21 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:81 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:36 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:23 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 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:25 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 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:27 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:42 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:29 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:37 msgid "Relaying" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:52 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:39 msgid "Enable relay-bot (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:54 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:41 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:51 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:53 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 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:55 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 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:57 msgid "Use the bridge for direct chats only (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:72 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:59 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:65 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:80 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:67 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:70 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:72 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:87 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:74 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:83 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:85 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:96 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:87 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:98 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:89 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:100 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:91 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 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:93 msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/telegram/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:104 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:95 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." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:106 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:108 -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 -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:" -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po index 8ef99f728..9853453b6 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,104 +19,100 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:10 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:1 msgid "Setting up Mautrix Twitter bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:12 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:14 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:5 +msgid "**Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md) bridge supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:7 msgid "The playbook can install and configure [mautrix-twitter](https://github.com/mautrix/twitter) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:16 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:9 msgid "See the project's [documentation](https://github.com/mautrix/twitter/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:18 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:11 msgid "Prerequisite (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:20 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:13 msgid "Enable Appservice Double Puppet" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:22 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:15 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:24 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:17 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-twitter.md:26 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:19 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:28 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:21 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:27 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:29 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:39 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:32 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-twitter.md:41 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:43 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:50 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:52 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:54 -msgid "Usage" +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:43 +msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:56 -msgid "To use the bridge, you need to start a chat with `@twitterbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:45 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:58 -msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/twitter/authentication.html)." +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:47 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:60 -msgid "After logging in, the bridge will create portal rooms for recent chats. Portal rooms for other chats will be created as you receive messages." +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:49 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:62 -msgid "Troubleshooting" +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:51 +msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:64 -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-twitter`." +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:53 +msgid "To use the bridge, you need to start a chat with `@twitterbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:66 -msgid "Increase logging verbosity" +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:55 +msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/twitter/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:68 -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:" +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:57 +msgid "After logging in, the bridge will create portal rooms for some recent chats. Portal rooms for other chats will be created as you receive messages." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po index b803902aa..de3864cf0 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,112 +19,104 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:14 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:1 msgid "Setting up Mautrix Whatsapp bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:16 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:18 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:5 msgid "The playbook can install and configure [mautrix-whatsapp](https://github.com/mautrix/whatsapp) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:20 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:7 msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/whatsapp/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:22 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:9 msgid "Prerequisite (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:24 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:11 msgid "Enable Appservice Double Puppet or Shared Secret Auth" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:26 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:13 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:28 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:15 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-whatsapp.md:30 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:17 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-whatsapp.md:32 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:19 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:34 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:21 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:40 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:27 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:42 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:29 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:44 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:31 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-whatsapp.md:46 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:33 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:48 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:35 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:55 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:42 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:44 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:46 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md: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." +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:48 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:59 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:50 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:61 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:52 msgid "To use the bridge, you need to start a chat with `@whatsappbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:63 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:54 msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/whatsapp/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:65 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:56 msgid "Approximately in a minute after logging in, the bridge will create portal rooms for recent chats." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:67 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:58 msgid "**Note**: your linked devices will be logged out if you don’t use your phone for over 14 days (see the official FAQ entry [here](https://faq.whatsapp.com/general/download-and-installation/about-linked-devices)). The bridge will warn you if it doesn't receive any data from the phone over 12 days." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:69 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:71 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-whatsapp`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:73 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:75 -msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po index 719ad3eca..83fa145ed 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,104 +19,104 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:9 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:1 msgid "Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:11 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:13 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:5 msgid "The playbook can install and configure [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:15 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:7 msgid "See the project's [documentation](https://github.com/mautrix/wsproxy/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:17 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:9 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:19 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:11 msgid "By default, this playbook installs wsproxy on the `wsproxy.` subdomain (`wsproxy.example.com`) and requires you to create a CNAME record for `wsproxy`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:21 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:13 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:23 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:15 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:25 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:17 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:37 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:29 msgid "Note that the tokens must match what is compiled into the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android device." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:39 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:31 msgid "Adjusting the wsproxy URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:41 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:33 msgid "By tweaking the `matrix_mautrix_wsproxy_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:43 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:35 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:50 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:42 msgid "After changing the domain, **you may need to adjust your DNS** records to point the wsproxy domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:52 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:44 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:54 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:46 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:56 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:48 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-wsproxy.md:58 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:50 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:60 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:52 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:67 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:59 +msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.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." +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:61 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:71 -msgid "Usage" +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:63 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:73 -msgid "Follow the [mautrix-imessage documentation](https://docs.mau.fi/bridges/go/imessage/index.html) for running `android-sms` and/or `matrix-imessage` on your device(s)." +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:65 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:75 -msgid "Troubleshooting" +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:67 +msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:77 -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-wsproxy`." +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:69 +msgid "Follow the [mautrix-imessage documenation](https://docs.mau.fi/bridges/go/imessage/index.html) for running `android-sms` and/or `matrix-imessage` on your device(s)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po index ea908b76b..38262cd43 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po @@ -10,7 +10,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: 2024-12-20 23:17+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,24 +19,84 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:15 -msgid "Setting up MX Puppet Discord bridging (optional, removed)" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:1 +msgid "Setting up MX Puppet Discord bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:17 -msgid "🪦 The playbook used to be able to install and configure [mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord), but no longer includes this component, as it has been unmaintained for a long time." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:3 +msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md)and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:4 +msgid "For using as a Bot we recommend the [Appservice Discord](configuring-playbook-bridge-appservice-discord.md), because it supports plumbing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:5 +msgid "For personal use with a discord account we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:7 +msgid "The playbook can install and configure [mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:9 +msgid "See the project's [documentation](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:13 +msgid "To enable the [Discord](https://discordapp.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:19 -msgid "You may wish to use the [Mautrix Discord bridge](https://github.com/mautrix/discord) instead." +msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:21 -msgid "Uninstalling the bridge manually" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:28 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:30 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:32 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:34 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:36 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:38 +msgid "To use the bridge, you need to start a chat with `Discord Puppet Bridge` with the handle `@_discordpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:40 +msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-discord [documentation](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) for more information about how to configure the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:42 +msgid "Once logged in, send `list` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:44 +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:23 -msgid "If you still have the MX Puppet Discord bridge 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:" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:46 +msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po index d7b8a79d0..ad848ffcb 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po @@ -10,7 +10,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: 2024-12-20 23:17+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,68 +19,76 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:10 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:1 msgid "Setting up MX Puppet GroupMe bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:12 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:3 msgid "The playbook can install and configure [mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:14 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:5 msgid "See the project's [documentation](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:16 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:7 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:18 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:9 msgid "To enable the [GroupMe](https://groupme.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:24 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:15 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:26 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:17 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:33 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:26 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:28 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:35 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:30 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:37 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:32 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:39 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:34 msgid "To use the bridge, you need to start a chat with `GroupMe Puppet Bridge` with the handle `@_groupmepuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:41 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:36 msgid "One authentication method is available." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:43 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:38 msgid "To link your GroupMe account, go to [dev.groupme.com](https://dev.groupme.com/), sign in, and select \"Access Token\" from the top menu. Copy the token and message the bridge with:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:49 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:44 msgid "Once logged in, send `listrooms` to the bot user to list the available rooms." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:51 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:46 msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:53 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:48 msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po index 9b8d2c76c..918c8fe79 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po @@ -10,7 +10,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: 2024-12-20 23:17+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,24 +19,88 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:14 -msgid "Setting up MX Puppet Instagram bridging (optional, removed)" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:1 +msgid "Setting up MX Puppet Instagram bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:16 -msgid "🪦 The playbook used to be able to install and configure [mx-puppet-instagram](https://gitlab.com/mx-puppet/instagram/mx-puppet-instagram), but no longer includes this component, as it has been unmaintained for a long time." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:3 +msgid "The playbook can install and configure [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:18 -msgid "You may wish to use the [Mautrix Meta](https://github.com/mautrix/meta) Messenger/Instagram bridge instead." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:5 +msgid "This allows you to bridge Instagram DirectMessages into Matrix." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:20 -msgid "Uninstalling the bridge manually" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:7 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:22 -msgid "If you still have the MX Puppet Instagram bridge 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:" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:9 +msgid "To enable the [Instagram](https://www.instagram.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:17 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:26 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:28 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:30 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:34 +msgid "To use the bridge, you need to start a chat with `Instagram Puppet Bridge` with the handle `@_instagrampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:36 +msgid "Send `link ` to the bridge bot to link your instagram account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:38 +msgid "The `list` commands shows which accounts are linked and which `puppetId` is associated." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:40 +msgid "For double-puppeting, you probably want to issue these commands:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:42 +msgid "`settype $puppetId puppet` to enable puppeting for the link (instead of relaying)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:43 +msgid "`setautoinvite $puppetId 1` to automatically invite you to chats" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:44 +msgid "`setmatrixtoken $accessToken` to set the access token to enable puppeting from the other side (the \"double\" in double puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:46 +msgid "If you are linking only one Instagram account, your `$puppetId` is probably 1, but use the `list` command find out." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:48 +msgid "Send `help` to the bot to see the available commands. At the time of writing, not every command is fully implemented." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po index 4fa949e9e..97456fc18 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,16 +19,16 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:9 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:1 msgid "Setting up MX Puppet Skype bridging (optional, removed)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:11 -msgid "🪦 The playbook used to be able to install and configure [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype), but no longer includes this component, because it has been broken and unmaintained for a long time." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:3 +msgid "The playbook used to be able to install and configure [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype), but no longer includes this component, because it has been broken and unmaintained for a long time." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:13 -msgid "The playbook used to be able to install and configure [go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md) as alternative to this bridge, but no longer includes this component, because Skype has been discontinued since May 2025." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:5 +msgid "Bridging to [Skype](https://www.skype.com/) can also happen via the [go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md) bridge supported by the playbook." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po index 3d044c003..67ae99b1e 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po @@ -8,31 +8,91 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2026-02-13 10:32+0000\n" +"POT-Creation-Date: 2024-12-20 23:17+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:17 -msgid "Setting up MX Puppet Slack bridging (optional, removed)" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:1 +msgid "Setting up MX Puppet Slack bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:19 -msgid "🪦 The playbook used to be able to install and configure [mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack), but no longer includes this component, as it has been unmaintained for a long time." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:3 +msgid "**Note**: bridging to [Slack](https://slack.com) can also happen via the [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook. Note that `matrix-appservice-slack` is not available for new installation unless you have already created a classic Slack application, because the creation of classic Slack applications, which this bridge makes use of, has been discontinued." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:21 -msgid "You may wish to use the [Mautrix Slack bridge](https://github.com/mautrix/slack) instead." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:5 +msgid "The playbook can install and configure [mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:23 -msgid "Uninstalling the bridge manually" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:7 +msgid "See the project's [documentation](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:25 -msgid "If you still have the MX Puppet Slack bridge 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:" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:9 +msgid "Prerequisite" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:11 +msgid "Follow the [OAuth credentials](https://gitlab.com/mx-puppet/slack/mx-puppet-slack#option-2-oauth) instructions to create a new Slack app, setting the redirect URL to `https://matrix.example.com/slack/oauth`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:15 +msgid "To enable the [Slack](https://slack.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:24 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:26 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:33 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:35 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:37 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:39 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:41 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:43 +msgid "To use the bridge, you need to start a chat with `Slack Puppet Bridge` with the handle `@_slackpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:45 +msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-slack [documentation](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for more information about how to configure the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:47 +msgid "Once logged in, send `list` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:49 +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:51 +msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po index 190c0add5..4ece71ba6 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po @@ -10,7 +10,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: 2024-12-20 23:17+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,68 +19,72 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:10 -msgid "Setting up MX Puppet Steam bridging (optional, deprecated)" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:1 +msgid "Setting up MX Puppet Steam bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:12 -msgid "**Note**: This bridge has been deprecated in favor of the [matrix-steam-bridge](https://github.com/jasonlaguidice/matrix-steam-bridge) bridge for Steam, which can be [installed using this playbook](configuring-playbook-bridge-steam.md). Consider using that bridge instead of this one." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:3 +msgid "The playbook can install and configure [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:14 -msgid "The playbook can install and configure [mx-puppet-steam](https://codeberg.org/icewind/mx-puppet-steam) for you." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:5 +msgid "See the project's [documentation](https://github.com/icewind1991/mx-puppet-steam/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:16 -msgid "See the project's [documentation](https://codeberg.org/icewind/mx-puppet-steam/blob/master/README.md) to learn what it does and why it might be useful to you." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:18 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:7 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:20 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:9 msgid "To enable the [Steam](https://steampowered.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:26 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:15 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:28 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:17 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:35 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:26 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:28 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:37 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:30 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:39 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:32 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:41 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:34 msgid "To use the bridge, you need to start a chat with `Steam Puppet Bridge` with the handle `@_steampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:43 -msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-steam [documentation](https://codeberg.org/icewind/mx-puppet-steam) for more information about how to configure the bridge." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:36 +msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-steam [documentation](https://github.com/icewind1991/mx-puppet-steam) for more information about how to configure the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:45 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:38 msgid "Once logged in, send `list` to the bot user to list the available rooms." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:47 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:40 msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:49 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:42 msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po index 2a5a91be5..904abfeac 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po @@ -10,7 +10,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: 2024-12-20 23:17+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,24 +19,84 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:1 +msgid "Setting up MX Puppet Twitter bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:3 +msgid "**Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mautrix-twitter](configuring-playbook-bridge-mautrix-twitter.md) bridge supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:5 +msgid "The playbook can install and configure [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:7 +msgid "See the project's [documentation](https://github.com/Sorunome/mx-puppet-twitter/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:9 +msgid "Prerequisite" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:11 +msgid "Make an app on [developer.twitter.com](https://developer.twitter.com/en/apps)." +msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:13 -msgid "Setting up MX Puppet Twitter bridging (optional, removed)" +msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:15 -msgid "🪦 The playbook used to be able to install and configure [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter), but no longer includes this component, as it has been unmaintained for a long time." +msgid "To enable the [Twitter](https://twitter.com) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:26 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:28 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:35 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:37 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:39 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:41 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:43 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:45 +msgid "To use the bridge, you need to start a chat with `Twitter Puppet Bridge` with the handle `@_twitterpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:47 +msgid "To log in, use `link` and click the link." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:17 -msgid "You may wish to use the [Mautrix Twitter bridge](https://github.com/mautrix/twitter) instead." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:49 +msgid "Once logged in, send `list` to the bot user to list the available rooms." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:19 -msgid "Uninstalling the bridge manually" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:51 +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:21 -msgid "If you still have the MX Puppet Twitter bridge 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:" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:53 +msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-steam.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-steam.po deleted file mode 100644 index 5829042e5..000000000 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-steam.po +++ /dev/null @@ -1,90 +0,0 @@ -# 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 , 2026. -# -#, fuzzy -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" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: bg\n" -"Language-Team: bg \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-bridge-steam.md:7 -msgid "Setting up Steam bridging (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:9 -msgid "The playbook can install and configure [matrix-steam-bridge](https://github.com/jasonlaguidice/matrix-steam-bridge) for you." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:11 -msgid "See the project's [documentation](https://github.com/jasonlaguidice/matrix-steam-bridge/blob/main/README.md) to learn what it does and why it might be useful to you." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:13 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:15 -msgid "To enable the [Steam](https://steampowered.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:21 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:23 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:30 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` and `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:32 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:34 -msgid "The tag for `just` commands for this bridge is `matrix-steam-bridge` - for example: `just install-service matrix-steam-bridge`" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:36 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:38 -msgid "To use the bridge, you need to start a chat with `Steam bridge bot` with the handle `@steambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:40 -msgid "The bridge supports QR code and password-based login as well as SteamGuard codes via app, SMS, or e-mail. See matrix-steam-bridge [documentation](https://github.com/jasonlaguidice/matrix-steam-bridge) for more information about how to configure the bridge." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:42 -msgid "To login, send `login [flow ID]` where possible flow IDs are `password` or `qr`" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:44 -msgid "Once logged in, send `search [name]` to search through recognized Steam friends. You can send a user name, display name, or all forms of Steam ID. Send `start-chat [identifier]` to request the bridge bot to open a chat room with a user." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:46 -msgid "Chat rooms will automatically be opened as new messages are received." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:48 -msgid "Send `help` to the bot to see the available commands." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po index 51c9f4764..cc56d8907 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,96 +19,60 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-wechat.md:8 +#: ../../../docs/configuring-playbook-bridge-wechat.md:1 msgid "Setting up WeChat bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:10 +#: ../../../docs/configuring-playbook-bridge-wechat.md:3 msgid "The playbook can install and configure [matrix-wechat](https://github.com/duo/matrix-wechat) for you, for bridging to [WeChat](https://www.wechat.com/)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:12 +#: ../../../docs/configuring-playbook-bridge-wechat.md:5 msgid "See the project's [documentation](https://github.com/duo/matrix-wechat/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:14 -msgid "[!WARNING] This bridge does not work against newer versions of Synapse anymore. See [this issue](https://github.com/duo/matrix-wechat/issues/33). Don't even bother installing it. Unless bridge maintenance is resumed and fixes this issue, we have no choice but to remove it from the playbook." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:17 +#: ../../../docs/configuring-playbook-bridge-wechat.md:7 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:19 +#: ../../../docs/configuring-playbook-bridge-wechat.md:9 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:25 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:27 -msgid "There are some additional things you may wish to configure about the bridge." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:29 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:31 -msgid "`roles/custom/matrix-bridge-wechat/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:32 -msgid "`roles/custom/matrix-bridge-wechat/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_wechat_configuration_extension_yaml` variable" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:34 +#: ../../../docs/configuring-playbook-bridge-wechat.md:15 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:36 +#: ../../../docs/configuring-playbook-bridge-wechat.md:17 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:43 +#: ../../../docs/configuring-playbook-bridge-wechat.md:24 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:45 +#: ../../../docs/configuring-playbook-bridge-wechat.md:26 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:28 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:47 +#: ../../../docs/configuring-playbook-bridge-wechat.md:30 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:49 +#: ../../../docs/configuring-playbook-bridge-wechat.md:32 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:51 +#: ../../../docs/configuring-playbook-bridge-wechat.md:34 msgid "To use the bridge, you need to start a chat with `@wechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:53 +#: ../../../docs/configuring-playbook-bridge-wechat.md:36 msgid "Send `help` to the bot to see the available commands." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:55 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:57 -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-wechat`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:59 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:61 -msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po index ef9f4e4a9..0463b83d5 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,180 +19,188 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-cactus-comments.md:10 +#: ../../../docs/configuring-playbook-cactus-comments.md:1 msgid "Setting up Cactus Comments (optional)" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:12 +#: ../../../docs/configuring-playbook-cactus-comments.md:3 msgid "The playbook can install and configure the [Cactus Comments](https://cactus.chat) system for you." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:14 +#: ../../../docs/configuring-playbook-cactus-comments.md:5 msgid "Cactus Comments is a **federated comment system** built on Matrix. It respects your privacy, and puts you in control." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:16 +#: ../../../docs/configuring-playbook-cactus-comments.md:7 msgid "See the project's [documentation](https://cactus.chat/docs/getting-started/introduction/) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:18 +#: ../../../docs/configuring-playbook-cactus-comments.md:9 msgid "The playbook contains 2 roles for configuring different pieces of the Cactus Comments system:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:20 +#: ../../../docs/configuring-playbook-cactus-comments.md:11 msgid "`matrix-cactus-comments` — the backend appservice integrating with the Matrix homeserver" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:22 +#: ../../../docs/configuring-playbook-cactus-comments.md:13 msgid "`matrix-cactus-comments-client` — a static website server serving the [cactus-client](https://cactus.chat/docs/client/introduction/) static assets (`cactus.js` and `styles.css`)" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:24 +#: ../../../docs/configuring-playbook-cactus-comments.md:15 msgid "You can enable whichever component you need (typically both)." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:26 +#: ../../../docs/configuring-playbook-cactus-comments.md:17 msgid "Adjusting DNS records (optional)" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:28 +#: ../../../docs/configuring-playbook-cactus-comments.md:19 msgid "By default, this playbook installs Cactus Comments' client on the `matrix.` subdomain, at the `/cactus-comments` path (https://matrix.example.com/cactus-comments). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:30 +#: ../../../docs/configuring-playbook-cactus-comments.md:21 msgid "If you wish to adjust it, see the section [below](#adjusting-the-cactus-comments-client-url-optional) for details about DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:32 +#: ../../../docs/configuring-playbook-cactus-comments.md:23 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:34 +#: ../../../docs/configuring-playbook-cactus-comments.md:25 msgid "To enable Cactus Comments, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:54 +#: ../../../docs/configuring-playbook-cactus-comments.md:45 msgid "Adjusting the Cactus Comments' client URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:56 +#: ../../../docs/configuring-playbook-cactus-comments.md:47 msgid "By tweaking the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:58 +#: ../../../docs/configuring-playbook-cactus-comments.md:49 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:67 +#: ../../../docs/configuring-playbook-cactus-comments.md:58 msgid "If you've changed the default hostname, you may need to create a CNAME record for the Cactus Comments' client domain (`cactus.example.com`), which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:69 +#: ../../../docs/configuring-playbook-cactus-comments.md:60 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:71 +#: ../../../docs/configuring-playbook-cactus-comments.md:62 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:73 +#: ../../../docs/configuring-playbook-cactus-comments.md:64 msgid "There are some additional things you may wish to configure about the components." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:75 +#: ../../../docs/configuring-playbook-cactus-comments.md:66 msgid "For `matrix-cactus-comments`, take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:77 +#: ../../../docs/configuring-playbook-cactus-comments.md:68 msgid "`roles/custom/matrix-cactus-comments/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:79 +#: ../../../docs/configuring-playbook-cactus-comments.md:70 msgid "For `matrix-cactus-comments-client`, take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:81 +#: ../../../docs/configuring-playbook-cactus-comments.md:72 msgid "`roles/custom/matrix-cactus-comments-client/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:83 +#: ../../../docs/configuring-playbook-cactus-comments.md:74 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:85 +#: ../../../docs/configuring-playbook-cactus-comments.md:76 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:92 +#: ../../../docs/configuring-playbook-cactus-comments.md:83 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:85 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:87 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:94 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-cactus-comments.md:89 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:96 +#: ../../../docs/configuring-playbook-cactus-comments.md:91 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:98 +#: ../../../docs/configuring-playbook-cactus-comments.md:93 msgid "To use the component, you need to start a chat with `@bot.cactusbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:100 +#: ../../../docs/configuring-playbook-cactus-comments.md:95 msgid "Then, register a site by sending `register YOUR_SITE_NAME_HERE` (where `YOUR_SITE_NAME_HERE` is a unique identifier you choose. It does not have to match your domain). You will then be invited into a moderation room." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:102 +#: ../../../docs/configuring-playbook-cactus-comments.md:97 msgid "Now you are good to go and can embed the comment section on your website!" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:104 +#: ../../../docs/configuring-playbook-cactus-comments.md:99 msgid "Embed Cactus Comments" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:106 +#: ../../../docs/configuring-playbook-cactus-comments.md:101 msgid "The official [documentation](https://cactus.chat/docs/getting-started/quick-start/) provides a useful guide to embed Cactus Comments on your website." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:108 +#: ../../../docs/configuring-playbook-cactus-comments.md:103 msgid "After including the JavaScript and CSS asset files, insert a `
` where you'd like to display the comment section:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:114 +#: ../../../docs/configuring-playbook-cactus-comments.md:109 msgid "Then, you need to initialize the comment section. Make sure to replace `example.com` with your base domain and `YOUR_SITE_NAME_HERE` with the one that has been registered above:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:128 +#: ../../../docs/configuring-playbook-cactus-comments.md:123 msgid "Adjust the domain name for self-hosting" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:130 +#: ../../../docs/configuring-playbook-cactus-comments.md:125 msgid "To have the assets served from your homeserver (not from `cactus.chat`), you need to adjust the domain name on the official documentation." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:132 +#: ../../../docs/configuring-playbook-cactus-comments.md:127 msgid "Make sure to replace `example.com` with your base domain before you include the following lines, instead of the one provided by the official documentation:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:139 +#: ../../../docs/configuring-playbook-cactus-comments.md:134 msgid "**Note**: if the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_path_prefix` variables are tweaked, you would need to adjust the URLs of the assets accordingly." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:141 +#: ../../../docs/configuring-playbook-cactus-comments.md:136 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:143 +#: ../../../docs/configuring-playbook-cactus-comments.md:138 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-cactus-comments` for the backend appservice or `journalctl -fu matrix-cactus-comments-client` for the server serving the client assets, respectively." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:145 +#: ../../../docs/configuring-playbook-cactus-comments.md:140 msgid "Increase logging verbosity" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:147 +#: ../../../docs/configuring-playbook-cactus-comments.md:142 msgid "It is possible to increase logging verbosity for `matrix-cactus-comments-client`. The default logging level for this component is `error`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-cinny.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-cinny.po index 288ed6ae8..c0dde38c1 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-cinny.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-cinny.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,108 +19,80 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-client-cinny.md:9 +#: ../../../docs/configuring-playbook-client-cinny.md:1 msgid "Setting up Cinny (optional)" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:11 +#: ../../../docs/configuring-playbook-client-cinny.md:3 msgid "The playbook can install and configure the [Cinny](https://github.com/ajbura/cinny) Matrix web client for you." msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:13 +#: ../../../docs/configuring-playbook-client-cinny.md:5 msgid "Cinny is a web client focusing primarily on simple, elegant and secure interface. It can be installed alongside or instead of [Element Web](./configuring-playbook-client-element-web.md)." msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:15 +#: ../../../docs/configuring-playbook-client-cinny.md:7 msgid "💡 **Note**: the latest version of Cinny is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting:" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:17 +#: ../../../docs/configuring-playbook-client-cinny.md:9 msgid "[app.cinny.in](https://app.cinny.in), hosted by the [Cinny](https://cinny.in/) developers" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:19 +#: ../../../docs/configuring-playbook-client-cinny.md:11 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:21 +#: ../../../docs/configuring-playbook-client-cinny.md:13 msgid "By default, this playbook installs Cinny on the `cinny.` subdomain (`cinny.example.com`) and requires you to create a CNAME record for `cinny`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:23 +#: ../../../docs/configuring-playbook-client-cinny.md:15 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:25 +#: ../../../docs/configuring-playbook-client-cinny.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:27 +#: ../../../docs/configuring-playbook-client-cinny.md:19 msgid "To enable Cinny, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:33 +#: ../../../docs/configuring-playbook-client-cinny.md:25 msgid "Adjusting the Cinny URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:35 -msgid "By tweaking the `cinny_hostname` variable, you can easily make the service available at a **different hostname** than the default one." +#: ../../../docs/configuring-playbook-client-cinny.md:27 +msgid "By tweaking the `matrix_client_cinny_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:37 +#: ../../../docs/configuring-playbook-client-cinny.md:29 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:47 +#: ../../../docs/configuring-playbook-client-cinny.md:39 msgid "After changing the domain, **you may need to adjust your DNS** records to point the Cinny domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:49 -msgid "**Note**: while there is a `cinny_path_prefix` variable for changing the path where Cinny is served, overriding it is [not possible](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Cinny requires an application rebuild (with a tweaked build config) to be functional under a custom path. You'd need to serve Cinny at a dedicated subdomain." -msgstr "" - -#: ../../../docs/configuring-playbook-client-cinny.md:51 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-client-cinny.md:53 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-client-cinny.md:55 -msgid "Take a look at:" +#: ../../../docs/configuring-playbook-client-cinny.md:41 +msgid "**Note**: while there is a `matrix_client_cinny_path_prefix` variable for changing the path where Cinny is served, overriding it is [not possible](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Cinny requires an application rebuild (with a tweaked build config) to be functional under a custom path. You'd need to serve Cinny at a dedicated subdomain." msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:57 -msgid "`roles/galaxy/cinny/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-client-cinny.md:58 -msgid "`roles/galaxy/cinny/templates/config.json.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `cinny_configuration_extension_json` variable" -msgstr "" - -#: ../../../docs/configuring-playbook-client-cinny.md:60 +#: ../../../docs/configuring-playbook-client-cinny.md:43 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:62 +#: ../../../docs/configuring-playbook-client-cinny.md:45 msgid "After configuring the playbook and [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:69 +#: ../../../docs/configuring-playbook-client-cinny.md:52 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:71 +#: ../../../docs/configuring-playbook-client-cinny.md:54 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-client-cinny.md:73 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-client-cinny.md:75 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-client-cinny`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-element-web.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-element-web.po index 9fae06ea7..eefacd9f8 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-element-web.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-element-web.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,176 +19,152 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-client-element-web.md:11 +#: ../../../docs/configuring-playbook-client-element-web.md:1 msgid "Configuring Element Web (optional)" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:13 +#: ../../../docs/configuring-playbook-client-element-web.md:3 msgid "By default, this playbook installs the [Element Web](https://github.com/element-hq/element-web) Matrix client for you. If that's okay, you can skip this document." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:15 +#: ../../../docs/configuring-playbook-client-element-web.md:5 msgid "If you'd like to stop the playbook installing the client, see the section [below](#disabling-element-web) to check the configuration for disabling it." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:17 +#: ../../../docs/configuring-playbook-client-element-web.md:7 msgid "💡 **Note**: the latest version of Element Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting (by [disabling Element Web](#disabling-element-web)):" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:19 +#: ../../../docs/configuring-playbook-client-element-web.md:9 msgid "[app.element.io](https://app.element.io/), hosted by [Element](https://element.io/)" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:20 +#: ../../../docs/configuring-playbook-client-element-web.md:10 msgid "[app.etke.cc](https://app.etke.cc/), hosted by [etke.cc](https://etke.cc/)" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:22 +#: ../../../docs/configuring-playbook-client-element-web.md:12 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:24 +#: ../../../docs/configuring-playbook-client-element-web.md:14 msgid "By default, this playbook installs Element Web on the `element.` subdomain (`element.example.com`) and requires you to create a CNAME record for `element`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:26 +#: ../../../docs/configuring-playbook-client-element-web.md:16 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:28 +#: ../../../docs/configuring-playbook-client-element-web.md:18 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:30 -msgid "Set the country code for phone number inputs" -msgstr "" - -#: ../../../docs/configuring-playbook-client-element-web.md:32 -msgid "You can change the country code (default: `GB`) to use when showing phone number inputs. To change it to `FR` for example, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-element-web.md:38 +#: ../../../docs/configuring-playbook-client-element-web.md:20 msgid "Themes" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:40 -msgid "Change the default theme" -msgstr "" - -#: ../../../docs/configuring-playbook-client-element-web.md:42 -msgid "You can change the default theme from `light` to `dark`. To do so, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-client-element-web.md:22 +msgid "You can change the look of Element Web by pulling themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project or defining your own themes manually." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:49 +#: ../../../docs/configuring-playbook-client-element-web.md:24 msgid "Use themes by `element-themes`" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:51 -msgid "You can change the look of Element Web by pulling themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project or defining your own themes manually." -msgstr "" - -#: ../../../docs/configuring-playbook-client-element-web.md:53 -msgid "To pull the themes and use them for your Element Web instance, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-client-element-web.md:26 +msgid "To pull the themes from the `element-themes` project and use them for your Element Web instance, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:59 +#: ../../../docs/configuring-playbook-client-element-web.md:32 msgid "If the variable is set to `true`, all themes found in the repository specified with `matrix_client_element_themes_repository_url` will be installed and enabled automatically." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:61 +#: ../../../docs/configuring-playbook-client-element-web.md:34 msgid "Note that for a custom theme to work well, all Element Web instances that you use must have the same theme installed." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:63 +#: ../../../docs/configuring-playbook-client-element-web.md:36 msgid "Define themes manually" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:65 +#: ../../../docs/configuring-playbook-client-element-web.md:38 msgid "You can also define your own themes manually by adding and adjusting the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:72 +#: ../../../docs/configuring-playbook-client-element-web.md:45 msgid "If you define your own themes with it and set `matrix_client_element_themes_enabled` to `true` for the themes by `element-themes`, your themes will be preserved as well." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:74 +#: ../../../docs/configuring-playbook-client-element-web.md:47 msgid "If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:76 +#: ../../../docs/configuring-playbook-client-element-web.md:49 msgid "Adjusting the Element Web URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:78 +#: ../../../docs/configuring-playbook-client-element-web.md:51 msgid "By tweaking the `matrix_client_element_hostname` and `matrix_client_element_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:80 +#: ../../../docs/configuring-playbook-client-element-web.md:53 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:91 +#: ../../../docs/configuring-playbook-client-element-web.md:64 msgid "After changing the domain, **you may need to adjust your DNS** records to point the Element domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:93 +#: ../../../docs/configuring-playbook-client-element-web.md:66 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:95 +#: ../../../docs/configuring-playbook-client-element-web.md:68 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:97 +#: ../../../docs/configuring-playbook-client-element-web.md:70 msgid "There are some additional things you may wish to configure about the component." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:99 +#: ../../../docs/configuring-playbook-client-element-web.md:72 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:101 +#: ../../../docs/configuring-playbook-client-element-web.md:74 msgid "`roles/custom/matrix-client-element/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:102 +#: ../../../docs/configuring-playbook-client-element-web.md:75 msgid "`roles/custom/matrix-client-element/templates/config.json.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_client_element_configuration_extension_json` variable" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:104 +#: ../../../docs/configuring-playbook-client-element-web.md:77 msgid "For example, to override some Element Web settings, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:122 +#: ../../../docs/configuring-playbook-client-element-web.md:95 msgid "Disabling Element Web" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:124 +#: ../../../docs/configuring-playbook-client-element-web.md:97 msgid "If you'd like for the playbook to not install Element Web (or to uninstall it if it was previously installed), add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:130 +#: ../../../docs/configuring-playbook-client-element-web.md:103 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:132 +#: ../../../docs/configuring-playbook-client-element-web.md:105 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:139 +#: ../../../docs/configuring-playbook-client-element-web.md:112 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:141 +#: ../../../docs/configuring-playbook-client-element-web.md:114 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-client-element-web.md:143 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-client-element-web.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-client-element`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-fluffychat-web.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-fluffychat-web.po deleted file mode 100644 index 3dcc4c530..000000000 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-fluffychat-web.po +++ /dev/null @@ -1,106 +0,0 @@ -# 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 , 2026. -# -#, fuzzy -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" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: bg\n" -"Language-Team: bg \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-client-fluffychat-web.md:8 -msgid "Setting up FluffyChat Web (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:10 -msgid "The playbook can install and configure the [FluffyChat Web](https://github.com/krille-chan/fluffychat) Matrix client for you." -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:12 -msgid "FluffyChat Web is a cute cross-platform (web, iOS, Android) messenger for Matrix written in [Flutter](https://flutter.dev/)." -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:14 -msgid "💡 **Note**: the latest version of FluffyChat Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Application, you can consider using it from there:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:16 -msgid "[fluffychat.im](https://fluffychat.im/web), hosted by the [FluffyChat](https://fluffy.chat/) developers" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:18 -msgid "Adjusting DNS records" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:20 -msgid "By default, this playbook installs FluffyChat Web on the `fluffychat.` subdomain (`fluffychat.example.com`) and requires you to create a CNAME record for `fluffychat`, which targets `matrix.example.com`." -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:22 -msgid "When setting, replace `example.com` with your own." -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:24 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:26 -msgid "To enable FluffyChat Web, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:32 -msgid "Adjusting the FluffyChat Web URL (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:34 -msgid "By tweaking the `matrix_client_fluffychat_hostname` and `matrix_client_fluffychat_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:36 -msgid "Example additional configuration for your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:47 -msgid "After changing the domain, **you may need to adjust your DNS** records to point the FluffyChat Web domain to the Matrix server." -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:49 -msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:51 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:53 -msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:60 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:62 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:64 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:66 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-client-fluffychat`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po index ae96b6644..063a8dd81 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,100 +19,72 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-client-hydrogen.md:10 +#: ../../../docs/configuring-playbook-client-hydrogen.md:1 msgid "Setting up Hydrogen (optional)" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:12 +#: ../../../docs/configuring-playbook-client-hydrogen.md:3 msgid "The playbook can install and configure the [Hydrogen](https://github.com/element-hq/hydrogen-web) Matrix web client for you." msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:14 +#: ../../../docs/configuring-playbook-client-hydrogen.md:5 msgid "Hydrogen is a lightweight web client that supports mobile and legacy web browsers. It can be installed alongside or instead of Element Web." msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:16 +#: ../../../docs/configuring-playbook-client-hydrogen.md:7 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:18 +#: ../../../docs/configuring-playbook-client-hydrogen.md:9 msgid "By default, this playbook installs Hydrogen on the `hydrogen.` subdomain (`hydrogen.example.com`) and requires you to create a CNAME record for `hydrogen`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:20 +#: ../../../docs/configuring-playbook-client-hydrogen.md:11 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:22 +#: ../../../docs/configuring-playbook-client-hydrogen.md:13 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:24 +#: ../../../docs/configuring-playbook-client-hydrogen.md:15 msgid "To enable Hydrogen, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:30 +#: ../../../docs/configuring-playbook-client-hydrogen.md:21 msgid "Adjusting the Hydrogen URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:32 -msgid "By tweaking the `hydrogen_hostname` and `hydrogen_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +#: ../../../docs/configuring-playbook-client-hydrogen.md:23 +msgid "By tweaking the `matrix_client_hydrogen_hostname` and `matrix_client_hydrogen_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:34 +#: ../../../docs/configuring-playbook-client-hydrogen.md:25 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:45 +#: ../../../docs/configuring-playbook-client-hydrogen.md:36 msgid "After changing the domain, **you may need to adjust your DNS** records to point the Hydrogen domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:47 +#: ../../../docs/configuring-playbook-client-hydrogen.md:38 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:49 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-client-hydrogen.md:51 -msgid "There are some additional things you may wish to configure about the client." -msgstr "" - -#: ../../../docs/configuring-playbook-client-hydrogen.md:53 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-hydrogen.md:55 -msgid "`roles/galaxy/hydrogen/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-client-hydrogen.md:56 -msgid "`roles/galaxy/hydrogen/templates/config.json.j2` for the client's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `hydrogen_configuration_extension_json` variable" -msgstr "" - -#: ../../../docs/configuring-playbook-client-hydrogen.md:58 +#: ../../../docs/configuring-playbook-client-hydrogen.md:40 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:60 +#: ../../../docs/configuring-playbook-client-hydrogen.md:42 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:67 +#: ../../../docs/configuring-playbook-client-hydrogen.md:49 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:69 +#: ../../../docs/configuring-playbook-client-hydrogen.md:51 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-client-hydrogen.md:71 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-client-hydrogen.md:73 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-client-hydrogen`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-sable.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-sable.po deleted file mode 100644 index a4b8dff3e..000000000 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-sable.po +++ /dev/null @@ -1,118 +0,0 @@ -# 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 , 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 \n" -"Language: bg\n" -"Language-Team: bg \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-client-sable.md:9 -msgid "Setting up Sable (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:11 -msgid "The playbook can install and configure the [Sable](https://github.com/7w1/sable) Matrix web client for you." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:13 -msgid "Sable is a web client focusing primarily on simple, elegant and secure interface. It can be installed alongside or instead of [Element Web](./configuring-playbook-client-element-web.md), [Cinny](./configuring-playbook-client-cinny.md) and others." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:15 -msgid "Adjusting DNS records" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:17 -msgid "By default, this playbook installs Sable on the `sable.` subdomain (`sable.example.com`) and requires you to create a CNAME record for `sable`, which targets `matrix.example.com`." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:19 -msgid "When setting, replace `example.com` with your own." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:21 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:23 -msgid "To enable Sable, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:29 -msgid "Adjusting the Sable URL (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:31 -msgid "By tweaking the `sable_hostname` variable, you can easily make the service available at a **different hostname** than the default one." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:33 -msgid "Example additional configuration for your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:43 -msgid "After changing the domain, **you may need to adjust your DNS** records to point the Sable domain to the Matrix server." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:45 -msgid "**Note**: while there is a `sable_path_prefix` variable for changing the path where Sable is served, overriding it is [not possible](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Sable requires an application rebuild (with a tweaked build config) to be functional under a custom path. You'd need to serve Sable at a dedicated subdomain." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:47 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:49 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:51 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:53 -msgid "`roles/galaxy/sable/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:54 -msgid "`roles/galaxy/sable/templates/config.json.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `sable_configuration_extension_json` variable" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:56 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:58 -msgid "After configuring the playbook and [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:65 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:67 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:69 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:71 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-client-sable`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po index cb108c32f..76b960173 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,168 +19,144 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:9 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:1 msgid "Setting up SchildiChat Web (optional)" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:11 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:3 msgid "The playbook can install and configure the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) Matrix client for you." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:13 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:5 msgid "SchildiChat Web is a feature-rich messenger for Matrix based on Element Web with some extras and tweaks. It can be installed alongside or instead of Element Web." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:15 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:7 msgid "💡 **Note**: the latest version of SchildiChat Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Application, you can consider using it from there:" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:17 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:9 msgid "[app.schildi.chat](https://app.schildi.chat/), hosted by the [SchildiChat](https://schildi.chat/) developers" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:19 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:11 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:21 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:13 msgid "By default, this playbook installs SchildiChat Web on the `schildichat.` subdomain (`schildichat.example.com`) and requires you to create a CNAME record for `schildichat`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:23 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:15 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:25 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:27 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:19 msgid "To enable SchildiChat Web, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:33 -msgid "Set the country code for phone number inputs" -msgstr "" - -#: ../../../docs/configuring-playbook-client-schildichat-web.md:35 -msgid "You can change the country code (default: `GB`) to use when showing phone number inputs. To change it to `FR` for example, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-schildichat-web.md:41 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:25 msgid "Themes" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:43 -msgid "Change the default theme" -msgstr "" - -#: ../../../docs/configuring-playbook-client-schildichat-web.md:45 -msgid "You can change the default theme from `light` to `dark`. To do so, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-client-schildichat-web.md:27 +msgid "You can change the look of SchildiChat Web by pulling themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project or defining your own themes manually." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:52 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:29 msgid "Use themes by `element-themes`" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:54 -msgid "You can change the look of SchildiChat Web by pulling themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project or defining your own themes manually." +#: ../../../docs/configuring-playbook-client-schildichat-web.md:31 +msgid "To pull the themes from the `element-themes` project and use them for your SchildiChat Web instance, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:56 -msgid "To pull the themes and use them for your SchildiChat Web instance, add the following configuration to your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-schildichat-web.md:62 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:37 msgid "If the variable is set to `true`, all themes found in the repository specified with `matrix_client_schildichat_themes_repository_url` will be installed and enabled automatically." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:64 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:39 msgid "Note that for a custom theme to work well, all SchildiChat Web instances that you use must have the same theme installed." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:66 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:41 msgid "Define themes manually" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:68 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:43 msgid "You can also define your own themes manually by adding and adjusting the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:75 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:50 msgid "If you define your own themes with it and set `matrix_client_schildichat_themes_enabled` to `true` for the themes by `element-themes`, your themes will be preserved as well." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:77 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:52 msgid "If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:79 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:54 msgid "Adjusting the SchildiChat Web URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:81 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:56 msgid "By tweaking the `matrix_client_schildichat_hostname` and `matrix_client_schildichat_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:83 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:58 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:94 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:69 msgid "After changing the domain, **you may need to adjust your DNS** records to point the SchildiChat Web domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:96 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:71 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:98 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:73 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:100 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:75 msgid "There are some additional things you may wish to configure about the component." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:102 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:77 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:104 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:79 msgid "`roles/custom/matrix-client-schildichat/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:105 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:80 msgid "`roles/custom/matrix-client-schildichat/templates/config.json.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_client_schildichat_configuration_extension_json` variable" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:107 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:82 msgid "For example, to override some SchildiChat Web settings, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:125 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:100 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:127 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:102 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:134 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:109 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:136 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:111 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-client-schildichat-web.md:138 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-client-schildichat-web.md:140 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-client-schildichat`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduit.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduit.po index 275c83601..816e7dcf6 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduit.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduit.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,120 +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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-conduit.md:8 +#: ../../../docs/configuring-playbook-conduit.md:1 msgid "Configuring Conduit (optional)" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:10 +#: ../../../docs/configuring-playbook-conduit.md:3 msgid "The playbook can install and configure the [Conduit](https://conduit.rs) Matrix server for you." msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:12 +#: ../../../docs/configuring-playbook-conduit.md:5 msgid "See the project's [documentation](https://docs.conduit.rs/) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:14 +#: ../../../docs/configuring-playbook-conduit.md:7 msgid "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." msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:16 -msgid "[!WARNING]" +#: ../../../docs/configuring-playbook-conduit.md:9 +msgid "💡 **Note**: The playbook also supports installing a (currently) faster-moving Conduit fork called [conduwuit](./configuring-playbook-conduwuit.md)." msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:17 +#: ../../../docs/configuring-playbook-conduit.md:11 +msgid "⚠️ **Warnings**:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:13 msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet." msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:18 +#: ../../../docs/configuring-playbook-conduit.md:15 msgid "**Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:20 +#: ../../../docs/configuring-playbook-conduit.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:22 +#: ../../../docs/configuring-playbook-conduit.md:19 msgid "To use Conduit, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below:" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:28 +#: ../../../docs/configuring-playbook-conduit.md:25 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:30 +#: ../../../docs/configuring-playbook-conduit.md:27 msgid "There are some additional things you may wish to configure about the server." msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:32 +#: ../../../docs/configuring-playbook-conduit.md:29 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:34 +#: ../../../docs/configuring-playbook-conduit.md:31 msgid "`roles/custom/matrix-conduit/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:35 +#: ../../../docs/configuring-playbook-conduit.md:32 msgid "`roles/custom/matrix-conduit/templates/conduit.toml.j2` for the server's default configuration" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:37 +#: ../../../docs/configuring-playbook-conduit.md:34 msgid "If you'd like to have your own different configuration, feel free to copy and paste the original files into your inventory (e.g. in `inventory/host_vars/matrix.example.com/`) and then change the specific host's `vars.yml` file like this:" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:43 +#: ../../../docs/configuring-playbook-conduit.md:40 msgid "Creating the first user account" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:45 +#: ../../../docs/configuring-playbook-conduit.md:42 msgid "Since it is difficult to create the first user account on Conduit (see [famedly/conduit#276](https://gitlab.com/famedly/conduit/-/issues/276) and [famedly/conduit#354](https://gitlab.com/famedly/conduit/-/merge_requests/354)) and it does not support [registering users](registering-users.md) (via the command line or via the playbook) like Synapse and Dendrite do, we recommend the following procedure:" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:47 +#: ../../../docs/configuring-playbook-conduit.md:44 msgid "Add `matrix_conduit_allow_registration: true` to your `vars.yml` the first time around, temporarily" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:48 +#: ../../../docs/configuring-playbook-conduit.md:45 msgid "Run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start` — see [Installing](installing.md))" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:49 +#: ../../../docs/configuring-playbook-conduit.md:46 msgid "Create your first user via Element Web or any other client which supports creating users" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:50 +#: ../../../docs/configuring-playbook-conduit.md:47 msgid "Get rid of `matrix_conduit_allow_registration: true` from your `vars.yml`" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:51 +#: ../../../docs/configuring-playbook-conduit.md:48 msgid "Run the playbook again (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-conduit,start` would be enough this time)" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:52 +#: ../../../docs/configuring-playbook-conduit.md:49 msgid "You can now use your server safely. Additional users can be created by messaging the internal Conduit bot" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:54 +#: ../../../docs/configuring-playbook-conduit.md:51 msgid "Configuring bridges / appservices" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:56 +#: ../../../docs/configuring-playbook-conduit.md:53 msgid "For other homeserver implementations (like Synapse and Dendrite), the playbook automatically registers appservices (for bridges, bots, etc.) with the homeserver." msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:58 +#: ../../../docs/configuring-playbook-conduit.md:55 msgid "For Conduit, you will have to manually register appservices using the the [register-appservice](https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.md) command." msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:60 +#: ../../../docs/configuring-playbook-conduit.md:57 msgid "Find the `registration.yaml` in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`, then pass the content to Conduit:" msgstr "" - -#: ../../../docs/configuring-playbook-conduit.md:83 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-conduit.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-conduit`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduwuit.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduwuit.po index 85ca90196..3e74a14ad 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduwuit.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduwuit.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,44 +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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-conduwuit.md:18 -msgid "Configuring conduwuit (optional, removed)" +#: ../../../docs/configuring-playbook-conduwuit.md:1 +msgid "Configuring conduwuit (optional)" msgstr "" -#: ../../../docs/configuring-playbook-conduwuit.md:20 -msgid "🪦 The playbook used to be able to install and configure the [conduwuit](https://conduwuit.puppyirl.gay/) Matrix server, but no longer includes this component, as it's been abandoned and unmaintained." +#: ../../../docs/configuring-playbook-conduwuit.md:3 +msgid "The playbook can install and configure the [conduwuit](https://conduwuit.puppyirl.gay/) Matrix server for you." msgstr "" -#: ../../../docs/configuring-playbook-conduwuit.md:22 -msgid "Uninstalling the service manually" +#: ../../../docs/configuring-playbook-conduwuit.md:5 +msgid "See the project's [documentation](https://conduwuit.puppyirl.gay/) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-conduwuit.md:24 -msgid "If you still have conduwuit installed on your Matrix server, the playbook can no longer help you uninstall it and you will need to do it manually." +#: ../../../docs/configuring-playbook-conduwuit.md:7 +msgid "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." msgstr "" -#: ../../../docs/configuring-playbook-conduwuit.md:26 -msgid "To uninstall the service, run the command below on the server:" +#: ../../../docs/configuring-playbook-conduwuit.md:9 +msgid "💡 **Note**: conduwuit is a fork of [Conduit](./configuring-playbook-conduit.md), which the playbook also supports. See [Differences from upstream Conduit](https://conduwuit.puppyirl.gay/differences.html)." msgstr "" -#: ../../../docs/configuring-playbook-conduwuit.md:32 -msgid "Migrating to Continuwuity" +#: ../../../docs/configuring-playbook-conduwuit.md:11 +msgid "⚠️ **Warnings**:" msgstr "" -#: ../../../docs/configuring-playbook-conduwuit.md:34 -msgid "Since [Continuwuity](configuring-playbook-continuwuity.md) is a drop-in replacement for conduwuit, migration is possible. Please refer to [this section](./configuring-playbook-continuwuity.md#migrating-from-conduwuit) for details." +#: ../../../docs/configuring-playbook-conduwuit.md:13 +msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> conduwuit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet." msgstr "" -#: ../../../docs/configuring-playbook-conduwuit.md:36 -msgid "Removing data manually" +#: ../../../docs/configuring-playbook-conduwuit.md:15 +msgid "**Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding" msgstr "" -#: ../../../docs/configuring-playbook-conduwuit.md:38 -msgid "If you are not going to migrate to [Continuwuity](configuring-playbook-continuwuity.md), you can remove data by running the command on the server:" +#: ../../../docs/configuring-playbook-conduwuit.md:17 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:19 +msgid "To use conduwuit, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:33 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:35 +msgid "There are some additional things you may wish to configure about the server." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:37 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:39 +msgid "`roles/custom/matrix-conduwuit/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:40 +msgid "`roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2` for the server's default configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:42 +msgid "There are various Ansible variables that control settings in the `conduwuit.toml` file." msgstr "" #: ../../../docs/configuring-playbook-conduwuit.md:44 -msgid "[!WARNING] Once you removing the path, there is no going back. Your data on the homeserver (including chat history, rooms, etc.) will be deleted and not be possible to restore them. Please be certain." +msgid "If a specific setting you'd like to change does not have a dedicated Ansible variable, you can either submit a PR to us to add it, or you can [override the setting using an environment variable](https://conduwuit.puppyirl.gay/configuration.html#environment-variables) using `matrix_conduwuit_environment_variables_extension`. For example:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:52 +msgid "Creating the first user account" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:54 +msgid "Unlike other homeserver implementations (like Synapse and Dendrite), conduwuit does not support creating users via the command line or via the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:56 +msgid "If you followed the instructions above (see [Adjusting the playbook configuration](#adjusting-the-playbook-configuration)), you should have registration enabled and protected by a registration token." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:58 +msgid "This should allow you to create the first user account via any client (like [Element Web](./configuring-playbook-client-element-web.md)) which supports creating users." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:60 +msgid "The **first user account that you create will be marked as an admin** and **will be automatically invited to an admin room**." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:63 +msgid "Configuring bridges / appservices" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:65 +msgid "For other homeserver implementations (like Synapse and Dendrite), the playbook automatically registers appservices (for bridges, bots, etc.) with the homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:67 +msgid "For conduwuit, you will have to manually register appservices using the [`!admin appservices register` command](https://conduwuit.puppyirl.gay/appservices.html#set-up-the-appservice---general-instructions) sent to the server bot account." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:69 +msgid "The server's bot account has a Matrix ID of `@conduit:example.com` (not `@conduwuit:example.com`!) due to conduwuit's historical legacy. Your first user account would already have been invited to an admin room with this bot." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:72 +msgid "Find the appservice file you'd like to register. This can be any `registration.yaml` file found in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:74 +msgid "Then, send its content to the existing admin room:" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-continuwuity.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-continuwuity.po index a24d0d69c..8e5129018 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-continuwuity.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-continuwuity.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,148 +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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-continuwuity.md:8 -msgid "Configuring Continuwuity (optional)" +#: ../../../docs/configuring-playbook-continuwuity.md:1 +msgid "Configuring continuwuity (optional)" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:10 -msgid "The playbook can install and configure the [Continuwuity](https://continuwuity.org) Matrix server for you." +#: ../../../docs/configuring-playbook-continuwuity.md:3 +msgid "The playbook can install and configure the [continuwuity](https://continuwuity.org/) Matrix server for you." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:12 -msgid "See the project's [documentation](https://continuwuity.org) to learn what it does and why it might be useful to you." +#: ../../../docs/configuring-playbook-continuwuity.md:5 +msgid "See the project's [documentation](https://continuwuity.org/) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:14 +#: ../../../docs/configuring-playbook-continuwuity.md:7 msgid "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." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:16 -msgid "💡 **Note**: continuwuity is a fork of [conduwuit](./configuring-playbook-conduwuit.md), which the playbook has supported." +#: ../../../docs/configuring-playbook-continuwuity.md:9 +msgid "💡 **Note**: continuwuity is a fork of [conduwuit](./configuring-playbook-conduwuit.md), which the playbook also supports." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:18 -msgid "[!WARNING]" +#: ../../../docs/configuring-playbook-continuwuity.md:11 +msgid "⚠️ **Warnings**:" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:19 -msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Continuwuity). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet." +#: ../../../docs/configuring-playbook-continuwuity.md:13 +msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> continuwuity). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:20 +#: ../../../docs/configuring-playbook-continuwuity.md:15 msgid "**Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:22 +#: ../../../docs/configuring-playbook-continuwuity.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:24 -msgid "To use Continuwuity, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below:" +#: ../../../docs/configuring-playbook-continuwuity.md:19 +msgid "To use continuwuity, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below:" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:38 +#: ../../../docs/configuring-playbook-continuwuity.md:33 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:40 +#: ../../../docs/configuring-playbook-continuwuity.md:35 msgid "There are some additional things you may wish to configure about the server." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:42 +#: ../../../docs/configuring-playbook-continuwuity.md:37 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:44 +#: ../../../docs/configuring-playbook-continuwuity.md:39 msgid "`roles/custom/matrix-continuwuity/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:45 +#: ../../../docs/configuring-playbook-continuwuity.md:40 msgid "`roles/custom/matrix-continuwuity/templates/continuwuity.toml.j2` for the server's default configuration" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:47 +#: ../../../docs/configuring-playbook-continuwuity.md:42 msgid "There are various Ansible variables that control settings in the `continuwuity.toml` file." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:49 +#: ../../../docs/configuring-playbook-continuwuity.md:44 msgid "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:" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:57 +#: ../../../docs/configuring-playbook-continuwuity.md:52 msgid "Creating the first user account" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:59 +#: ../../../docs/configuring-playbook-continuwuity.md:54 msgid "Unlike other homeserver implementations (like Synapse and Dendrite), continuwuity does not support creating users via the command line or via the playbook." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:61 -msgid "On first startup, Continuwuity creates a special one-time-use registration token and logs it to the server's console. To access this, you will need to SSH into the server and run the following command:" +#: ../../../docs/configuring-playbook-continuwuity.md:56 +msgid "If you followed the instructions above (see [Adjusting the playbook configuration](#adjusting-the-playbook-configuration)), you should have registration enabled and protected by a registration token." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:68 -msgid "Find the token, highlight it, and copy it (ctrl+shift+C). This token should allow you to create the first user account via any client (like [Element Web](./configuring-playbook-client-element-web.md)) which supports creating users." +#: ../../../docs/configuring-playbook-continuwuity.md:58 +msgid "This should allow you to create the first user account via any client (like [Element Web](./configuring-playbook-client-element-web.md)) which supports creating users." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:70 +#: ../../../docs/configuring-playbook-continuwuity.md:60 msgid "The **first user account that you create will be marked as an admin** and **will be automatically invited to an admin room**." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:73 +#: ../../../docs/configuring-playbook-continuwuity.md:63 msgid "Configuring bridges / appservices" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:75 +#: ../../../docs/configuring-playbook-continuwuity.md:65 msgid "For other homeserver implementations (like Synapse and Dendrite), the playbook automatically registers appservices (for bridges, bots, etc.) with the homeserver." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:77 -msgid "For continuwuity, you will have to manually register appservices using the [`!admin appservices register` command](https://continuwuity.org/appservices.html#set-up-the-appservice---general-instructions) sent to the server bot account." +#: ../../../docs/configuring-playbook-continuwuity.md:67 +msgid "For continuwuity, you will have to manually register appservices using the [`!admin appservices register` command](https://continuwuity.org/appservices#set-up-the-appservice---general-instructions) sent to the server bot account." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:79 +#: ../../../docs/configuring-playbook-continuwuity.md:69 msgid "The server's bot account has a Matrix ID of `@conduit:example.com` (not `@continuwuity:example.com`!) due to continuwuity's historical legacy. Your first user account would already have been invited to an admin room with this bot." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:82 +#: ../../../docs/configuring-playbook-continuwuity.md:72 msgid "Find the appservice file you'd like to register. This can be any `registration.yaml` file found in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:84 +#: ../../../docs/configuring-playbook-continuwuity.md:74 msgid "Then, send its content to the existing admin room:" msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:108 -msgid "Migrating from conduwuit" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:110 -msgid "Since Continuwuity is a drop-in replacement for [conduwuit](configuring-playbook-conduwuit.md), migration is possible." -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:112 -msgid "Make sure that Continuwuity is properly set up on your `vars.yml` as described above" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:114 -msgid "Make sure that Conduwuit references are removed from your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:116 -msgid "Run the installation in a way that installs new services and uninstalls old ones (e.g. `just setup-all`)" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:118 -msgid "Run the playbook with the `continuwuity-migrate-from-conduwuit` tag (e.g. `just run-tags continuwuity-migrate-from-conduwuit`). This migrates data from `/matrix/conduwuit` to `/matrix/continuwuity`" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:120 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:122 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-continuwuity`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dendrite.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dendrite.po index 6c83f88b4..007da27af 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dendrite.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dendrite.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,96 +19,80 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-dendrite.md:9 +#: ../../../docs/configuring-playbook-dendrite.md:1 msgid "Configuring Dendrite (optional)" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:11 +#: ../../../docs/configuring-playbook-dendrite.md:3 msgid "The playbook can install and configure the [Dendrite](https://github.com/element-hq/dendrite) Matrix server for you." msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:13 +#: ../../../docs/configuring-playbook-dendrite.md:5 msgid "See the project's [documentation](https://element-hq.github.io/dendrite/) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:15 +#: ../../../docs/configuring-playbook-dendrite.md:7 msgid "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." msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:17 -msgid "[!WARNING]" +#: ../../../docs/configuring-playbook-dendrite.md:9 +msgid "⚠️ **Warnings**:" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:18 +#: ../../../docs/configuring-playbook-dendrite.md:11 msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Dendrite). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet." msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:19 +#: ../../../docs/configuring-playbook-dendrite.md:13 msgid "**Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:21 +#: ../../../docs/configuring-playbook-dendrite.md:15 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:23 +#: ../../../docs/configuring-playbook-dendrite.md:17 msgid "To use Dendrite, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below:" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:29 +#: ../../../docs/configuring-playbook-dendrite.md:23 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:31 +#: ../../../docs/configuring-playbook-dendrite.md:25 msgid "There are some additional things you may wish to configure about the server." msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:33 +#: ../../../docs/configuring-playbook-dendrite.md:27 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:35 +#: ../../../docs/configuring-playbook-dendrite.md:29 msgid "`roles/custom/matrix-dendrite/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:36 +#: ../../../docs/configuring-playbook-dendrite.md:30 msgid "`roles/custom/matrix-dendrite/templates/dendrite.yaml.j2` for the server's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_dendrite_configuration_extension_yaml` variable" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:38 +#: ../../../docs/configuring-playbook-dendrite.md:32 msgid "For example, to override some Dendrite settings, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:59 +#: ../../../docs/configuring-playbook-dendrite.md:53 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:61 +#: ../../../docs/configuring-playbook-dendrite.md:55 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:68 +#: ../../../docs/configuring-playbook-dendrite.md:62 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:70 +#: ../../../docs/configuring-playbook-dendrite.md:64 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-dendrite.md:72 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-dendrite.md:74 -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-dendrite`." -msgstr "" - -#: ../../../docs/configuring-playbook-dendrite.md:76 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-dendrite.md:78 -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 "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dimension.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dimension.po index 98e515963..e9d06252e 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dimension.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dimension.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,20 +19,197 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" + +#: ../../../docs/configuring-playbook-dimension.md:1 +msgid "Setting up Dimension integration manager (optional, unmaintained)" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:3 +#: ../../../docs/configuring-playbook-dimension.md:109 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:4 +msgid "Dimension is **[officially unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299)**. We recommend not bothering with installing it." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:5 +msgid "This playbook now supports running Dimension in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:7 +msgid "The playbook can install and configure the [Dimension](https://dimension.t2bot.io) integration manager for you." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:9 +msgid "See the project's [documentation](https://github.com/turt2live/matrix-dimension/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:13 +msgid "Open Matrix Federation port" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:15 +msgid "Enabling the Dimension service will automatically reconfigure your Synapse homeserver to expose the `openid` API endpoints on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. If you enable the component, make sure that the port is accessible." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:17 +msgid "Install Matrix services" +msgstr "" #: ../../../docs/configuring-playbook-dimension.md:19 -msgid "Setting up Dimension integration manager (optional, removed)" +msgid "Dimension can only be installed after Matrix services are installed and running. If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) and come back here later." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:21 -msgid "🪦 The playbook used to be able to install and configure [Dimension](https://dimension.t2bot.io) integration manager, but no longer includes this component, as it has been unmaintained." +msgid "Register a dedicated Matrix user (optional, recommended)" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:23 -msgid "Uninstalling the component manually" +msgid "We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username)." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:25 -msgid "If you still have the Dimension integration manager 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:" +msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:27 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:33 +msgid "Obtain an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:35 +msgid "Dimension requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:37 +msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:40 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:42 +msgid "By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to create a CNAME record for `dimension`, which targets `matrix.example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:44 +msgid "When setting, replace `example.com` with your own." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:46 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:48 +msgid "To enable Dimension, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:56 +msgid "Define admin users" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:58 +msgid "To define admin users who can modify the integrations this Dimension supports, add the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:66 +msgid "The admin interface is accessible within Element Web by accessing it in any room and clicking the cog wheel/settings icon in the top right. Currently, Dimension can be opened in Element Web by the \"Add widgets, bridges, & bots\" link in the room information." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:68 +msgid "Adjusting the Dimension URL (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:70 +msgid "By tweaking the `matrix_dimension_hostname` and `matrix_dimension_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:72 +msgid "Example additional configuration for your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:83 +msgid "After changing the domain, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:85 +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:87 +msgid "**Note**: while there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You'd need to serve Dimension at a dedicated subdomain." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:89 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:91 +msgid "There are some additional things you may wish to configure about the component." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:93 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:95 +msgid "`roles/custom/matrix-dimension/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:96 +msgid "`roles/custom/matrix-dimension/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_dimension_configuration_extension_yaml` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:98 +msgid "You can find all configuration options on [GitHub page of Dimension project](https://github.com/turt2live/matrix-dimension/blob/master/config/default.yaml)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:100 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:102 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:111 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:113 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:115 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:117 +msgid "After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the room info button (`i`) on the top right corner, and then clicking the \"Add widgets, bridges, & bots\" link." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:119 +msgid "Set up a Jitsi widget" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:121 +msgid "By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:123 +msgid "To set up the widget, an admin user needs to configure the domain via the admin UI once Dimension is running. In Element Web, go to *Manage Integrations* → *Settings* → *Widgets* → *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:125 +msgid "There is unfortunately no way to configure the widget via the playbook. See [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po index 899562e9f..e37cf2462 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,116 +19,60 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-dynamic-dns.md:22 +#: ../../../docs/configuring-playbook-dynamic-dns.md:1 msgid "Setting up Dynamic DNS (optional)" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:24 +#: ../../../docs/configuring-playbook-dynamic-dns.md:3 msgid "The playbook can configure Dynamic DNS with [ddclient⁠](https://github.com/ddclient/ddclient) for you. It is a Perl client used to update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider." msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:26 +#: ../../../docs/configuring-playbook-dynamic-dns.md:5 msgid "Most cloud providers / ISPs will charge you extra for a static IP address. If you're not hosting a highly reliable homeserver you can workaround this via dynamic DNS." msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:28 -msgid "For details about configuring the [Ansible role for ddclient](https://github.com/mother-of-all-self-hosting/ansible-role-ddclient), you can check them via:" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:29 -msgid "🌐 [the role's documentation](https://github.com/mother-of-all-self-hosting/ansible-role-ddclient/blob/main/docs/configuring-ddclient.md) online" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:30 -msgid "📁 `roles/galaxy/ddclient/docs/configuring-ddclient.md` locally, if you have [fetched the Ansible roles](../installing.md)" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:32 +#: ../../../docs/configuring-playbook-dynamic-dns.md:7 msgid "Prerequisite" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:34 -msgid "You'll need to authenticate with your DNS provider somehow, in most cases this is simply a username and password but can differ from provider to provider. Please consult with your providers documentation and the upstream [ddclient documentation](https://github.com/ddclient/ddclient/blob/main/ddclient.conf.in) to determine what you'll need to provide to authenticate." +#: ../../../docs/configuring-playbook-dynamic-dns.md:9 +msgid "You'll need to get a username and password from your DNS provider. Please consult with the provider about how to retrieve them." msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:36 +#: ../../../docs/configuring-playbook-dynamic-dns.md:11 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:38 +#: ../../../docs/configuring-playbook-dynamic-dns.md:13 msgid "To enable dynamic DNS, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:51 -msgid "Keep in mind that certain providers may require a different configuration of the `ddclient_domain_configurations` variable, for provider specific examples see the [upstream documentation](https://github.com/ddclient/ddclient/blob/main/ddclient.conf.in)." -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:53 -msgid "Configuring the endpoint to obtain IP address (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:55 -msgid "The playbook sets the default endpoint for obtaining the IP address to `https://cloudflare.com/cdn-cgi/trace`. You can replace it by specifying yours to `ddclient_web` and `ddclient_web_skip` if necessary." -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:57 -msgid "Refer to [this section](https://github.com/mother-of-all-self-hosting/ansible-role-ddclient/blob/main/docs/configuring-ddclient.md#setting-the-endpoint-to-obtain-ip-address-optional) for more information." -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:59 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:61 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:63 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:65 -msgid "`roles/galaxy/ddclient/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:67 +#: ../../../docs/configuring-playbook-dynamic-dns.md:26 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:69 +#: ../../../docs/configuring-playbook-dynamic-dns.md:28 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:76 +#: ../../../docs/configuring-playbook-dynamic-dns.md:35 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:78 +#: ../../../docs/configuring-playbook-dynamic-dns.md:37 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:80 +#: ../../../docs/configuring-playbook-dynamic-dns.md:39 msgid "Additional Reading" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:82 +#: ../../../docs/configuring-playbook-dynamic-dns.md:41 msgid "Additional resources:" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:84 +#: ../../../docs/configuring-playbook-dynamic-dns.md:43 msgid "https://matrix.org/docs/guides/free-small-matrix-server" msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:85 -msgid "https://github.com/linuxserver/docker-ddclient" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:87 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:89 -msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-ddclient/blob/main/docs/configuring-ddclient.md#troubleshooting) on the role's documentation for details." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-element-call.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-element-call.po deleted file mode 100644 index b0124cad8..000000000 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-element-call.po +++ /dev/null @@ -1,250 +0,0 @@ -# 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 , 2026. -# -#, fuzzy -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" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: bg\n" -"Language-Team: bg \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-call.md:8 -msgid "Setting up Element Call (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:10 -msgid "The playbook can install and configure [Element Call](https://github.com/element-hq/element-call) and its supporting components that are part of the [Matrix RTC stack](configuring-playbook-matrix-rtc.md)." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:12 -msgid "Element Call is a native Matrix video conferencing application developed by [Element](https://element.io), designed for secure, scalable, privacy-respecting, and decentralized video and voice calls over the Matrix protocol. Built on MatrixRTC ([MSC4143](https://github.com/matrix-org/matrix-spec-proposals/pull/4143)), it utilizes [MSC4195](https://github.com/hughns/matrix-spec-proposals/blob/hughns/matrixrtc-livekit/proposals/4195-matrixrtc-livekit.md) with [LiveKit Server](configuring-playbook-livekit-server.md) as its backend." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:14 -msgid "See the project's [documentation](https://github.com/element-hq/element-call) to learn more." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:16 -msgid "Prerequisites" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:18 -msgid "A [Synapse](configuring-playbook-synapse.md) homeserver (see the warning below)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:19 -msgid "The [Matrix RTC (Real-Time Communication) stack](configuring-playbook-matrix-rtc.md) (automatically done when Element Call is enabled)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:20 -msgid "A client compatible with Element Call. As of 2025-03-15, that's just [Element Web](configuring-playbook-client-element-web.md) and the Element X mobile clients (iOS and Android)." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:21 -msgid "(Optional) Guest accounts being enabled for your Matrix server, if you'd like guests to be able to use Element Call. See [Allowing guests to use Element Call](#allowing-guests-to-use-element-call-optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:23 -msgid "[!WARNING] Because Element Call [requires](https://github.com/element-hq/element-call/blob/93ae2aed9841e0b066d515c56bd4c122d2b591b2/docs/self-hosting.md#a-matrix-homeserver) a few experimental features in the Matrix protocol, it's **very likely that it only works with the Synapse homeserver**." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:26 -msgid "Decide between Element Call vs just the Matrix RTC stack" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:28 -msgid "All clients that can currently use Element Call (Element Web and Element X on mobile) already embed the Element Call frontend within them. These **clients will use their own embedded Element Call frontend**, so **self-hosting the Element Call frontend by the playbook is largely unnecessary**." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:31 -msgid "💡 A reason you may wish to continue installing the Element Call frontend (despite Matrix clients not making use of it), is if you need to use it standalone - directly via a browser (without a Matrix client). Note that unless you [allow guest accounts to use Element Call](#allowing-guests-to-use-element-call-optional), you will still need a Matrix user account **on the same homeserver** to be able to use Element Call." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:33 -msgid "The playbook makes a distinction between enabling Element Call (`matrix_element_call_enabled`) and enabling the Matrix RTC Stack (`matrix_rtc_enabled`). Enabling Element Call automatically enables the Matrix RTC stack. Because installing the Element Call frontend is now unnecessary, **we recommend only installing the Matrix RTC stack, without the Element Call frontend**." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "Description / Variable" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "Element Call frontend" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "[LiveKit Server](configuring-playbook-livekit-server.md)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "[LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "Description" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "Static website that provides the Element Call UI (but often embedded by clients)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "Scalable, multi-user conferencing solution based on WebRTC" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "A helper component that allows Element Call to integrate with LiveKit Server" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "Required for Element Call to function" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "No" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "Yes" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "`matrix_element_call_enabled`" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "✅ Installed" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "`matrix_rtc_enabled`" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "❌ Not Installed, but usually unnecessary" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:42 -msgid "All documentation below assumes that you've decided to install Element Call and not just the Matrix RTC stack." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:44 -msgid "Decide on a domain and path" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:46 -msgid "By default, the Element Call frontend is configured to be served on the `call.element.example.com` domain." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:48 -msgid "If you'd like to run Element Call on another hostname, see the [Adjusting the Element Call URL](#adjusting-the-element-call-url-optional) section below." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:50 -msgid "Adjusting DNS records" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:52 -msgid "By default, this playbook installs Element Call on the `call.element.` subdomain (`call.element.example.com`) and requires you to create a `CNAME` record for `call.element`, which targets `matrix.example.com`." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:54 -msgid "When setting these values, replace `example.com` with your own." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:56 -msgid "All dependency services for Element Call ([LiveKit Server](configuring-playbook-livekit-server.md) and [Livekit JWT Service](configuring-playbook-livekit-jwt-service.md)) are installed and configured automatically by the playbook. By default, these services are installed on subpaths on the `matrix.` domain (e.g. `/livekit-server`, `/livekit-jwt-service`), so no DNS record adjustments are required for them." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:58 -msgid "Adjusting firewall rules" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:60 -msgid "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." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:62 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:64 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:72 -msgid "Adjusting the Element Call URL (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:74 -msgid "By tweaking the `matrix_element_call_hostname` variable, you can easily make the service available at a **different hostname** than the default one." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:76 -msgid "Example additional configuration for your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:82 -msgid "[!WARNING] A `matrix_element_call_path_prefix` variable is also available and mean to let you configure a path prefix for the Element Call service, but [Element Call does not support running under a sub-path yet](https://github.com/element-hq/element-call/issues/3084)." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:85 -msgid "Allowing guests to use Element Call (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:87 -msgid "By default, Element Call can only be used by people having accounts on your Matrix server." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:89 -msgid "If you'd like guests to be able to use Element Call as well, you need to enable guest accounts support for your homeserver." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:91 -msgid "[!WARNING] Enabling guest accounts means that your homeserver's user database may get polluted with guest account signups (potentially made by bots). Guest accounts should be limited in what (damage) they can do to your server and the rest of the Matrix ecosystem, but it's better to not enable them unless necessary." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:95 -msgid "For [Synapse](configuring-playbook-synapse.md) (the default homeserver implementation), the configuration is like this:" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:101 -msgid "For [Dendrite](configuring-playbook-dendrite.md), the configuration is like this:" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:107 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:109 -msgid "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:" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:116 -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-call.md:118 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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-element-call.md:120 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:122 -msgid "Once installed, Element Call integrates seamlessly with Matrix clients like [Element Web](configuring-playbook-client-element-web.md) and Element X on mobile (iOS and Android)." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email.po index 7b94c5085..a7212a3c9 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,136 +19,76 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-email.md:10 +#: ../../../docs/configuring-playbook-email.md:1 msgid "Adjusting email-sending settings (optional)" msgstr "" -#: ../../../docs/configuring-playbook-email.md:12 -msgid "By default, this playbook sets up an [Exim](https://www.exim.org/) relay SMTP mailer service (powered by [exim-relay](https://github.com/devture/exim-relay) and the [ansible-role-exim-relay](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay) Ansible role), through which all Matrix services send emails." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:14 -msgid "**With the default setting, exim-relay attempts to deliver emails directly with the address `matrix@matrix.example.com`**, as specified by the `exim_relay_sender_address` playbook variable. See below if you want to configure the playbook to relay email through another SMTP server." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:16 -msgid "The [Ansible role for exim-relay](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring exim-relay, you can check them via:" +#: ../../../docs/configuring-playbook-email.md:3 +msgid "By default, this playbook sets up an [Exim](https://www.exim.org/) email server through which all Matrix services send emails." msgstr "" -#: ../../../docs/configuring-playbook-email.md:17 -msgid "🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md) online" +#: ../../../docs/configuring-playbook-email.md:5 +msgid "The email server would attempt to deliver emails directly to their final destination. This may or may not work, depending on your domain configuration (SPF settings, etc.)" msgstr "" -#: ../../../docs/configuring-playbook-email.md:18 -msgid "📁 `roles/galaxy/exim_relay/docs/configuring-exim-relay.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" +#: ../../../docs/configuring-playbook-email.md:7 +msgid "By default, emails are sent from `matrix@matrix.example.com`, as specified by the `exim_relay_sender_address` playbook variable." msgstr "" -#: ../../../docs/configuring-playbook-email.md:20 -msgid "Why use exim-relay?" +#: ../../../docs/configuring-playbook-email.md:9 +msgid "[!WARNING] On some cloud providers (Google Cloud, etc.), [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible. You will need to [relay email through another SMTP server](#relaying-email-through-another-smtp-server)." msgstr "" -#: ../../../docs/configuring-playbook-email.md:22 -msgid "**Benefits of using exim-relay** instead of configuring SMTP directly in each service:" +#: ../../../docs/configuring-playbook-email.md:12 +msgid "💡 To improve deliverability, we recommend [relaying email through another SMTP server](#relaying-email-through-another-smtp-server) anyway." msgstr "" -#: ../../../docs/configuring-playbook-email.md:24 -msgid "**Final delivery capability**: Can deliver emails directly if you don't have an SMTP server" +#: ../../../docs/configuring-playbook-email.md:14 +msgid "Firewall settings" msgstr "" -#: ../../../docs/configuring-playbook-email.md:26 -msgid "**Centralized configuration**: Configure your upstream SMTP server once in exim-relay, then point all services ([Synapse](configuring-playbook-synapse.md), [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), etc.) there—no need to configure SMTP in each component" +#: ../../../docs/configuring-playbook-email.md:16 +msgid "No matter whether you send email directly (the default) or you relay email through another host (see how below), you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration)." msgstr "" -#: ../../../docs/configuring-playbook-email.md:28 -msgid "**Local spooling**: Stores messages locally and retries delivery if your upstream SMTP server is temporarily unavailable" +#: ../../../docs/configuring-playbook-email.md:18 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-email.md:30 -msgid "Firewall settings" +#: ../../../docs/configuring-playbook-email.md:20 +msgid "Relaying email through another SMTP server" msgstr "" -#: ../../../docs/configuring-playbook-email.md:32 -msgid "No matter whether you send email directly (the default) or you relay email through another host, you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration)." +#: ../../../docs/configuring-playbook-email.md:22 +msgid "If you'd like to relay email through another SMTP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-email.md:34 -msgid "Docker automatically opens these ports in the server's firewall, so you likely don't need to do anything. If you use another firewall in front of the server, you may need to adjust it." +msgid "**Note**: only the secure submission protocol (using `STARTTLS`, usually on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port `465`) **is not supported**." msgstr "" #: ../../../docs/configuring-playbook-email.md:36 -msgid "Adjusting the playbook configuration" +msgid "Sending emails using Sendgrid" msgstr "" #: ../../../docs/configuring-playbook-email.md:38 -msgid "Enable DKIM authentication to improve deliverability (optional)" +msgid "An easy and free SMTP service to set up is [Sendgrid](https://sendgrid.com/). Its free tier allows for up to 100 emails per day to be sent." msgstr "" #: ../../../docs/configuring-playbook-email.md:40 -msgid "By default, exim-relay attempts to deliver emails directly. This may or may not work, depending on your domain configuration." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:42 -msgid "To improve email deliverability, you can configure authentication methods such as DKIM (DomainKeys Identified Mail), SPF, and DMARC for your domain. Without setting any of these authentication methods, your outgoing email is most likely to be quarantined as spam at recipient's mail servers." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:44 -msgid "For details about configuring DKIM, refer [this section](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md#enable-dkim-support-optional) on the role's documentation." +msgid "To set it up, add the following configuration to your `vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-email.md:46 -msgid "💡 If you cannot enable DKIM, SPF, or DMARC on your domain for some reason, we recommend relaying email through another SMTP server." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:48 -msgid "Relaying email through another SMTP server (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:50 -msgid "**On some cloud providers such as Google Cloud, [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible.** In this case, you will need to relay email through another SMTP server." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:52 -msgid "For details about configuration, refer [this section](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md#relaying-email-through-another-smtp-server) on the role's document." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:54 -msgid "Disable mail service (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:56 -msgid "For a low-power server you might probably want to disable exim-relay. To do so, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:62 -msgid "Note that disabling exim-relay will stop email-notifications and other similar functions from working." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:64 -msgid "See [this entry on the FAQ](faq.md#how-do-i-optimize-this-setup-for-a-low-power-server) for other possible optimizations for a low-power server." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:66 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:68 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:75 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:77 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-email.md:57 +msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-email.md:79 -msgid "Troubleshooting" +#: ../../../docs/configuring-playbook-email.md:59 +msgid "If you're having trouble with email not being delivered, it may be useful to inspect the mailer logs." msgstr "" -#: ../../../docs/configuring-playbook-email.md:81 -msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md#troubleshooting) on the role's documentation for details." +#: ../../../docs/configuring-playbook-email.md:61 +msgid "To do so, log in to the server with SSH and run `journalctl -f -u matrix-exim-relay`." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po index 3ae5fc004..baf25b3ba 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,24 +19,260 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" + +#: ../../../docs/configuring-playbook-email2matrix.md:1 +msgid "Setting up Email2Matrix (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:3 +msgid "**Note**: this component has been deprecated. We recommend not bothering with installing it. While not a 1:1 replacement, 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). Consider using that component instead of this one." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:5 +msgid "The playbook can install and configure [Email2Matrix](https://github.com/devture/email2matrix) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:7 +msgid "See the project's [documentation](https://github.com/devture/email2matrix/blob/master/docs/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:9 +msgid "Preparation" +msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:11 -msgid "Setting up Email2Matrix (optional, removed)" +msgid "Port availability" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:13 -msgid "🪦 The playbook used to be able to install and configure [Email2Matrix](https://github.com/devture/email2matrix), but no longer includes this component." +msgid "Ensure that port 25 is available on your Matrix server and open in your firewall." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:15 -msgid "For a long time now, it been replaced by the much better and more maintained [Postmoogle](https://github.com/etkecc/postmoogle) bridge, which can also be [installed using this playbook](configuring-playbook-bridge-postmoogle.md)." +msgid "If you have `postfix` or some other email server software installed, you may need to manually remove it first (unless you need it, of course)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:17 +msgid "If you really need to run an email server on the Matrix machine for other purposes, it may be possible to run Email2Matrix on another port (with a configuration like `matrix_email2matrix_smtp_host_bind_port: \"127.0.0.01:2525\"`) and have your other email server relay messages there." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:19 +msgid "For details about using Email2Matrix alongside [Postfix](http://www.postfix.org/), see [here](https://github.com/devture/email2matrix/blob/master/docs/setup_with_postfix.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:21 +msgid "Register a dedicated Matrix user (optional, recommended)" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:23 +msgid "We recommend that you create a dedicated Matrix user for Email2Matrix." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:25 +msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:27 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:33 +msgid "Take note of the user's ID as it needs to be specified as `MatrixUserId` on your `inventory/host_vars/matrix.example.com/vars.yml` file later." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:35 +msgid "Obtain an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:37 +msgid "Email2Matrix requires an access token for the sender user to be able to send messages to the room. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:39 +msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:42 +msgid "Join to rooms as the sender user manually" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:44 +msgid "ℹ️ **Email2Matrix does not accept room invitations automatically**. To deliver messages to rooms, the sender user must be joined to all rooms manually." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:46 +msgid "For each new room you would like the user to deliver messages to, invite the user to the room." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:48 +msgid "Then, log in as the sender user using any Matrix client of your choosing, accept the room invitation from the user's account." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:50 +msgid "Make sure that you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there, then log out." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:52 +msgid "Take note of each room's room ID (different clients show the room ID in a different place). You'll need the room ID when [configuring the playbook](#adjusting-the-playbook-configuration) below." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:54 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:56 +msgid "To increase the chances that incoming emails reach your server, you can set up a `MX` record for `matrix.example.com` that looks like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "Type" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "Host" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "Priority" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "Weight" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "Port" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "Target" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "MX" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "`matrix`" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "10" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "0" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "-" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "`matrix.example.com`" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:62 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:64 +msgid "To enable Email2Matrix, add the following configuration to your `vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE` and `ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE` with the ones created [above](#obtain-an-access-token)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:90 +msgid "where:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:92 +msgid "MailboxName — local-part of the email address, through which emails are bridged to the room whose ID is defined with MatrixRoomId" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:93 +msgid "MatrixRoomId — internal ID of the room, to which received emails are sent as Matrix message" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:94 +msgid "MatrixHomeserverUrl — URL of your Matrix homeserver, through which to send Matrix messages. You can also set `MatrixHomeserverUrl` to the container URL where your homeserver's Client-Server API lives by using the `{{ matrix_addons_homeserver_client_api_url }}` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:95 +msgid "MatrixUserId — the full ID of the sender user which sends bridged messages to the room. On this configuration it is `@email2matrix1:example.com` and `@email2matrix2:example.com` (where `example.com` is your base domain, not the `matrix.` domain)" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:96 +msgid "MatrixAccessToken — sender user's access token" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:97 +msgid "IgnoreSubject — if set to \"true\", the subject is not bridged to Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:98 +msgid "IgnoreBody — if set to \"true\", the message body is not bridged to Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:99 +msgid "SkipMarkdown — if set to \"true\", emails are bridged as plain text Matrix message instead of Markdown (actually HTML)" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:101 +msgid "Refer to the official documentation [here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:103 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:105 +msgid "There are some additional things you may wish to configure about the component." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:107 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:109 +msgid "`roles/custom/matrix-email2matrix/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:111 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:113 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:120 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:122 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service email2matrix` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:124 +msgid "`just install-service email2matrix` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:126 +msgid "After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:128 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:130 +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-email2matrix`." msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:18 -msgid "Uninstalling Email2Matrix manually" +#: ../../../docs/configuring-playbook-email2matrix.md:132 +msgid "Increase logging verbosity" msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:20 -msgid "If you still have the Email2Matrix component installed on your Matrix server, the playbook can no longer help you uninstall it and you will need to do it manually. To uninstall manually, run these commands on the server:" +#: ../../../docs/configuring-playbook-email2matrix.md:134 +msgid "If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-etherpad.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-etherpad.po index 5f4946b29..11e08ff3e 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-etherpad.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-etherpad.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,148 +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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-etherpad.md:13 +#: ../../../docs/configuring-playbook-etherpad.md:1 msgid "Setting up Etherpad (optional)" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:15 +#: ../../../docs/configuring-playbook-etherpad.md:3 msgid "The playbook can install and configure [Etherpad](https://etherpad.org) for you." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:17 +#: ../../../docs/configuring-playbook-etherpad.md:5 msgid "Etherpad is an open source collaborative text editor. It can not only be integrated with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS) as a widget, but also be used as standalone web app." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:19 -msgid "When enabled together with the Jitsi video-conferencing platform (see [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made available as an option during the conferences." +#: ../../../docs/configuring-playbook-etherpad.md:7 +msgid "When enabled together with the Jitsi audio/video conferencing system (see [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made available as an option during the conferences." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:21 -msgid "The [Ansible role for Etherpad](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring Etherpad, you can check them via:" +#: ../../../docs/configuring-playbook-etherpad.md:9 +msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:23 -msgid "🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md) online" +#: ../../../docs/configuring-playbook-etherpad.md:11 +msgid "By default, this playbook installs Etherpad on the `etherpad.` subdomain (`etherpad.example.com`) and requires you to create a CNAME record for `etherpad`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:24 -msgid "📁 `roles/galaxy/etherpad/docs/configuring-etherpad.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" +#: ../../../docs/configuring-playbook-etherpad.md:13 +msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:26 -msgid "Adjusting DNS records" +#: ../../../docs/configuring-playbook-etherpad.md:15 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:28 -msgid "By default, this playbook installs Etherpad on the `etherpad.` subdomain (`etherpad.example.com`) and requires you to create a CNAME record for `etherpad`, which targets `matrix.example.com`." +#: ../../../docs/configuring-playbook-etherpad.md:17 +msgid "To enable Etherpad, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:30 -msgid "When setting, replace `example.com` with your own." +#: ../../../docs/configuring-playbook-etherpad.md:27 +msgid "Adjusting the Etherpad URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:32 -msgid "Adjusting the playbook configuration" +#: ../../../docs/configuring-playbook-etherpad.md:29 +msgid "By tweaking the `etherpad_hostname` and `etherpad_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:34 -msgid "To enable Etherpad, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +#: ../../../docs/configuring-playbook-etherpad.md:31 +msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:52 -msgid "As the most of the necessary settings for the role have been taken care of by the playbook, you can enable Etherpad on your Matrix server with this minimum configuration." +#: ../../../docs/configuring-playbook-etherpad.md:42 +msgid "After changing the domain, **you may need to adjust your DNS** records to point the Etherpad domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:54 -msgid "See the role's documentation for details about configuring Etherpad per your preference (such as [the name of the instance](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md#set-the-name-of-the-instance-optional) and [the default pad text](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md#set-the-default-text-optional))." +#: ../../../docs/configuring-playbook-etherpad.md:44 +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:56 -msgid "Create admin user (optional)" +#: ../../../docs/configuring-playbook-etherpad.md:46 +msgid "Configure the default text (optional)" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:58 -msgid "You probably might want to enable authentication to disallow anonymous access to your Etherpad." +#: ../../../docs/configuring-playbook-etherpad.md:48 +msgid "You can also edit the default text on a new pad with the variable `etherpad_default_pad_text`." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:60 -msgid "It is possible to enable HTTP basic authentication by **creating an admin user** with `etherpad_admin_username` and `etherpad_admin_password` variables. The admin user account is also used by plugins for authentication and authorization." +#: ../../../docs/configuring-playbook-etherpad.md:50 +msgid "To do so, add the following configuration to your `vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:62 -msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md#create-admin-user-optional) on the role's documentation for details about how to create the admin user." +msgid "Extending the configuration" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:64 -msgid "Adjusting the Etherpad URL (optional)" +msgid "There are some additional things you may wish to configure about the component." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:66 -msgid "By tweaking the `etherpad_hostname` and `etherpad_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgid "Take a look at:" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:68 -msgid "Example additional configuration for your `vars.yml` file:" +msgid "[etherpad role](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/defaults/main.yml) for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `etherpad_configuration_extension_json` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:70 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:72 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:79 -msgid "After changing the domain, **you may need to adjust your DNS** records to point the Etherpad domain to the Matrix server." +msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:81 -msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the Etherpad admin user (`etherpad_admin_username`)." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:83 -msgid "Installing" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:85 -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:" +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:92 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-etherpad.md:94 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-etherpad.md:87 +msgid "If you change the Etherpad admin user's password (`etherpad_admin_password` in your `vars.yml` file) subsequently, the admin user's credentials on the homeserver won't be updated automatically. If you'd like to change the admin user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `etherpad_admin_password` to let the admin user know its new password." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:96 +#: ../../../docs/configuring-playbook-etherpad.md:89 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:98 -msgid "By default, the Etherpad UI should be available at `https://etherpad.example.com`, while the admin UI (if enabled) should then be available at `https://etherpad.example.com/admin`." +#: ../../../docs/configuring-playbook-etherpad.md:91 +msgid "The Etherpad UI should be available at `https://etherpad.example.com`, while the admin UI (if enabled) should then be available at `https://etherpad.example.com/admin`." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:100 +#: ../../../docs/configuring-playbook-etherpad.md:93 msgid "If you've [decided on another hostname or path-prefix](#adjusting-the-etherpad-url-optional) (e.g. `https://matrix.example.com/etherpad`), adjust these URLs accordingly before using it." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:102 -msgid "💡 For more information about usage, take a look at [this section](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md#usage) on the role's documentation." +#: ../../../docs/configuring-playbook-etherpad.md:95 +msgid "Managing / Deleting old pads" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:104 -msgid "Integrating a Etherpad widget in a room" +#: ../../../docs/configuring-playbook-etherpad.md:97 +msgid "If you want to manage and remove old unused pads from Etherpad, you will first need to create the Etherpad admin user as described above." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:106 -msgid "**Note**: this is how it works in Element Web. It might work quite similar with other clients:" +#: ../../../docs/configuring-playbook-etherpad.md:99 +msgid "After logging in to the admin web UI, go to the plugin manager page, and install the `adminpads2` plugin." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:108 -msgid "To integrate a standalone Etherpad in a room, create your pad by visiting `https://etherpad.example.com`. When the pad opens, copy the URL and send a command like this to the room: `/addwidget URL`. You will then find your integrated Etherpad within the right sidebar in the `Widgets` section." +#: ../../../docs/configuring-playbook-etherpad.md:101 +msgid "Once the plugin is installed, you should have a \"Manage pads\" section in the UI." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:110 -msgid "Troubleshooting" +#: ../../../docs/configuring-playbook-etherpad.md:103 +msgid "Integrating a Etherpad widget in a room" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:112 -msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md#troubleshooting) on the role's documentation for details." +#: ../../../docs/configuring-playbook-etherpad.md:105 +msgid "**Note**: this is how it works in Element Web. It might work quite similar with other clients:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:107 +msgid "To integrate a standalone Etherpad in a room, create your pad by visiting `https://etherpad.example.com`. When the pad opens, copy the URL and send a command like this to the room: `/addwidget URL`. You will then find your integrated Etherpad within the right sidebar in the `Widgets` section." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-federation.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-federation.po index 66ad037ef..8c43749f2 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-federation.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-federation.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,72 +19,72 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-federation.md:9 +#: ../../../docs/configuring-playbook-federation.md:1 msgid "Controlling Matrix federation (optional)" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:11 +#: ../../../docs/configuring-playbook-federation.md:3 msgid "By default, your server federates with the whole Matrix network. That is, people on your server can communicate with people on any other Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-federation.md:13 -msgid "**Note**: in the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com` and set up [server delegation](howto-server-delegation.md) / redirection. Without a proper configuration, your server will effectively not be part of the Matrix network. If you find your server is not federated, make sure to [check whether services work](maintenance-and-troubleshooting.md#how-to-check-if-services-work) and your server is properly delegated." +#: ../../../docs/configuring-playbook-federation.md:5 +msgid "**Note**: in the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com` and set up [server delegation](howto-server-delegation.md) / redirection. Without a proper configuration, your server will effectively not be part of the Matrix network. If you find your server is not federated, make sure to [check whether services work](maintenance-checking-services.md) and your server is properly delegated." msgstr "" -#: ../../../docs/configuring-playbook-federation.md:15 +#: ../../../docs/configuring-playbook-federation.md:7 msgid "Federating only with select servers" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:17 +#: ../../../docs/configuring-playbook-federation.md:9 msgid "To make your server only federate with servers of your choosing, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:25 +#: ../../../docs/configuring-playbook-federation.md:17 msgid "If you wish to disable federation, you can do that with an empty list (`[]`), or better yet by completely disabling federation (see below)." msgstr "" -#: ../../../docs/configuring-playbook-federation.md:27 +#: ../../../docs/configuring-playbook-federation.md:19 msgid "Exposing the room directory over federation" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:29 +#: ../../../docs/configuring-playbook-federation.md:21 msgid "By default, your server's public rooms directory is not exposed to other servers via federation." msgstr "" -#: ../../../docs/configuring-playbook-federation.md:31 +#: ../../../docs/configuring-playbook-federation.md:23 msgid "To expose it, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:37 +#: ../../../docs/configuring-playbook-federation.md:29 msgid "Disabling federation" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:39 +#: ../../../docs/configuring-playbook-federation.md:31 msgid "To completely disable federation, isolating your server from the rest of the Matrix network, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:45 +#: ../../../docs/configuring-playbook-federation.md:37 msgid "With that, your server's users will only be able to talk among themselves, but not to anyone who is on another server." msgstr "" -#: ../../../docs/configuring-playbook-federation.md:47 -msgid "**Disabling federation does not necessarily disable the federation port** (`8448`). Even if you disable federation and only if necessary, we may still be exposing the federation port and serving the `openid` APIs there. To override this and completely disable Synapse's federation port use:" +#: ../../../docs/configuring-playbook-federation.md:39 +msgid "**Disabling federation does not necessarily disable the federation port** (`8448`). Services like [Dimension](configuring-playbook-dimension.md) and [ma1sd](configuring-playbook-ma1sd.md) normally rely on `openid` APIs exposed on that port. Even if you disable federation and only if necessary, we may still be exposing the federation port and serving the `openid` APIs there. To override this and completely disable Synapse's federation port use:" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:59 +#: ../../../docs/configuring-playbook-federation.md:51 msgid "Changing the federation port from 8448 to a different port to use a CDN that only accepts 443/80 ports" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:61 +#: ../../../docs/configuring-playbook-federation.md:53 msgid "Why? This change could be useful for people running small Synapse instances on small severs/VPSes to avoid being impacted by a simple DOS/DDOS when bandwidth, RAM, an CPU resources are limited and if your hosting provider does not provide a DOS/DDOS protection." msgstr "" -#: ../../../docs/configuring-playbook-federation.md:63 +#: ../../../docs/configuring-playbook-federation.md:55 msgid "To make it possible to proxy the federation through a CDN such as CloudFlare or any other, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:74 +#: ../../../docs/configuring-playbook-federation.md:66 msgid "**Use this at you own risk as all the possible side-effects of doing this are not fully known. However, it has been tested and works fine and passes all the tests on without issues.**" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jitsi.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jitsi.po index 5f4c3ca25..b4ee0c25c 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jitsi.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jitsi.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,164 +19,488 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-jitsi.md:17 +#: ../../../docs/configuring-playbook-jitsi.md:1 msgid "Setting up the Jitsi video-conferencing platform (optional)" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:19 +#: ../../../docs/configuring-playbook-jitsi.md:3 msgid "The playbook can install and configure the [Jitsi](https://jitsi.org/) video-conferencing platform for you." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:21 -msgid "Because Jitsi still requires a TURN server, enabling Jitsi automatically enables coturn (`coturn_enabled: true`) unless you explicitly disable it." +#: ../../../docs/configuring-playbook-jitsi.md:5 +msgid "Jitsi can not only be integrated with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS) as a widget, but also be used as standalone web app." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:24 -msgid "Jitsi is an open source video-conferencing platform. It can not only be integrated with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS) as a widget, but also be used as standalone web app." +#: ../../../docs/configuring-playbook-jitsi.md:7 +msgid "See the project's [documentation](https://jitsi.github.io/handbook/) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:26 -msgid "💡 If you're into experimental technology, you may also be interested in trying out [Element Call](configuring-playbook-element-call.md) - a native Matrix video conferencing application." +#: ../../../docs/configuring-playbook-jitsi.md:9 +msgid "**Note**: the configuration by the playbook is similar to the one by [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the official documentation for Docker deployment [here](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:13 +msgid "You may need to open the following ports to your server:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:15 +msgid "`4443/tcp` — RTP media fallback over TCP" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:16 +msgid "`10000/udp` — RTP media over UDP. Depending on your firewall/NAT configuration, incoming RTP packets on port `10000` may have the external IP of your firewall as destination address, due to the usage of STUN in JVB (see [`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/defaults/main.yml))." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:18 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:20 +msgid "By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to create a CNAME record for `jitsi`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:28 -msgid "The [Ansible role for Jitsi](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring Jitsi, you can check them via:" +#: ../../../docs/configuring-playbook-jitsi.md:22 +msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:29 -msgid "🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md) online" +#: ../../../docs/configuring-playbook-jitsi.md:24 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:30 -msgid "📁 `roles/galaxy/jitsi/docs/configuring-jitsi.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" +#: ../../../docs/configuring-playbook-jitsi.md:26 +msgid "To enable Jitsi, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:32 -msgid "Prerequisites" +msgid "Adjusting the Jitsi URL (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:34 -msgid "Before proceeding, make sure to check server's requirements recommended by [the official deployment guide](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-requirements)." +msgid "By tweaking the `jitsi_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:36 -msgid "You may need to open some ports to your server, if you use another firewall in front of the server. Refer [the role's documentation](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#prerequisites) to check which ones to be configured." +msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:38 -msgid "Adjusting DNS records" +#: ../../../docs/configuring-playbook-jitsi.md:43 +msgid "After changing the domain, **you may need to adjust your DNS** records to point the Jitsi domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:40 -msgid "By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to create a CNAME record for `jitsi`, which targets `matrix.example.com`." +#: ../../../docs/configuring-playbook-jitsi.md:45 +msgid "Configure Jitsi authentication and guests mode (optional)" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:42 -msgid "When setting, replace `example.com` with your own." +#: ../../../docs/configuring-playbook-jitsi.md:47 +msgid "By default the Jitsi instance does not require for anyone to log in, and is open to use without an account. To control who is allowed to start meetings on your Jitsi instance, you'd need to enable Jitsi's authentication and optionally guests mode." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:44 -msgid "Adjusting the playbook configuration" +#: ../../../docs/configuring-playbook-jitsi.md:49 +msgid "Authentication type must be one of them: `internal` (default), `jwt`, `matrix` or `ldap`. Currently, only `internal`, `matrix` and `ldap` mechanisms are supported by the [Jitsi role](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi)." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:46 -msgid "To enable Jitsi, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +#: ../../../docs/configuring-playbook-jitsi.md:51 +msgid "With authentication enabled, all meetings have to be started by a registered user. After the meeting is started by that user, then guests are free to join. If the registered user is not yet present, the guests are put on hold in individual waiting rooms." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:64 -msgid "As the most of the necessary settings for the role have been taken care of by the playbook, you can enable Jitsi on your Matrix server with this minimum configuration." +#: ../../../docs/configuring-playbook-jitsi.md:53 +msgid "**Note**: authentication is not tested by the playbook's self-checks. We therefore recommend that you would make sure by yourself that authentication is configured properly. To test it, start a meeting at `jitsi.example.com` on your browser." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:66 -msgid "However, **since Jitsi's performance heavily depends on server resource (bandwidth, RAM, and CPU), it is recommended to review settings and optimize them as necessary before deployment.** You can check [here](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#example-configurations) for an example set of configurations to set up a Jitsi instance, focusing on performance. If you will host a large conference, you probably might also want to consider to provision additional JVBs ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)). See [here](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#set-up-additional-jvbs-for-more-video-conferences-optional) for details about setting them up with the playbook." +#: ../../../docs/configuring-playbook-jitsi.md:55 +msgid "Authenticate using Jitsi accounts: Auth-Type `internal` (recommended)" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:68 -msgid "See the role's documentation for details about configuring Jitsi per your preference (such as setting [a custom hostname](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#set-the-hostname) and [the environment variable for running Jitsi in a LAN](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#configure-jvb_advertise_ips-for-running-behind-nat-or-on-a-lan-environment-optional))." +#: ../../../docs/configuring-playbook-jitsi.md:57 +msgid "The default authentication mechanism is `internal` auth, which requires a Jitsi account to have been configured. This is a recommended method, as it also works in federated rooms." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:70 -msgid "Enable authentication and guests mode (optional)" +#: ../../../docs/configuring-playbook-jitsi.md:59 +msgid "To enable authentication with a Jitsi account, add the following configuration to your `vars.yml` file. Make sure to replace `USERNAME_…` and `PASSWORD_…` with your own values." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:72 -msgid "By default the Jitsi Meet instance **does not require for anyone to log in, and is open to use without an account**." +#: ../../../docs/configuring-playbook-jitsi.md:71 +msgid "**Note**: as Jitsi account removal function is not integrated into the playbook, these accounts will not be able to be removed from the Prosody server automatically, even if they are removed from your `vars.yml` file subsequently." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:74 -msgid "If you would like to control who is allowed to start meetings on your instance, you'd need to enable Jitsi's authentication and optionally guests mode." +#: ../../../docs/configuring-playbook-jitsi.md:73 +msgid "Authenticate using Matrix OpenID: Auth-Type `matrix`" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:76 -msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#configure-jitsi-authentication-and-guests-mode-optional) on the role's documentation for details about how to configure the authentication and guests mode. The recommended authentication method is `internal` as it also works in federated rooms. If you want to enable authentication with Matrix OpenID making use of [Matrix User Verification Service (UVS)](configuring-playbook-user-verification-service.md), see [here](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix) for details about how to set it up." +#: ../../../docs/configuring-playbook-jitsi.md:75 +msgid "[!WARNING] This breaks the Jitsi instance on federated rooms probably and does not allow sharing conference links with guests." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:78 -msgid "Enable Gravatar (optional)" +msgid "This authentication method requires [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service), which can be installed using this [playbook](configuring-playbook-user-verification-service.md). It verifies against Matrix openID, and requires a user-verification-service to run." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:80 +msgid "To enable authentication with Matrix OpenID, add the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:88 +msgid "For more information see also [https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification](https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:90 +msgid "Authenticate using LDAP: Auth-Type `ldap`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:92 +msgid "To enable authentication with LDAP, add the following configuration to your `vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:112 +msgid "For more information refer to the [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:114 +msgid "Configure `JVB_ADVERTISE_IPS` for running behind NAT or on a LAN environment (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:116 +msgid "When running Jitsi in a LAN environment, or on the public Internet via NAT, the `JVB_ADVERTISE_IPS` enviornment variable should be set." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:118 +msgid "This variable allows to control which IP addresses the JVB will advertise for WebRTC media traffic. It is necessary to set it regardless of the use of a reverse proxy, since it's the IP address that will receive the media (audio / video) and not HTTP traffic, hence it's oblivious to the reverse proxy." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:120 +msgid "If your users are coming in over the Internet (and not over LAN), this will likely be your public IP address. If this is not set up correctly, calls will crash when more than two users join a meeting." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:122 +msgid "To set the variable, add the following configuration to your `vars.yml` file. Make sure to replace `LOCAL_IP_ADDRESS_OF_THE_HOST_HERE` with a proper value." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:129 +msgid "Check [the official documentation](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/#running-behind-nat-or-on-a-lan-environment) for more details about it." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:131 +msgid "Set a maximum number of participants on a Jitsi conference (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:133 +msgid "You can set a maximum number of participants allowed to join a Jitsi conference. By default the number is not specified." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:135 +msgid "To set it, add the following configuration to your `vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:141 +msgid "Enable Gravatar (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:143 msgid "In the default Jisti Meet configuration, `gravatar.com` is enabled as an avatar service." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:82 -msgid "Since the Element clients send the URL of configured Matrix avatars to the Jitsi instance, our configuration has disabled the Gravatar service." +#: ../../../docs/configuring-playbook-jitsi.md:145 +msgid "Since the Element clients send the URL of configured Matrix avatars to the Jitsi instance, our default configuration has disabled the Gravatar service." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:84 -msgid "To enable the Gravatar service nevertheless, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-jitsi.md:147 +msgid "To enable the Gravatar service, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:90 +#: ../../../docs/configuring-playbook-jitsi.md:153 msgid "[!WARNING] This will result in third party request leaking data to the Gravatar Service (`gravatar.com`, unless configured otherwise). Besides metadata, the Matrix user_id and possibly the room ID (via `referrer` header) will be also sent to the third party." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:93 +#: ../../../docs/configuring-playbook-jitsi.md:156 +msgid "Fine tune Jitsi (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:158 +msgid "If you'd like to have Jitsi save up resources, add the following configuration to your `vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:171 +msgid "These configurations:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:173 +msgid "**limit the maximum video resolution**, to save up resources on both server and clients" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:174 +msgid "**suspend unused video layers** until they are requested again, to save up resources on both server and clients. Read more on this feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-feature/)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:175 +msgid "**disable audio levels** to avoid excessive refresh of the client-side page and decrease the CPU consumption involved" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:176 +msgid "**limit the number of video feeds forwarded to each client**, to save up resources on both server and clients. As clients’ bandwidth and CPU may not bear the load, use this setting to avoid lag and crashes. This feature is available by default on other webconference applications such as Office 365 Teams (the number is limited to 4). Read how it works [here](https://github.com/jitsi/jitsi-videobridge/blob/5ff195985edf46c9399dcf263cb07167f0a2c724/doc/allocation.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:178 +msgid "Example configurations" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:180 +msgid "Here is an example set of configurations for running a Jitsi instance with:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:182 +msgid "authentication using a Jitsi account (username: `US3RNAME`, password: `passw0rd`)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:183 +msgid "guests: allowed" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:184 +msgid "maximum participants: 6 people" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:185 +msgid "fine tuning with the configurations presented above" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:186 +msgid "other miscellaneous options (see the official Jitsi documentation [here](https://jitsi.github.io/handbook/docs/dev-guide/dev-guide-configuration) and [here](https://jitsi.github.io/handbook/docs/user-guide/user-guide-advanced))" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:206 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:95 +#: ../../../docs/configuring-playbook-jitsi.md:208 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:102 +#: ../../../docs/configuring-playbook-jitsi.md:215 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:104 +#: ../../../docs/configuring-playbook-jitsi.md:217 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:106 +#: ../../../docs/configuring-playbook-jitsi.md:219 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:108 +#: ../../../docs/configuring-playbook-jitsi.md:221 msgid "You can use the self-hosted Jitsi server in multiple ways:" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:110 +#: ../../../docs/configuring-playbook-jitsi.md:223 msgid "**by adding a widget to a room via Element Web** (the one configured by the playbook at `https://element.example.com`). Just start a voice or a video call in a room containing more than 2 members and that would create a Jitsi widget which utilizes your self-hosted Jitsi server." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:112 -msgid "**directly (without any Matrix integration)**. Just go to `https://jitsi.example.com`, and you can start a videoconference." +#: ../../../docs/configuring-playbook-jitsi.md:225 +msgid "**directly (without any Matrix integration)**. Just go to `https://jitsi.example.com`" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:114 -msgid "Note that you'll need to log in to your Jitsi's account to start a conference if you have configured authentication with `internal` auth." +#: ../../../docs/configuring-playbook-jitsi.md:227 +msgid "Set up additional JVBs for more video-conferences (optional)" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:116 -msgid "Check [the official user guide](https://jitsi.github.io/handbook/docs/category/user-guide) for details about how to use Jitsi." +#: ../../../docs/configuring-playbook-jitsi.md:229 +msgid "By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)) is deployed on the same host as the Matrix server. To allow more video-conferences to happen at the same time, you'd need to provision additional JVB services on other hosts." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:118 +#: ../../../docs/configuring-playbook-jitsi.md:231 +msgid "These settings below will allow you to provision those extra JVB instances. The instances will register themselves with the Prosody service, and be available for Jicofo to route conferences too." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:233 +msgid "Add the `jitsi_jvb_servers` section on `hosts` file" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:235 +msgid "For additional JVBs, you'd need to add the section titled `jitsi_jvb_servers` on the ansible `hosts` file with the details of the JVB hosts as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:242 +msgid "Make sure to replace `jvb-2.example.com` with your hostname for the JVB and `192.168.0.2` with your JVB's external IP address, respectively." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:244 +msgid "You could add JVB hosts as many as you would like. When doing so, add lines with the details of them." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:246 +msgid "Prepare `vars.yml` files for additional JVBs" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:248 +msgid "If the main server is `matrix.example.com` and the additional JVB instance is going to be deployed at `jvb-2.example.com`, the variables for the latter need to be specified on `vars.yml` in its directory (`inventory/host_vars/jvb-2.example.com`)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:250 +msgid "Note that most (if not all) variables are common for both servers." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:252 +msgid "If you are setting up multiple JVB instances, you'd need to create `vars.yml` files for each of them too (`inventory/host_vars/jvb-3.example.com/vars.yml`, for example)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:254 +msgid "Set the server ID to each JVB" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:256 +msgid "Each JVB requires a server ID to be set, so that it will be uniquely identified. The server ID allows Jitsi to keep track of which conferences are on which JVB." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:258 +msgid "The server ID can be set with the variable `jitsi_jvb_server_id`. It will end up as the `JVB_WS_SERVER_ID` environment variables in the JVB docker container." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:260 +msgid "To set the server ID to `jvb-2`, add the following configuration to either `hosts` or `vars.yml` files (adapt to your needs)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:262 +msgid "On `hosts`:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:264 +msgid "Add `jitsi_jvb_server_id=jvb-2` after your JVB's external IP addresses as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:272 +msgid "On `vars.yml` files:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:278 +msgid "Alternatively, you can specify the variable as a parameter to [the ansible command](#run-the-playbook)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:280 +msgid "**Note**: the server ID `jvb-1` is reserved for the JVB instance running on the Matrix host, therefore should not be used as the ID of an additional JVB host." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:282 +msgid "Set colibri WebSocket port" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:284 +msgid "The additional JVBs will need to expose the colibri WebSocket port." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:286 +msgid "To expose the port, add the following configuration to your `vars.yml` files:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:292 +msgid "Set Prosody XMPP server" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:294 +msgid "The JVB will also need to know the location of the Prosody XMPP server." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:296 +msgid "Similar to the server ID (`jitsi_jvb_server_id`), this can be set with the variable for the JVB by using the variable `jitsi_xmpp_server`." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:298 +msgid "Set the Matrix domain" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:300 +msgid "The Jitsi Prosody container is deployed on the Matrix server by default, so the value can be set to the Matrix domain. To set the value, add the following configuration to your `vars.yml` files:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:306 +msgid "Set an IP address of the Matrix server" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:308 +msgid "Alternatively, the IP address of the Matrix server can be set. This can be useful if you would like to use a private IP address." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:310 +msgid "To set the IP address of the Matrix server, add the following configuration to your `vars.yml` files:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:316 +msgid "Expose XMPP port" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:318 +msgid "By default, the Matrix server does not expose the XMPP port (`5222`); only the XMPP container exposes it internally inside the host. This means that the first JVB (which runs on the Matrix server) can reach it but the additional JVBs cannot. Therefore, the XMPP server needs to expose the port, so that the additional JVBs can connect to it." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:320 +msgid "To expose the port and have Docker forward the port, add the following configuration to your `vars.yml` files:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:326 +msgid "Reverse-proxy with Traefik" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:328 +msgid "To make Traefik reverse-proxy to these additional JVBs, add the following configuration to your main `vars.yml` file (`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:364 +msgid "Run the playbook" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:366 +msgid "After configuring `hosts` and `vars.yml` files, run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:372 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:120 -msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#troubleshooting) on the role's documentation for details." +#: ../../../docs/configuring-playbook-jitsi.md:374 +msgid "`Error: Account creation/modification not supported`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:376 +msgid "If you get an error like `Error: Account creation/modification not supported` with authentication enabled, it's likely that you had previously installed Jitsi without auth/guest support." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:378 +msgid "In this case, you should consider to rebuild your Jitsi installation." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:380 +msgid "Rebuilding your Jitsi installation" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:382 +msgid "If you ever run into any trouble or if you have changed configuration (`jitsi_*` variables) too much, you can rebuild your Jitsi installation." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:384 +msgid "We normally don't recommend manual intervention, but Jitsi services tend to generate a lot of configuration files, and it is often wise to start afresh setting the services up, rather than messing with the existing configuration files. Since not all of those files are managed by Ansible (at least not yet), you may sometimes need to delete them by yourself manually." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:386 +msgid "To rebuild your Jitsi configuration, follow the procedure below:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:388 +msgid "run this command locally to stop all Jitsi services: `just run-tags stop-group --extra-vars=group=jitsi`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:389 +msgid "log in the server with SSH" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:390 +msgid "run this command remotely to remove all Jitsi configuration & data: `rm -rf /matrix/jitsi`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:391 +msgid "run this command locally to set up Jitsi anew and restart services: `just install-service jitsi`" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jwt-service.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jwt-service.po deleted file mode 100644 index 6fc4927ba..000000000 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jwt-service.po +++ /dev/null @@ -1,98 +0,0 @@ -# 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 , 2026. -# -#, fuzzy -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" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: bg\n" -"Language-Team: bg \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-jwt-service.md:8 -msgid "Setting up JWT Service (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:10 -msgid "The playbook can install and configure [LiveKit JWT Service](https://github.com/element-hq/lk-jwt-service) for you." -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:12 -msgid "LK-JWT-Service is currently used for a single reason: generate JWT tokens with a given identity for a given room, so that users can use them to authenticate against LiveKit SFU." -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:14 -msgid "See the project's [documentation](https://github.com/element-hq/lk-jwt-service/) to learn more." -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:16 -msgid "Decide on a domain and path" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:18 -msgid "By default, JWT Service is configured to be served:" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:20 -msgid "on the Matrix domain (`matrix.example.com`), configurable via `matrix_livekit_jwt_service_hostname`" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:21 -msgid "under a `/livekit-jwt-service` path prefix, configurable via `matrix_livekit_jwt_service_path_prefix`" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:23 -msgid "This makes it easy to set it up, **without** having to adjust your DNS records manually." -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:25 -msgid "Adjusting DNS records" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:27 -msgid "If you've changed the default hostname, **you may need to adjust your DNS** records accordingly to point to the correct server." -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:29 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:31 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:37 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:39 -msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:41 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:43 -msgid "Once installed, a new `org.matrix.msc4143.rtc_foci` section is added to the Element Web client to point to your JWT service URL (e.g., `https://matrix.example.com/livekit-jwt-service`)." -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:45 -msgid "Additional Information" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:47 -msgid "Refer to the LiveKit JWT-Service documentation for more details on configuring and using JWT Service." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po index 85240ca7a..650db6880 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,60 +19,48 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-ldap-auth.md:10 +#: ../../../docs/configuring-playbook-ldap-auth.md:1 msgid "Setting up the LDAP authentication password provider module (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:12 +#: ../../../docs/configuring-playbook-ldap-auth.md:3 msgid "The playbook can install and configure the [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) LDAP Auth password provider for you." msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:14 +#: ../../../docs/configuring-playbook-ldap-auth.md:5 msgid "See the project's [documentation](https://github.com/matrix-org/matrix-synapse-ldap3/blob/main/README.rst) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:16 -msgid "Adjusting the playbook configuration" +#: ../../../docs/configuring-playbook-ldap-auth.md:7 +msgid "If you decide that you'd like to let this playbook install it for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:18 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" -msgstr "" - -#: ../../../docs/configuring-playbook-ldap-auth.md:35 +#: ../../../docs/configuring-playbook-ldap-auth.md:24 msgid "Authenticating only using a password provider" msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:37 -msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, you can disable it by adding the following configuration to your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-ldap-auth.md:43 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-ldap-auth.md:45 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +#: ../../../docs/configuring-playbook-ldap-auth.md:26 +msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:" msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:52 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +#: ../../../docs/configuring-playbook-ldap-auth.md:32 +msgid "Using ma1sd Identity Server for authentication (not recommended)" msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:54 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-ldap-auth.md:34 +msgid "The playbook can instead configure [ma1sd](https://github.com/ma1uta/ma1sd) Identity Server for LDAP authentication. However, **we recommend not bothering with installing it** as ma1sd has been unmaintained for years." msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:56 -msgid "Usage" +#: ../../../docs/configuring-playbook-ldap-auth.md:36 +msgid "If you wish to install it anyway, consult the [ma1sd Identity Server configuration](configuring-playbook-ma1sd.md#authentication)." msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:58 +#: ../../../docs/configuring-playbook-ldap-auth.md:38 msgid "Handling user registration" msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:60 +#: ../../../docs/configuring-playbook-ldap-auth.md:40 msgid "If you wish for users to also be able to make new registrations against LDAP, you may **also** wish to [set up the ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-livekit-jwt-service.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-livekit-jwt-service.po deleted file mode 100644 index 2a0a91383..000000000 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-livekit-jwt-service.po +++ /dev/null @@ -1,50 +0,0 @@ -# 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 , 2026. -# -#, fuzzy -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" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: bg\n" -"Language-Team: bg \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-livekit-jwt-service.md:7 -msgid "Setting up LiveKit JWT Service (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-jwt-service.md:9 -msgid "The playbook can install and configure [LiveKit JWT Service](https://github.com/element-hq/lk-jwt-service/) for you." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-jwt-service.md:11 -msgid "This is a helper component which is part of the [Matrix RTC stack](configuring-playbook-matrix-rtc.md) that allows [Element Call](configuring-playbook-element-call.md) to integrate with [LiveKit Server](configuring-playbook-livekit-server.md)." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-jwt-service.md:13 -msgid "💡 LiveKit JWT Service is automatically installed and configured when either [Element Call](configuring-playbook-element-call.md) or the [Matrix RTC stack](configuring-playbook-matrix-rtc.md) is enabled, so you don't need to do anything extra." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-jwt-service.md:15 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-jwt-service.md:17 -msgid "`roles/custom/matrix-livekit-jwt-service/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-jwt-service.md:18 -msgid "`roles/custom/matrix-livekit-jwt-service/templates/env.j2` for the component's default configuration." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-livekit-server.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-livekit-server.po deleted file mode 100644 index 99257f35b..000000000 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-livekit-server.po +++ /dev/null @@ -1,142 +0,0 @@ -# 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 , 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 \n" -"Language: bg\n" -"Language-Team: bg \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-livekit-server.md:8 -msgid "Setting up LiveKit Server (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:10 -msgid "The playbook can install and configure [LiveKit Server](https://github.com/livekit/livekit) for you." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:12 -msgid "LiveKit Server is an open source project that provides scalable, multi-user conferencing based on WebRTC. It's designed to provide everything you need to build real-time video audio data capabilities in your applications." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:14 -msgid "💡 LiveKit Server is automatically installed and configured when either [Element Call](configuring-playbook-element-call.md) or the [Matrix RTC stack](configuring-playbook-matrix-rtc.md) is enabled, so you don't need to do anything extra." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:16 -msgid "The [Ansible role for LiveKit Server](https://github.com/mother-of-all-self-hosting/ansible-role-livekit-server) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring LiveKit Server, you can check them via:" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:17 -msgid "🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-livekit-server/blob/main/docs/configuring-livekit-server.md) online" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:18 -msgid "📁 `roles/galaxy/livekit_server/docs/configuring-livekit-server.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:20 -msgid "Adjusting firewall rules" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:22 -msgid "To ensure LiveKit Server functions correctly, the following firewall rules and port forwarding settings are required:" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:24 -msgid "`7881/tcp`: ICE/TCP" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:26 -msgid "`7882/udp`: ICE/UDP Mux" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:28 -msgid "`3479/udp`: TURN/UDP. Also see the [Limitations](#limitations) section below." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:30 -msgid "`5350/tcp`: TURN/TCP. Also see the [Limitations](#limitations) section below." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:32 -msgid "`30000-30020/udp`: TURN relay range used by LiveKit's embedded TURN server." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:34 -msgid "💡 The suggestions above are inspired by the upstream [Ports and Firewall](https://docs.livekit.io/home/self-hosting/ports-firewall/) documentation based on how LiveKit is configured in the playbook. If you're using custom configuration for the LiveKit Server role, you may need to adjust firewall rules accordingly." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:36 -msgid "TURN TLS handling" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:38 -msgid "When `matrix_playbook_reverse_proxy_type` is `playbook-managed-traefik` (which is the default for this playbook), TURN over TCP is terminated by Traefik and forwarded to LiveKit with `turn.external_tls = true`. In this playbook default, this mode is enabled automatically when SSL is enabled and TURN is enabled." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:40 -msgid "The playbook installs a dedicated Traefik TCP entrypoint for TURN (`matrix-livekit-turn`) by default and binds it to `tcp/5350`." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:41 -msgid "`livekit_server_config_turn_external_tls` is automatically enabled for this setup." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:42 -msgid "Because Traefik handles TLS, LiveKit no longer needs certificate-file paths for TURN in this mode." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:44 -msgid "To opt out and keep TURN TLS termination in LiveKit itself, set:" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:50 -msgid "In this playbook, certificate paths are managed automatically via `group_vars/matrix_servers` when certificate dumping is enabled." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:52 -msgid "If your setup uses `other-traefik-container` or [another reverse-proxy](./configuring-playbook-own-webserver.md), behavior is unchanged by default and still relies on certificates being available inside the container as before." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:54 -msgid "Deployments using `other-traefik-container` can opt into the same Traefik-terminated mode there, by setting:" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:62 -msgid "and configuring their own Traefik TCP entrypoint dedicated to LiveKit TURN traffic." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:64 -msgid "Limitations" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:66 -msgid "LiveKit Server's TURN listener behavior depends on where TLS is terminated:" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:68 -msgid "Direct LiveKit TURN listeners (`livekit_server_config_turn_external_tls: false`) still use IPv4-only sockets for `3479/udp` and `5350/tcp`, so IPv6 connectivity to these endpoints is not possible." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:69 -msgid "With [TURN TLS handling](#turn-tls-handling) (`livekit_server_config_turn_external_tls: true`), the playbook's dedicated `matrix-livekit-turn` TCP entrypoint can still listen on both IPv4 and IPv6. Traefik then forwards TURN/TCP to LiveKit." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:71 -msgid "It appears that LiveKit Server intentionally only listens on `udp4` and `tcp4` in direct mode, as seen [here](https://github.com/livekit/livekit/blob/154b4d26b769c68a03c096124094b97bf61a996f/pkg/service/turn.go#L128) and [here](https://github.com/livekit/livekit/blob/154b4d26b769c68a03c096124094b97bf61a996f/pkg/service/turn.go#L92)." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ma1sd.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ma1sd.po index feea8f2ba..aa6374686 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ma1sd.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ma1sd.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-02-06 16:30+0900\n" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,24 +19,208 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" + +#: ../../../docs/configuring-playbook-ma1sd.md:1 +msgid "Setting up ma1sd Identity Server (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:3 +msgid "**⚠️Note**: ma1sd itself has also been unmaintained for years (the latest commit and release being from 2021). The role of identity servers in the Matrix specification also has an uncertain future. **We recommend not bothering with installing it unless it's the only way you can do what you need to do**. For example, certain things like LDAP integration can also be implemented via [the LDAP provider module for Synapse](./configuring-playbook-ldap-auth.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:5 +msgid "The playbook can configure the [ma1sd](https://github.com/ma1uta/ma1sd) Identity Server for you. It is a fork of [mxisd](https://github.com/kamax-io/mxisd) which was pronounced end of life 2019-06-21." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:7 +msgid "ma1sd is used for 3PIDs (3rd party identifiers like E-mail and phone numbers) and some [enhanced features](https://github.com/ma1uta/ma1sd/#features). It is private by default, potentially at the expense of user discoverability." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:9 +msgid "See the project's [documentation](https://github.com/ma1uta/ma1sd/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:13 +msgid "Open Matrix Federation port" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:15 +msgid "Enabling the ma1sd service will automatically reconfigure your Synapse homeserver to expose the `openid` API endpoints on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. If you enable the component, make sure that the port is accessible." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:17 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:19 +msgid "To make the ma1sd Identity Server enable its federation features, set up a SRV record that looks like this:" +msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:21 -msgid "Setting up ma1sd Identity Server (optional, removed)" +msgid "Name: `_matrix-identity._tcp` (use this text as-is)" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:22 +msgid "Content: `10 0 443 matrix.example.com` (replace `example.com` with your own)" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:24 +msgid "See [ma1sd's documentation](https://github.com/ma1uta/ma1sd/wiki/mxisd-and-your-privacy#choices-are-never-easy) for information on the privacy implications of setting up this SRV record." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:26 +msgid "When setting up a SRV record, if you are asked for a service and protocol instead of a hostname split the host value from the table where the period is. For example use service as `_matrix-identity` and protocol as `_tcp`." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:28 +msgid "**Note**: This `_matrix-identity._tcp` SRV record for the identity server is different from the `_matrix._tcp` that can be used for Synapse delegation. See [howto-server-delegation.md](howto-server-delegation.md) for more information about delegation." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:30 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:32 +msgid "To enable ma1sd, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:38 +msgid "Matrix.org lookup forwarding" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:40 +msgid "To ensure maximum discovery, you can make your identity server also forward lookups to the central matrix.org Identity server (at the cost of potentially leaking all your contacts information)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:42 +msgid "Enabling this is discouraged and you'd better [learn more](https://github.com/ma1uta/ma1sd/blob/master/docs/features/identity.md#lookups) before proceeding." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:44 +msgid "To enable matrix.org forwarding, add the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:50 +msgid "Additional features" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:52 +msgid "What this playbook configures for your is some bare minimum Identity Server functionality, so that you won't need to rely on external 3rd party services." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:54 +msgid "A few variables can be toggled in this playbook to alter the ma1sd configuration that gets generated." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:56 +msgid "Still, ma1sd can do much more. You can refer to the [ma1sd website](https://github.com/ma1uta/ma1sd) for more details and configuration options." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:58 +msgid "To use a more custom configuration, you can define a `matrix_ma1sd_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_ma1sd_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-ma1sd/defaults/main.yml) of the ma1sd component." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:60 +msgid "Customizing email templates" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:62 +msgid "If you'd like to change the default email templates used by ma1sd, take a look at the `matrix_ma1sd_threepid_medium_email_custom_` variables (in the `roles/custom/matrix-ma1sd/defaults/main.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:64 +msgid "ma1sd-controlled Registration" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:66 +msgid "To use the [Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) feature of ma1sd, you can make use of the following variables:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:68 +msgid "`matrix_synapse_enable_registration` — to enable user-initiated registration in Synapse" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:70 +msgid "`matrix_synapse_enable_registration_captcha` — to validate registering users using reCAPTCHA, as described in the [enabling reCAPTCHA](configuring-captcha.md) documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:72 +msgid "`matrix_synapse_registrations_require_3pid` — a list of 3pid types (among `'email'`, `'msisdn'`) required by the Synapse server for registering" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:74 +msgid "variables prefixed with `matrix_ma1sd_container_labels_` (e.g. `matrix_ma1sd_container_labels_matrix_client_3pid_registration_enabled`) — to configure the Traefik reverse-proxy to capture and send registration requests to ma1sd (instead of Synapse), so it can apply its additional functionality" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:76 +msgid "`matrix_ma1sd_configuration_extension_yaml` — to configure ma1sd as required. See the [Registration feature's docs](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) for inspiration. Also see the [Additional features](#additional-features) section below to learn more about how to use `matrix_ma1sd_configuration_extension_yaml`." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:78 +msgid "**Note**: For this to work, either the homeserver needs to [federate](configuring-playbook-federation.md) or the `openid` APIs need to exposed on the federation port. When federation is disabled and ma1sd is enabled, we automatically expose the `openid` APIs (only!) on the federation port. Make sure the federation port (usually `https://matrix.example.com:8448`) is whitelisted in your firewall (even if you don't actually use/need federation)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:80 +msgid "Authentication" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:82 +msgid "[Authentication](https://github.com/ma1uta/ma1sd/blob/master/docs/features/authentication.md) provides the possibility to use your own [Identity Stores](https://github.com/ma1uta/ma1sd/blob/master/docs/stores/README.md) (for example LDAP) to authenticate users on your Homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:84 +msgid "To enable authentication against an LDAP server, add the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:104 +msgid "Example: SMS verification" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:106 +msgid "If your use case requires mobile verification, it is quite simple to integrate ma1sd with [Twilio](https://www.twilio.com/), an online telephony services gateway. Their prices are reasonable for low-volume projects and integration can be done with the following configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:120 +msgid "Example: Open Registration for every Domain" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:122 +msgid "If you want to open registration for any domain, you have to setup the allowed domains with ma1sd's `blacklist` and `whitelist`. The default behavior when neither the `blacklist`, nor the `whitelist` match, is to allow registration. Beware: you can't block toplevel domains (aka `.xy`) because the internal architecture of ma1sd doesn't allow that." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:136 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:138 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:145 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:147 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-ma1sd.md:23 -msgid "🪦 The playbook used to be able to install and configure the [ma1sd](https://github.com/ma1uta/ma1sd) Identity Server, but no longer includes this component, as it has been unmaintained for a long time." +#: ../../../docs/configuring-playbook-ma1sd.md:149 +msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-ma1sd.md:25 -msgid "Please note that some of the functions can be achieved with other components. For example, if you wish to implement LDAP integration, you might as well check out [the LDAP provider module for Synapse](./configuring-playbook-ldap-auth.md) instead." +#: ../../../docs/configuring-playbook-ma1sd.md:151 +msgid "If email address validation emails sent by ma1sd are not reaching you, you should look into [Adjusting email-sending settings](configuring-playbook-email.md)." msgstr "" -#: ../../../docs/configuring-playbook-ma1sd.md:27 -msgid "Uninstalling the component manually" +#: ../../../docs/configuring-playbook-ma1sd.md:153 +msgid "If you'd like additional logging information, temporarily enable verbose logging for ma1sd." msgstr "" -#: ../../../docs/configuring-playbook-ma1sd.md:29 -msgid "If you still have the ma1sd Identity Server 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:" +#: ../../../docs/configuring-playbook-ma1sd.md:155 +msgid "To enable it, add the following configuration to your `vars.yml` file:" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po index 1a0104b9f..35eb8e43b 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,148 +19,112 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-matrix-corporal.md:9 +#: ../../../docs/configuring-playbook-matrix-corporal.md:1 msgid "Setting up Matrix Corporal (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:11 +#: ../../../docs/configuring-playbook-matrix-corporal.md:5 msgid "[!WARNING] This is an advanced feature! It requires prior experience with Matrix and a specific need for using [Matrix Corporal](https://github.com/devture/matrix-corporal). If you're unsure whether you have such a need, you most likely don't." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:14 +#: ../../../docs/configuring-playbook-matrix-corporal.md:10 msgid "The playbook can install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:16 -msgid "In short, it's a sort of automation and firewalling service, which is helpful if you're installing Matrix services in a controlled corporate environment." +#: ../../../docs/configuring-playbook-matrix-corporal.md:12 +msgid "In short, it's a sort of automation and firewalling service, which is helpful if you're instaling Matrix services in a controlled corporate environment." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:18 +#: ../../../docs/configuring-playbook-matrix-corporal.md:14 msgid "See the project's [documentation](https://github.com/devture/matrix-corporal/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:20 +#: ../../../docs/configuring-playbook-matrix-corporal.md:16 msgid "If you decide that you'd like to let this playbook install it for you, you'd need to also:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:21 +#: ../../../docs/configuring-playbook-matrix-corporal.md:17 msgid "(required) [set up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:22 +#: ../../../docs/configuring-playbook-matrix-corporal.md:18 msgid "(optional, but encouraged) [set up the REST authentication password provider module](configuring-playbook-rest-auth.md)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:24 +#: ../../../docs/configuring-playbook-matrix-corporal.md:20 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:26 +#: ../../../docs/configuring-playbook-matrix-corporal.md:22 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:79 +#: ../../../docs/configuring-playbook-matrix-corporal.md:75 msgid "Matrix Corporal operates with a specific Matrix user on your server. By default, it's `matrix-corporal` (controllable by the `matrix_corporal_reconciliation_user_id_local_part` setting, see above)." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:81 +#: ../../../docs/configuring-playbook-matrix-corporal.md:77 msgid "No matter what Matrix user ID you configure to run it with, make sure that:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:83 +#: ../../../docs/configuring-playbook-matrix-corporal.md:79 msgid "the Matrix Corporal user is created by [registering it](registering-users.md) **with administrator privileges**. Use a password you remember, as you'll need to log in from time to time to create or join rooms" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:85 +#: ../../../docs/configuring-playbook-matrix-corporal.md:81 msgid "the Matrix Corporal user is joined and has Admin/Moderator-level access to any rooms you want it to manage" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:87 +#: ../../../docs/configuring-playbook-matrix-corporal.md:83 msgid "Using a locally-stored static policy" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:89 +#: ../../../docs/configuring-playbook-matrix-corporal.md:85 msgid "If you'd like to use a [static policy file](https://github.com/devture/matrix-corporal/blob/master/docs/policy-providers.md#static-file-pull-style-policy-provider), you can use a configuration like this:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:121 +#: ../../../docs/configuring-playbook-matrix-corporal.md:117 msgid "To learn more about what the policy configuration, see the matrix-corporal documentation on [policy](https://github.com/devture/matrix-corporal/blob/master/docs/policy.md)." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:123 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:125 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:127 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:129 -msgid "`roles/custom/matrix-corporal/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:130 -msgid "`roles/custom/matrix-corporal/templates/config.json.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_corporal_configuration_extension_json` variable" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:132 +#: ../../../docs/configuring-playbook-matrix-corporal.md:119 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:134 +#: ../../../docs/configuring-playbook-matrix-corporal.md:121 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:141 +#: ../../../docs/configuring-playbook-matrix-corporal.md:128 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-aux-files,setup-corporal,start` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:143 +#: ../../../docs/configuring-playbook-matrix-corporal.md:130 msgid "`just run-tags setup-aux-files,setup-corporal,start` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:145 +#: ../../../docs/configuring-playbook-matrix-corporal.md:132 msgid "Matrix Corporal files" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:147 +#: ../../../docs/configuring-playbook-matrix-corporal.md:134 msgid "The following local filesystem paths are mounted in the `matrix-corporal` container and can be used in your configuration (or policy):" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:149 +#: ../../../docs/configuring-playbook-matrix-corporal.md:136 msgid "`/matrix/corporal/config` is mounted at `/etc/matrix-corporal` (read-only)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:151 +#: ../../../docs/configuring-playbook-matrix-corporal.md:138 msgid "`/matrix/corporal/var` is mounted at `/var/matrix-corporal` (read and write)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:153 +#: ../../../docs/configuring-playbook-matrix-corporal.md:140 msgid "`/matrix/corporal/cache` is mounted at `/var/cache/matrix-corporal` (read and write)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:155 +#: ../../../docs/configuring-playbook-matrix-corporal.md:142 msgid "As an example: you can create your own configuration files in `/matrix/corporal/config` and they will appear in `/etc/matrix-corporal` in the Docker container. Your configuration (stuff in `matrix_corporal_policy_provider_config`) needs to refer to these files via the local container paths — `/etc/matrix-corporal` (read-only), `/var/matrix-corporal` (read and write), `/var/cache/matrix-corporal` (read and write)." msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:157 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:159 -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-corporal`." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:161 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:163 -msgid "If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po index b0c1e9999..c2d7ae3d9 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,76 +19,48 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:9 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:1 msgid "Setting up matrix-ldap-registration-proxy (optional)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:11 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:3 msgid "The playbook can install and configure [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) for you." msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:13 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:5 msgid "This proxy handles Matrix registration requests and forwards them to LDAP." msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:15 -msgid "See the project's [documentation](https://gitlab.com/activism.international/matrix_ldap_registration_proxy/-/blob/main/README.md) to learn what it does and why it might be useful to you." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:17 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:7 msgid "**Note**: This does support the full Matrix specification for registrations. It only provide a very coarse implementation of a basic password registration." msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:19 -msgid "Adjusting the playbook configuration" +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:9 +msgid "Quickstart" msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:21 -msgid "To enable the component, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:11 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:33 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:22 msgid "If you already use the [synapse external password provider via LDAP](configuring-playbook-ldap-auth.md) (that is, you have `matrix_synapse_ext_password_provider_ldap_enabled: true` and other options in your configuration) you can use the following values as configuration:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:46 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:48 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:50 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:52 -msgid "`roles/custom/matrix-ldap-registration-proxy/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:54 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:35 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:56 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:37 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:63 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:44 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:65 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:46 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:67 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.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-ldap-registration-proxy`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po index 549aeb74c..3acc935c1 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po @@ -10,7 +10,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: 2024-12-28 10:25+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,219 +19,151 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:10 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:1 msgid "Storing Matrix media files using matrix-media-repo (optional)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:12 -msgid "The playbook can install and configure [matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often abbreviated \"MMR\") for you." +#: ../../../docs/configuring-playbook-matrix-media-repo.md:3 +msgid "[matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often abbreviated \"MMR\") is a highly customizable multi-domain media repository for Matrix. Intended for medium to large environments consisting of several homeservers, this media repo de-duplicates media (including remote media) while being fully compliant with the specification." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:14 -msgid "MMR is a highly customizable multi-domain media repository for Matrix. Intended for medium to large environments consisting of several homeservers, this media repo de-duplicates media (including remote media) while being fully compliant with the specification." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:16 -msgid "**Notes**:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:17 -msgid "If MMR is enabled, other media store roles should be disabled (if using Synapse with other media store roles)." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:18 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:5 msgid "Smaller/individual homeservers can still make use of this project's features, though it may be difficult to set up or have higher than expected resource consumption. Please do your research before deploying this as this project may not be useful for your environment." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:19 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:7 msgid "For a simpler alternative (which allows you to offload your media repository storage to S3, etc.), you can [configure S3 storage](configuring-playbook-s3.md) instead of setting up matrix-media-repo." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:21 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:23 -msgid "To enable matrix-media-repo, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:34 -msgid "**For existing installations**: retrieve the current datastore ID from the server's config file before proceeding:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:40 -msgid "Then use that value for `matrix_media_repo_datastore_file_id`. This is not a secret — it is a plain identifier used by matrix-media-repo to link media files to their storage backend." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:42 -msgid "By default, the media-repo will use the local filesystem for data storage. You can alternatively use a `s3` cloud backend as well. Access token caching is also enabled by default since the logout endpoints are proxied through the media repo." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:44 -msgid "Enable metrics" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:46 -msgid "The playbook can enable and configure the metrics of the service for you." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:48 -msgid "Metrics are **only enabled by default** if the builtin [Prometheus](configuring-playbook-prometheus-grafana.md) is enabled (by default, Prometheus isn't enabled). If so, metrics will automatically be collected by Prometheus and made available in Grafana. You will, however, need to set up your own Dashboard for displaying them." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:50 -msgid "To enable the metrics, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-matrix-media-repo.md +msgid "**Table of Contents**" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:57 -msgid "**To collect metrics from an external Prometheus server**, besides enabling metrics as described above, you will also need to enable metrics exposure on `https://matrix.example.com/metrics/matrix-media-repo` by adding the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-matrix-media-repo.md +msgid "[Quickstart](#quickstart)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:63 -msgid "By default metrics are exposed publicly **without** password-protection. To password-protect the metrics with dedicated credentials, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-matrix-media-repo.md +msgid "[Additional configuration options](#configuring-the-media-repo)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:70 -msgid "To `matrix_media_repo_container_labels_traefik_metrics_middleware_basic_auth_users`, set the Basic Authentication credentials (raw `htpasswd` file content) used to protect the endpoint. See https://doc.traefik.io/traefik/middlewares/http/basicauth/#users for details about it." +#: ../../../docs/configuring-playbook-matrix-media-repo.md +msgid "[Importing data from an existing media store](#importing-data-from-an-existing-media-store)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:72 -msgid "**Note**: alternatively, you can use `matrix_metrics_exposure_enabled` to expose all services on this `/metrics/*` feature, and you can use `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users` to password-protect the metrics of them. See [this section](configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) for more information." +#: ../../../docs/configuring-playbook-matrix-media-repo.md:15 +msgid "Quickstart" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:74 -msgid "Enable Grafana (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:76 -msgid "Probably you wish to enable Grafana along with Prometheus for generating graphs of the metrics." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:78 -msgid "To enable Grafana, see [this section](configuring-playbook-prometheus-grafana.md#adjusting-the-playbook-configuration-grafana) for instructions." +#: ../../../docs/configuring-playbook-matrix-media-repo.md:17 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file and [re-run the installation process](./installing.md) for the playbook:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:80 -msgid "Extending the configuration" +#: ../../../docs/configuring-playbook-matrix-media-repo.md:26 +msgid "The repo is pre-configured for integrating with the Postgres database, Traefik proxy and [Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) (if metrics enabled) from this playbook for all the available homeserver roles. When the media repo is enabled, other media store roles should be disabled (if using Synapse with other media store roles)." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:82 -msgid "There are some additional things you may wish to configure about the component." +#: ../../../docs/configuring-playbook-matrix-media-repo.md:28 +msgid "By default, the media-repo will use the local filesystem for data storage. You can alternatively use a `s3` cloud backend as well. Access token caching is also enabled by default since the logout endpoints are proxied through the media repo." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:84 -msgid "Take a look at:" +#: ../../../docs/configuring-playbook-matrix-media-repo.md:30 +msgid "Configuring the media-repo" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:86 -msgid "`roles/custom/matrix-media-repo/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +#: ../../../docs/configuring-playbook-matrix-media-repo.md:32 +msgid "Additional common configuration options:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:88 -msgid "Here is a list of additional common configuration options:" +#: ../../../docs/configuring-playbook-matrix-media-repo.md:91 +msgid "Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](../roles/custom/matrix-media-repo/defaults/main.yml)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:150 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:93 msgid "Signing Keys" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:152 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:95 msgid "Authenticated media endpoints ([MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916)) requires MMR to have a configured signing key to authorize outbound federation requests. Additionally, the signing key must be merged with your homeserver's signing key file." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:154 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:97 msgid "The playbook default is to generate a MMR signing key when invoking the setup role and merge it with your homeserver if you are using Synapse or Dendrite. This can be disabled if desired by setting the option in your inventory:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:160 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:103 msgid "If you wish to manually generate the signing key and merge it with your homeserver's signing key file, see https://docs.t2bot.io/matrix-media-repo/v1.3.5/installation/signing-key/ for more details." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:162 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:105 msgid "**Note that if you uninstall MMR from the playbook, it will not remove the old MMR signing key from your homeserver's signing key file. You will have to remove it manually.**" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:164 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:107 msgid "Key backup and revoking" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:166 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:109 msgid "Since your homeserver signing key file is modified by the playbook, a backup will be created in `HOMESERVER_DIR/config/example.com.signing.key.backup`. If you need to remove/revoke old keys, you can restore from this backup or remove the MMR key ID from your `example.com.signing.key` file." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:168 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:111 msgid "Additionally, its recommended after revoking a signing key to update your homeserver config file (`old_signing_keys` field for Synapse and `old_private_keys` for Dendrite). See your homeserver config file for further documentation on how to populate the field." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:170 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:113 msgid "Importing data from an existing media store" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:172 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:115 msgid "If you want to add this repo to an existing homeserver managed by the playbook, you will need to import existing media into MMR's database or you will lose access to older media while it is active. MMR versions up to `v1.3.3` only support importing from Synapse, but newer versions (at time of writing: only `latest`) also support importing from Dendrite." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:174 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:117 msgid "**Before importing**: ensure you have an initial matrix-media-repo deployment by following the [quickstart](#quickstart) guide above" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:176 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:119 msgid "Depending on the homeserver implementation yu're using (Synapse, Dendrite), you'll need to use a different import tool (part of matrix-media-repo) and point it to the homeserver's database." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:178 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:121 msgid "Importing data from the Synapse media store" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:180 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:123 msgid "To import the Synapse media store, you're supposed to invoke the `import_synapse` tool which is part of the matrix-media-repo container image. Your Synapse database is called `synapse` by default, unless you've changed it by modifying `matrix_synapse_database_database`." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:182 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:125 msgid "This guide here is adapted from the [upstream documentation about the import_synapse script](https://github.com/turt2live/matrix-media-repo#importing-media-from-synapse)." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:184 -#: ../../../docs/configuring-playbook-matrix-media-repo.md:206 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:127 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:149 msgid "Run the following command on the server (after replacing `postgres_connection_password` in it with the value found in your `vars.yml` file):" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:196 -#: ../../../docs/configuring-playbook-matrix-media-repo.md:218 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:139 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:161 msgid "Enter `1` for the Machine ID when prompted (you are not doing any horizontal scaling) unless you know what you're doing." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:198 -#: ../../../docs/configuring-playbook-matrix-media-repo.md:220 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:141 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:163 msgid "This should output a `msg=\"Import completed\"` when finished successfully!" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:200 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:143 msgid "Importing data from the Dendrite media store" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:202 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:145 msgid "If you're using the [Dendrite](configuring-playbook-dendrite.md) homeserver instead of the default for this playbook (Synapse), follow this importing guide here." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:204 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:147 msgid "To import the Dendrite media store, you're supposed to invoke the `import_dendrite` tool which is part of the matrix-media-repo container image. Your Dendrite database is called `dendrite_mediaapi` by default, unless you've changed it by modifying `matrix_dendrite_media_api_database`." msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:222 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:224 -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-media-repo`." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:226 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:228 -msgid "If you want to turn on sentry's built-in debugging, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po index 7095c78ef..dd519fc34 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,168 +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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-matrix-registration.md:9 +#: ../../../docs/configuring-playbook-matrix-registration.md:1 msgid "Setting up matrix-registration (optional)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:11 -msgid "[!WARNING]" +#: ../../../docs/configuring-playbook-matrix-registration.md:3 +msgid "⚠️ **Warnings**:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:12 +#: ../../../docs/configuring-playbook-matrix-registration.md:4 msgid "This is a poorly maintained and buggy project. It's better to avoid using it." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:13 +#: ../../../docs/configuring-playbook-matrix-registration.md:5 msgid "This is not related to [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:15 +#: ../../../docs/configuring-playbook-matrix-registration.md:7 msgid "The playbook can install and configure [matrix-registration](https://github.com/ZerataX/matrix-registration) for you. It is a simple python application to have a token based Matrix registration." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:17 +#: ../../../docs/configuring-playbook-matrix-registration.md:9 msgid "Use matrix-registration to **create unique registration links**, which people can use to register on your Matrix server. It allows certain people (these having a special link) to register a user account, **keeping your server's registration closed (private)**." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:19 +#: ../../../docs/configuring-playbook-matrix-registration.md:11 msgid "**matrix-registration** provides 2 things:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:21 +#: ../../../docs/configuring-playbook-matrix-registration.md:13 msgid "**an API for creating registration tokens** (unique registration links). This API can be used via `curl` or via the playbook (see [Usage](#usage) below)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:23 +#: ../../../docs/configuring-playbook-matrix-registration.md:15 msgid "**a user registration page**, where people can use these registration tokens. By default, exposed at `https://matrix.example.com/matrix-registration`" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:25 +#: ../../../docs/configuring-playbook-matrix-registration.md:17 msgid "Adjusting DNS records (optional)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:27 +#: ../../../docs/configuring-playbook-matrix-registration.md:19 msgid "By default, this playbook installs the matrix-registration on the `matrix.` subdomain, at the `/matrix-registration` path (https://matrix.example.com/matrix-registration). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:29 +#: ../../../docs/configuring-playbook-matrix-registration.md:21 msgid "If you wish to adjust it, see the section [below](#adjusting-the-matrix-registration-url-optional) for details about DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:31 +#: ../../../docs/configuring-playbook-matrix-registration.md:23 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:33 +#: ../../../docs/configuring-playbook-matrix-registration.md:25 msgid "To enable matrix-registration, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:42 +#: ../../../docs/configuring-playbook-matrix-registration.md:34 msgid "Adjusting the matrix-registration URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:44 +#: ../../../docs/configuring-playbook-matrix-registration.md:36 msgid "By tweaking the `matrix_registration_hostname` and `matrix_registration_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:46 +#: ../../../docs/configuring-playbook-matrix-registration.md:38 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:54 +#: ../../../docs/configuring-playbook-matrix-registration.md:46 msgid "If you've changed the default hostname, you may need to create a CNAME record for the matrix-registration domain (`registration.example.com`), which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:56 +#: ../../../docs/configuring-playbook-matrix-registration.md:48 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:58 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-registration.md:60 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-registration.md:62 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-registration.md:64 -msgid "`roles/custom/matrix-registration/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-registration.md:65 -msgid "`roles/custom/matrix-registration/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_registration_configuration_extension_yaml` variable" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-registration.md:67 +#: ../../../docs/configuring-playbook-matrix-registration.md:50 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:69 +#: ../../../docs/configuring-playbook-matrix-registration.md:52 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:76 +#: ../../../docs/configuring-playbook-matrix-registration.md:59 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:78 +#: ../../../docs/configuring-playbook-matrix-registration.md:61 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:80 +#: ../../../docs/configuring-playbook-matrix-registration.md:63 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:82 +#: ../../../docs/configuring-playbook-matrix-registration.md:65 msgid "**matrix-registration** gets exposed at `https://matrix.example.com/matrix-registration`" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:84 +#: ../../../docs/configuring-playbook-matrix-registration.md:67 msgid "It provides various [APIs](https://github.com/ZerataX/matrix-registration/wiki/api) — for creating registration tokens, listing tokens, disabling tokens, etc. To make use of all of its capabilities, consider using `curl`." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:86 +#: ../../../docs/configuring-playbook-matrix-registration.md:69 msgid "We make the most common APIs easy to use via the playbook (see below)." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:88 +#: ../../../docs/configuring-playbook-matrix-registration.md:71 msgid "Creating registration tokens" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:90 +#: ../../../docs/configuring-playbook-matrix-registration.md:73 msgid "To **create a new user registration token (link)**, use this command:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:98 +#: ../../../docs/configuring-playbook-matrix-registration.md:81 msgid "The above command creates and returns a **one-time use** token, which **expires** on the 31st of December 2021. Adjust the `one_time` and `ex_date` variables as you see fit." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:100 +#: ../../../docs/configuring-playbook-matrix-registration.md:83 msgid "Share the unique registration link (generated by the command above) with users to let them register on your Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:102 +#: ../../../docs/configuring-playbook-matrix-registration.md:85 msgid "Listing registration tokens" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:104 +#: ../../../docs/configuring-playbook-matrix-registration.md:87 msgid "To **list the existing user registration tokens**, use this command:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:111 +#: ../../../docs/configuring-playbook-matrix-registration.md:94 msgid "The shortcut command with `just` program is also available: `just run-tags list-matrix-registration-tokens`" msgstr "" - -#: ../../../docs/configuring-playbook-matrix-registration.md:113 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-registration.md:115 -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-registration`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-rtc.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-rtc.po deleted file mode 100644 index 23d01b042..000000000 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-rtc.po +++ /dev/null @@ -1,110 +0,0 @@ -# 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 , 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 \n" -"Language: bg\n" -"Language-Team: bg \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-matrix-rtc.md:8 -msgid "Setting up the Matrix RTC stack (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:10 -msgid "The playbook can install and configure the Matrix RTC (Real-Time Communication) stack." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:12 -msgid "The Matrix RTC stack is a set of supporting components ([LiveKit Server](configuring-playbook-livekit-server.md) and [LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md)) that allow the new [Element Call](configuring-playbook-element-call.md) audio/video calls to function." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:14 -msgid "💡 If you only plan on doing audio/video calls via Matrix client (which typically embed the Element Call frontend UI within them), you only need to install the Matrix RTC stack and don't necessarily need to install [Element Call](configuring-playbook-element-call.md). See the [Decide between Element Call vs just the Matrix RTC stack](configuring-playbook-element-call.md#decide-between-element-call-vs-just-the-matrix-rtc-stack) section of the [Element Call documentation](configuring-playbook-element-call.md) for more details." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:16 -msgid "Prerequisites" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:18 -msgid "A [Synapse](configuring-playbook-synapse.md) homeserver (see the warning below)" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:19 -msgid "Various experimental features for the Synapse homeserver which Element Call [requires](https://github.com/element-hq/element-call/blob/93ae2aed9841e0b066d515c56bd4c122d2b591b2/docs/self-hosting.md#a-matrix-homeserver) (automatically done when Element Call is enabled)" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:20 -msgid "A [LiveKit Server](configuring-playbook-livekit-server.md) (automatically installed when [Element Call or the Matrix RTC stack is enabled](configuring-playbook-element-call.md#decide-between-element-call-vs-just-the-matrix-rtc-stack))" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:21 -msgid "The [LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md) (automatically installed when [Element Call or the Matrix RTC stack is enabled](configuring-playbook-element-call.md#decide-between-element-call-vs-just-the-matrix-rtc-stack))" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:22 -msgid "A client compatible with Element Call. As of 2025-03-15, that's just [Element Web](configuring-playbook-client-element-web.md) and the Element X mobile clients (iOS and Android)." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:24 -msgid "[!WARNING] Because Element Call [requires](https://github.com/element-hq/element-call/blob/93ae2aed9841e0b066d515c56bd4c122d2b591b2/docs/self-hosting.md#a-matrix-homeserver) a few experimental features in the Matrix protocol, it's **very likely that it only works with the Synapse homeserver**." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:27 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:29 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:37 -msgid "Adjusting firewall rules" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:39 -msgid "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." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:41 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:43 -msgid "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:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:50 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:52 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:54 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:56 -msgid "Once installed, Matrix clients which support Element Call (like [Element Web](configuring-playbook-client-element-web.md) and Element X on mobile (iOS and Android)) will automatically use the Matrix RTC stack." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:58 -msgid "These clients typically embed the Element Call frontend UI within them, so installing [Element Call](configuring-playbook-element-call.md) is only necessary if you'd like to use it standalone - directly via a browser." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrixto.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrixto.po deleted file mode 100644 index 0eef2edb9..000000000 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrixto.po +++ /dev/null @@ -1,118 +0,0 @@ -# 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 , 2026. -# -#, fuzzy -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" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: bg\n" -"Language-Team: bg \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-matrixto.md:8 -msgid "Setting up Matrix.to (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:10 -msgid "The playbook can install and configure the [Matrix.to](https://github.com/matrix-org/matrix.to) URL redirection service for you." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:12 -msgid "See the project's [documentation](https://github.com/matrix-org/matrix.to/blob/main/README.md) to learn what it does and why it might be useful to you." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:14 -msgid "Adjusting DNS records" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:16 -msgid "By default, this playbook installs Matrix.to on the `mt.` subdomain (`mt.example.com`) and requires you to create a CNAME record for `mt`, which targets `matrix.example.com`." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:18 -msgid "When setting, replace `example.com` with your own." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:20 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:22 -msgid "To enable Matrix.to, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:28 -msgid "Adjusting the Matrix.to URL (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:30 -msgid "By tweaking the `matrix_matrixto_hostname` variable, you can easily make the service available at a **different hostname** than the default one." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:32 -msgid "Example additional configuration for your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:39 -msgid "After changing the domain, **you may need to adjust your DNS** records to point the Matrix.to domain to the Matrix server." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:41 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:43 -msgid "There are some additional things you may wish to configure about the server." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:45 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:47 -msgid "`roles/custom/matrix-matrixto/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:49 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:51 -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-matrixto.md:58 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:60 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:62 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:64 -msgid "Refer to the project's [documentation](https://github.com/matrix-org/matrix.to/blob/main/README.md) for available parameters, etc." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:66 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:68 -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-matrixto`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ntfy.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ntfy.po index 02bade546..0a92b3f04 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ntfy.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ntfy.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,260 +19,220 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-ntfy.md:12 +#: ../../../docs/configuring-playbook-ntfy.md:1 msgid "Setting up the ntfy push notifications server (optional)" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:14 -msgid "The playbook can install and configure the [ntfy](https://ntfy.sh/) (pronounced \"notify\") push notifications server for you." +#: ../../../docs/configuring-playbook-ntfy.md:3 +msgid "The playbook can install and configure the [ntfy](https://ntfy.sh/) push notifications server for you." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:16 -msgid "ntfy lets you send push notifications to your phone or desktop via scripts from any computer, using simple HTTP PUT or POST requests. It makes it possible to send/receive notifications, without relying on servers owned and controlled by third parties." +#: ../../../docs/configuring-playbook-ntfy.md:5 +msgid "Using the [UnifiedPush](https://unifiedpush.org) standard, ntfy enables self-hosted (Google-free) push notifications from Matrix (and other) servers to UnifiedPush-compatible Matrix compatible client apps running on Android and other devices." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:18 -msgid "With the [UnifiedPush](https://unifiedpush.org) standard, ntfy also enables self-hosted push notifications from Matrix (and other) servers to UnifiedPush-compatible Matrix client apps running on Android devices." +#: ../../../docs/configuring-playbook-ntfy.md:7 +msgid "This role is intended to support UnifiedPush notifications for use with the Matrix and Matrix-related services that this playbook installs. This role is not intended to support all of ntfy's other features." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:20 -msgid "See the project's [documentation](https://docs.ntfy.sh/) to learn what ntfy does and why it might be useful to you." +#: ../../../docs/configuring-playbook-ntfy.md:9 +msgid "**Note**: In contrast to push notifications using Google's FCM or Apple's APNs, the use of UnifiedPush allows each end-user to choose the push notification server that they prefer. As a consequence, deploying this ntfy server does not by itself ensure any particular user or device or client app will use it." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:22 -msgid "The [Ansible role for ntfy](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring ntfy, you can check them via:" -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:23 -msgid "🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/docs/configuring-ntfy.md) online" -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:24 -msgid "📁 `roles/galaxy/ntfy/docs/configuring-ntfy.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:26 -msgid "**Note**: this playbook focuses on setting up a ntfy server for getting it send push notifications with UnifiedPush to Matrix-related services that this playbook installs, while the installed server will be available for other non-Matrix apps like [Tusky](https://tusky.app/) and [DAVx⁵](https://www.davx5.com/) as well. This playbook does not intend to support all of ntfy's features. If you want to use them as well, refer the role's documentation for details to configure them by yourself." -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:28 -msgid "Improve push notification's privacy with ntfy" -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:30 -msgid "By default, push notifications received on Matrix apps on Android/iOS act merely as \"wake-up calls\" for the application, which contain only event IDs, and do not transmit actual message payload such as text message data." -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:32 -msgid "While your messages remain private even without ntfy, it makes it possible to improve privacy and sovereignty of your Matrix installation, offering greater control over your data, by avoiding routing these \"application wake-up calls\" through Google or Apple servers and having them pass through the self-hosted ntfy instance on your Matrix server." -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:34 -msgid "How ntfy works with UnifiedPush" -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:36 -msgid "⚠️ [UnifiedPush does not work on iOS.](https://unifiedpush.org/users/faq/#will-unifiedpush-ever-work-on-ios)" -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:38 -msgid "ntfy implements UnifiedPush, the standard which makes it possible to send and receive push notifications without using Google's Firebase Cloud Messaging (FCM) service." -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:40 -msgid "Working as a **Push Server**, a ntfy server can forward messages via [the ntfy Android app](https://docs.ntfy.sh/subscribe/phone/) as a **Distributor** to a UnifiedPush-compatible Matrix client such as Element Android and FluffyChat Android (see [here](https://unifiedpush.org/users/distributors/#definitions) for the definition of the Push Server and the Distributor)." -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:42 -msgid "Note that UnifiedPush-compatible applications must be able to communicate with the ntfy Android app which works as the Distributor on the same device, in order to receive push notifications from the Push Server." -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:44 -msgid "As the ntfy Android app functions as the Distributor, you do not have to install something else on your device, besides a UnifiedPush-compatible Matrix client." -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:46 +#: ../../../docs/configuring-playbook-ntfy.md:11 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:48 +#: ../../../docs/configuring-playbook-ntfy.md:13 msgid "By default, this playbook installs ntfy on the `ntfy.` subdomain (`ntfy.example.com`) and requires you to create a CNAME record for `ntfy`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:50 +#: ../../../docs/configuring-playbook-ntfy.md:15 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:52 +#: ../../../docs/configuring-playbook-ntfy.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:54 -msgid "To enable a ntfy server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +#: ../../../docs/configuring-playbook-ntfy.md:19 +msgid "To enable ntfy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:72 -msgid "As the most of the necessary settings for the role have been taken care of by the playbook, you can enable the ntfy server on your Matrix server with this minimum configuration." +#: ../../../docs/configuring-playbook-ntfy.md:33 +msgid "For a more complete list of variables that you could override, see the [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/defaults/main.yml) of the ntfy Ansible role." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:74 -msgid "See the role's documentation for details about configuring ntfy per your preference (such as [setting access control with authentication](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/docs/configuring-ntfy.md#enable-access-control-with-authentication-optional))." +#: ../../../docs/configuring-playbook-ntfy.md:35 +msgid "For a complete list of ntfy config options that you could put in `ntfy_configuration_extension_yaml`, see the [ntfy config documentation](https://ntfy.sh/docs/config/#config-options)." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:76 +#: ../../../docs/configuring-playbook-ntfy.md:37 msgid "Adjusting the ntfy URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:78 +#: ../../../docs/configuring-playbook-ntfy.md:39 msgid "By tweaking the `ntfy_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:80 +#: ../../../docs/configuring-playbook-ntfy.md:41 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:87 +#: ../../../docs/configuring-playbook-ntfy.md:48 msgid "After changing the domain, **you may need to adjust your DNS** records to point the ntfy domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:89 -msgid "Enable web app (optional)" +#: ../../../docs/configuring-playbook-ntfy.md:50 +msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:91 -msgid "The ntfy server can be accessed via its web app where you can subscribe to and push to \"topics\" from the browser. The web app may be helpful to troubleshoot notification issues or to use ntfy for other purposes than getting ntfy send UnifiedPush notifications to your Matrix-related services." +#: ../../../docs/configuring-playbook-ntfy.md:52 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:93 -msgid "**Note**: subscribing to a topic is not necessary for using the nfty server as the Push Server for UnifiedPush." +#: ../../../docs/configuring-playbook-ntfy.md:59 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:95 -msgid "To enable the web app, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-ntfy.md:61 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:101 -msgid "See [the official documentation](https://docs.ntfy.sh/subscribe/web/) for details about how to use it." +#: ../../../docs/configuring-playbook-ntfy.md:63 +msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:103 -msgid "Installing" +#: ../../../docs/configuring-playbook-ntfy.md:65 +msgid "To make use of your ntfy installation, on Android for example, you need two things:" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:105 -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:" +#: ../../../docs/configuring-playbook-ntfy.md:67 +msgid "the `ntfy` app" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:112 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +#: ../../../docs/configuring-playbook-ntfy.md:68 +msgid "a UnifiedPush-compatible Matrix app" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:114 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-ntfy.md:70 +msgid "You need to install the `ntfy` app on each device on which you want to receive push notifications through your ntfy server. The `ntfy` app will provide UnifiedPush notifications to any number of UnifiedPush-compatible messaging apps installed on the same device." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:116 -msgid "Usage" +#: ../../../docs/configuring-playbook-ntfy.md:72 +msgid "Setting up the `ntfy` Android app" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:118 -msgid "To receive push notifications with UnifiedPush from the ntfy server, you need to **install [the ntfy Android app](https://docs.ntfy.sh/subscribe/phone/)** which works as the Distributor, **log in to the account on the ntfy app** if you have enabled the access control, and then **configure a UnifiedPush-compatible Matrix client**. After setting up the ntfy Android app, the Matrix client listens to it, and push notifications are \"distributed\" from it." +#: ../../../docs/configuring-playbook-ntfy.md:74 +msgid "Install the [ntfy Android app](https://ntfy.sh/docs/subscribe/phone/) from F-droid or Google Play." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:120 -msgid "For details about installing and configuring the ntfy Android app, take a look at [this section](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/docs/configuring-ntfy.md#install-the-ntfy-androidios-app) on the role's documentation." +#: ../../../docs/configuring-playbook-ntfy.md:75 +msgid "In its Settings -> `General: Default server`, enter your ntfy server URL, such as `https://ntfy.example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:76 +msgid "In its Settings -> `Advanced: Connection protocol`, choose `WebSockets`." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:78 +msgid "That is all you need to do in the ntfy app. It has many other features, but for our purposes you can ignore them. In particular you do not need to follow any instructions about subscribing to a notification topic as UnifiedPush will do that automatically." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:122 -msgid "⚠️ Though the ntfy app is available for iOS ([App Store](https://apps.apple.com/us/app/ntfy/id1625396347); the app's source code can be retrieved from [here](https://github.com/binwiederhier/ntfy-ios)), **any Matrix clients for iOS currently do not support ntfy** due to [technical limitations of the iOS platform](https://github.com/binwiederhier/ntfy-ios/blob/main/docs/TECHNICAL_LIMITATIONS.md). If you develop your own Matrix client app for iOS, you may need to use the [Sygnal](configuring-playbook-sygnal.md) push gateway service to deliver push notifications to it." +#: ../../../docs/configuring-playbook-ntfy.md:80 +msgid "Setting up a UnifiedPush-compatible Matrix app" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:124 -msgid "Setting up a UnifiedPush-compatible Matrix client" +#: ../../../docs/configuring-playbook-ntfy.md:82 +msgid "Install any UnifiedPush-enabled Matrix app on that same device. The Matrix app will learn from the `ntfy` app that you have configured UnifiedPush on this device, and then it will tell your Matrix server to use it." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:126 -msgid "Having configured the ntfy Android app, you can configure a UnifiedPush-compatible Matrix client on the same device." +#: ../../../docs/configuring-playbook-ntfy.md:84 +msgid "Steps needed for specific Matrix apps:" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:128 -msgid "Steps needed for specific Matrix clients:" +#: ../../../docs/configuring-playbook-ntfy.md:86 +msgid "FluffyChat-android:" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:130 -msgid "FluffyChat-Android: this should auto-detect and use the app. No manual settings required." +#: ../../../docs/configuring-playbook-ntfy.md:87 +msgid "Should auto-detect and use it. No manual settings." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:132 -msgid "SchildiChat-Android:" +#: ../../../docs/configuring-playbook-ntfy.md:89 +msgid "SchildiChat-android:" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:133 +#: ../../../docs/configuring-playbook-ntfy.md:90 msgid "enable `Settings` -> `Notifications` -> `UnifiedPush: Force custom push gateway`." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:134 -msgid "choose `Settings` -> `Notifications` -> `UnifiedPush: Re-register push distributor`. *(For info, a more complex alternative to achieve the same is: delete the relevant unifiedpush registration in the ntfy Android app, force-close SchildiChat, re-open it.)*" +#: ../../../docs/configuring-playbook-ntfy.md:91 +msgid "choose `Settings` -> `Notifications` -> `UnifiedPush: Re-register push distributor`. *(For info, a more complex alternative to achieve the same is: delete the relevant unifiedpush registration in `ntfy` app, force-close SchildiChat, re-open it.)*" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:135 +#: ../../../docs/configuring-playbook-ntfy.md:92 msgid "verify `Settings` -> `Notifications` -> `UnifiedPush: Notification targets` as described below in the \"Troubleshooting\" section." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:137 -msgid "Element-Android v1.4.26+:" +#: ../../../docs/configuring-playbook-ntfy.md:94 +msgid "Element-android v1.4.26+:" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:138 +#: ../../../docs/configuring-playbook-ntfy.md:95 msgid "choose `Settings` -> `Notifications` -> `Notification method` -> `ntfy`" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:139 +#: ../../../docs/configuring-playbook-ntfy.md:96 msgid "verify `Settings` -> `Troubleshoot` -> `Troubleshoot notification settings`" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:141 -msgid "If the Matrix client asks, \"Choose a distributor: FCM Fallback or ntfy\", then choose \"ntfy\"." +#: ../../../docs/configuring-playbook-ntfy.md:98 +msgid "If the Matrix app asks, \"Choose a distributor: FCM Fallback or ntfy\", then choose \"ntfy\"." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:143 -msgid "If the Matrix client doesn't seem to pick it up, try restarting it and try the Troubleshooting section below." +#: ../../../docs/configuring-playbook-ntfy.md:100 +msgid "If the Matrix app doesn't seem to pick it up, try restarting it and try the Troubleshooting section below." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:145 -msgid "Troubleshooting" +#: ../../../docs/configuring-playbook-ntfy.md:102 +msgid "Web App" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:147 -msgid "The simple [UnifiedPush troubleshooting](https://unifiedpush.org/users/troubleshooting/) app [UP-Example](https://f-droid.org/en/packages/org.unifiedpush.example/) can be used to manually test UnifiedPush registration and operation on an Android device." +#: ../../../docs/configuring-playbook-ntfy.md:104 +msgid "ntfy also has a web app to subscribe to and push to topics from the browser. This may be helpful to further troubleshoot UnifiedPush problems or to use ntfy for other purposes. The web app only runs in the browser locally (after downloading the JavaScript)." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:149 -msgid "Check the Matrix client" +#: ../../../docs/configuring-playbook-ntfy.md:106 +msgid "The web app is disabled in this playbook by default as the expectation is that most users won't use it. You can either use the [official hosted one](https://ntfy.sh/app) (it supports using other public reachable ntfy instances) or host it yourself by setting `ntfy_web_root: \"app\"` and re-running Ansible." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:151 -msgid "Make sure that the Matrix client you are using supports UnifiedPush. There may well be different variants of the app." +#: ../../../docs/configuring-playbook-ntfy.md:108 +msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:153 -msgid "To check if UnifiedPush is correctly configured on the client device, look at \"Settings -> Notifications -> Notification Targets\" in Element Android or SchildiChat Android, or \"Settings -> Notifications -> Devices\" in FluffyChat. There should be one entry for each Matrix client that has enabled push notifications, and when that client is using UnifiedPush you should see a URL that begins with your ntfy server's URL." +#: ../../../docs/configuring-playbook-ntfy.md:110 +msgid "First check that the Matrix client app you are using supports UnifiedPush. There may well be different variants of the app." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:155 -msgid "In the \"Notification Targets\" screen in Element Android or SchildiChat Android, two relevant URLs are shown, \"push\\_key\" and \"Url\", and both should begin with your ntfy server's URL. If \"push\\_key\" shows your server but \"Url\" shows an external server such as `up.schildi.chat` then push notifications will still work but are being routed through that external server before they reach your ntfy server. To rectify that, in SchildiChat (at least around version 1.4.20.sc55) you must enable the `Force custom push gateway` setting as described in the \"Usage\" section above." +#: ../../../docs/configuring-playbook-ntfy.md:112 +msgid "Set the ntfy server's log level to 'DEBUG', as shown in the example settings above, and watch the server's logs with `sudo journalctl -fu matrix-ntfy`." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:157 -msgid "If it is not working, useful tools are \"Settings -> Notifications -> Re-register push distributor\" and \"Settings -> Notifications -> Troubleshoot Notifications\" in SchildiChat Android (possibly also Element Android). In particular the \"Endpoint/FCM\" step of that troubleshooter should display your ntfy server's URL that it has discovered from the ntfy client app." +#: ../../../docs/configuring-playbook-ntfy.md:114 +msgid "To check if UnifiedPush is correctly configured on the client device, look at \"Settings -> Notifications -> Notification Targets\" in Element Android or SchildiChat Android, or \"Settings -> Notifications -> Devices\" in FluffyChat. There should be one entry for each Matrix client app that has enabled push notifications, and when that client is using UnifiedPush you should see a URL that begins with your ntfy server's URL." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:116 +msgid "In the \"Notification Targets\" screen in Element Android or SchildiChat Android, two relevant URLs are shown, \"push\\_key\" and \"Url\", and both should begin with your ntfy server's URL. If \"push\\_key\" shows your server but \"Url\" shows an external server such as `up.schildi.chat` then push notifications will still work but are being routed through that external server before they reach your ntfy server. To rectify that, in SchildiChat (at least around version 1.4.20.sc55) you must enable the `Force custom push gateway` setting as described in the \"Usage\" section above." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:159 -msgid "Check the service's logs" +#: ../../../docs/configuring-playbook-ntfy.md:118 +msgid "If it is not working, useful tools are \"Settings -> Notifications -> Re-register push distributor\" and \"Settings -> Notifications -> Troubleshoot Notifications\" in SchildiChat Android (possibly also Element Android). In particular the \"Endpoint/FCM\" step of that troubleshooter should display your ntfy server's URL that it has discovered from the ntfy client app." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:161 -msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/docs/configuring-ntfy.md#check-the-services-logs) on the role's documentation for details." +#: ../../../docs/configuring-playbook-ntfy.md:120 +msgid "The simple [UnifiedPush troubleshooting](https://unifiedpush.org/users/troubleshooting/) app [UP-Example](https://f-droid.org/en/packages/org.unifiedpush.example/) can be used to manually test UnifiedPush registration and operation on an Android device." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-own-webserver.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-own-webserver.po index 45d23f11f..7455f73ca 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-own-webserver.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-own-webserver.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,176 +19,176 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-own-webserver.md:19 +#: ../../../docs/configuring-playbook-own-webserver.md:1 msgid "Using your own webserver, instead of this playbook's Traefik reverse-proxy (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:21 +#: ../../../docs/configuring-playbook-own-webserver.md:3 msgid "By default, this playbook installs its own [Traefik](https://traefik.io/) reverse-proxy server (in a Docker container) which listens on ports 80 and 443. If that's okay, you can skip this document." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:23 +#: ../../../docs/configuring-playbook-own-webserver.md:5 msgid "Traefik" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:25 +#: ../../../docs/configuring-playbook-own-webserver.md:7 msgid "[Traefik](https://traefik.io/) is the default reverse-proxy for the playbook since [2023-02-26](../CHANGELOG.md/#2023-02-26) and serves **2 purposes**:" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:27 +#: ../../../docs/configuring-playbook-own-webserver.md:9 msgid "serving public traffic and providing SSL-termination with certificates obtained from [Let's Encrypt](https://letsencrypt.org/). See [Adjusting SSL certificate retrieval](./configuring-playbook-ssl-certificates.md)." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:29 -msgid "assists internal communication between addon services (bridges, bots, etc.) and the homeserver via an internal entrypoint (`matrix-internal-matrix-client-api`)." +#: ../../../docs/configuring-playbook-own-webserver.md:11 +msgid "assists internal communication between addon services (briges, bots, etc.) and the homeserver via an internal entrypoint (`matrix-internal-matrix-client-api`)." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:31 +#: ../../../docs/configuring-playbook-own-webserver.md:13 msgid "There are 2 ways to use Traefik with this playbook, as described below." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:33 +#: ../../../docs/configuring-playbook-own-webserver.md:15 msgid "Traefik managed by the playbook" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:35 +#: ../../../docs/configuring-playbook-own-webserver.md:17 msgid "To have the playbook install and use Traefik, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:41 +#: ../../../docs/configuring-playbook-own-webserver.md:25 msgid "Traefik will manage SSL certificates for all services seamlessly." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:43 +#: ../../../docs/configuring-playbook-own-webserver.md:27 msgid "Traefik managed by you" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:69 +#: ../../../docs/configuring-playbook-own-webserver.md:53 msgid "In this mode all roles will still have Traefik labels attached. You will, however, need to configure your Traefik instance and its entrypoints." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:71 +#: ../../../docs/configuring-playbook-own-webserver.md:55 msgid "By default, the playbook configured a `default` certificate resolver and multiple entrypoints." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:73 +#: ../../../docs/configuring-playbook-own-webserver.md:57 msgid "You need to configure 4 entrypoints for your Traefik server:" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:75 +#: ../../../docs/configuring-playbook-own-webserver.md:59 msgid "`web` (TCP port `80`) — used for redirecting to HTTPS (`web-secure`)" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:76 +#: ../../../docs/configuring-playbook-own-webserver.md:60 msgid "`web-secure` (TCP port `443`) — used for exposing the Matrix Client-Server API and all other services" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:77 +#: ../../../docs/configuring-playbook-own-webserver.md:61 msgid "`matrix-federation` (TCP port `8448`) — used for exposing the Matrix Federation API" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:78 +#: ../../../docs/configuring-playbook-own-webserver.md:62 msgid "`matrix-internal-matrix-client-api` (TCP port `8008`) — used internally for addon services (bridges, bots) to communicate with the homserver" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:80 +#: ../../../docs/configuring-playbook-own-webserver.md:64 msgid "Below is some configuration for running Traefik yourself, although we recommend using [Traefik managed by the playbook](#traefik-managed-by-the-playbook)." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:82 +#: ../../../docs/configuring-playbook-own-webserver.md:66 msgid "Note that this configuration on its own does **not** redirect traffic on port 80 (plain HTTP) to port 443 for HTTPS. If you are not already doing this in Traefik, it can be added to Traefik in a [file provider](https://docs.traefik.io/v2.0/providers/file/) as follows:" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:102 +#: ../../../docs/configuring-playbook-own-webserver.md:86 msgid "You can use the following `docker-compose.yml` as example to launch Traefik." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:138 +#: ../../../docs/configuring-playbook-own-webserver.md:122 msgid "Another webserver" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:140 +#: ../../../docs/configuring-playbook-own-webserver.md:124 msgid "If you don't wish to use Traefik, you can also use your own webserver." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:142 +#: ../../../docs/configuring-playbook-own-webserver.md:126 msgid "Doing this is possible, but requires manual work." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:144 +#: ../../../docs/configuring-playbook-own-webserver.md:128 msgid "There are 2 ways to go about it:" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:146 +#: ../../../docs/configuring-playbook-own-webserver.md:130 msgid "(recommended) [Fronting the integrated reverse-proxy webserver with another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) — using the playbook-managed reverse-proxy (Traefik), but disabling SSL termination for it, exposing this reverse-proxy on a few local ports (e.g. `127.0.0.1:81`, etc.) and forwarding traffic from your own webserver to those few ports" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:148 +#: ../../../docs/configuring-playbook-own-webserver.md:132 msgid "(difficult) [Using no reverse-proxy on the Matrix side at all](#using-no-reverse-proxy-on-the-matrix-side-at-all) disabling the playbook-managed reverse-proxy (Traefik), exposing services one by one using `_host_bind_port` variables and forwarding traffic from your own webserver to those ports" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:150 +#: ../../../docs/configuring-playbook-own-webserver.md:134 msgid "Fronting the integrated reverse-proxy webserver with another reverse-proxy" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:152 +#: ../../../docs/configuring-playbook-own-webserver.md:136 msgid "This method is about leaving the integrated reverse-proxy webserver be, but making it not get in the way (using up important ports, trying to retrieve SSL certificates, etc.)." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:154 +#: ../../../docs/configuring-playbook-own-webserver.md:138 msgid "If you wish to use another webserver, the integrated reverse-proxy webserver usually gets in the way because it attempts to fetch SSL certificates and binds to ports 80, 443 and 8448 (if Matrix Federation is enabled)." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:156 +#: ../../../docs/configuring-playbook-own-webserver.md:140 msgid "You can disable such behavior and make the integrated reverse-proxy webserver only serve traffic locally on the host itself (or over a local network)." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:158 +#: ../../../docs/configuring-playbook-own-webserver.md:142 msgid "This is the recommended way for using another reverse-proxy, because the integrated one would act as a black box and wire all Matrix services correctly. You would then only need to reverse-proxy a few individual domains and ports over to it." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:160 +#: ../../../docs/configuring-playbook-own-webserver.md:144 msgid "To front Traefik with another reverse-proxy, you would need some configuration like this:" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:210 +#: ../../../docs/configuring-playbook-own-webserver.md:194 msgid "Such a configuration would expose all services on a local port `81` and Matrix Federation on a local port `8449`. Your reverse-proxy configuration needs to send traffic to these ports. [`examples/reverse-proxies`](../examples/reverse-proxies/) contains examples for various webservers such as Apache2, Caddy, HAproxy, nginx and Nginx Proxy Manager." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:212 +#: ../../../docs/configuring-playbook-own-webserver.md:196 msgid "It's important that these webservers proxy-pass requests to the correct `ip:port` and also set the `Host` HTTP header appropriately. If you don't pass the `Host` header correctly, Traefik will return a `404 - not found` error." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:214 +#: ../../../docs/configuring-playbook-own-webserver.md:198 msgid "To put it another way:" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:215 +#: ../../../docs/configuring-playbook-own-webserver.md:199 msgid "`curl http://127.0.0.1:81` will result in a `404 - not found` error" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:216 +#: ../../../docs/configuring-playbook-own-webserver.md:200 msgid "but `curl -H 'Host: matrix.example.com' http://127.0.0.1:81` should work." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:218 +#: ../../../docs/configuring-playbook-own-webserver.md:202 msgid "Using no reverse-proxy on the Matrix side at all" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:220 +#: ../../../docs/configuring-playbook-own-webserver.md:204 msgid "Instead of [Fronting the integrated reverse-proxy webserver with another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy), you can also go another way — completely disabling the playbook-managed Traefik reverse-proxy. You would then need to reverse-proxy from your own webserver directly to each individual Matrix service." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:222 +#: ../../../docs/configuring-playbook-own-webserver.md:206 msgid "This is more difficult, as you would need to handle the configuration for each service manually. Enabling additional services would come with extra manual work you need to do." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:224 +#: ../../../docs/configuring-playbook-own-webserver.md:208 msgid "Also, the Traefik reverse-proxy, besides fronting everything is also serving a 2nd purpose of allowing addons services to communicate with the Matrix homeserver thanks to its `matrix-internal-matrix-client-api` entrypoint (read more about it above). Disabling Traefik completely means the playbook would wire services to directly talk to the homeserver. This can work for basic setups, but not for more complex setups involving [matrix-media-repo](./configuring-playbook-matrix-media-repo.md), [matrix-corporal](./configuring-playbook-matrix-corporal.md) or other such services that need to \"steal routes\" from the homeserver." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:226 +#: ../../../docs/configuring-playbook-own-webserver.md:210 msgid "If your webserver is on the same machine, ensure your web server user (something like `http`, `apache`, `www-data`, `nginx`) is part of the `matrix` group. You should run something like this: `usermod -a -G matrix nginx`. This allows your webserver user to access files owned by the `matrix` group, so that it can serve static files from `/matrix/static-files`." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po index 0e79c521c..df09dce7b 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,28 +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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-postgres-backup.md:9 -msgid "Setting up Postgres backup (optional)" +#: ../../../docs/configuring-playbook-postgres-backup.md:1 +msgid "Setting up postgres backup (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:3 +msgid "The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you via the [ansible-role-postgres-backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup) Ansible role." msgstr "" -#: ../../../docs/configuring-playbook-postgres-backup.md:11 -msgid "The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you." +#: ../../../docs/configuring-playbook-postgres-backup.md:5 +msgid "For a more complete backup solution (one that includes not only Postgres, but also other configuration/data files), you may wish to look into [BorgBackup](configuring-playbook-backup-borg.md) instead." msgstr "" -#: ../../../docs/configuring-playbook-postgres-backup.md:13 -msgid "The [Ansible role for docker-postgres-backup-local](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring docker-postgres-backup-local, you can check them via:" +#: ../../../docs/configuring-playbook-postgres-backup.md:7 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-postgres-backup.md:14 -msgid "🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup/blob/main/docs/configuring-postgres-backup.md) online" +#: ../../../docs/configuring-playbook-postgres-backup.md:9 +msgid "To enable Postgres backup, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-postgres-backup.md:15 -msgid "📁 `roles/galaxy/postgres_backup/docs/configuring-postgres-backup.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" +msgid "Refer to the table below for additional configuration variables and their default values." +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Name" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Default value" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Description" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`false`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Set to true to use [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) to create automatic database backups" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_schedule`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`'@daily'`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Cron-schedule specifying the interval between postgres backups." +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_keep_days`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`7`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Number of daily backups to keep" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_keep_weeks`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`4`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Number of weekly backups to keep" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_keep_months`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`12`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Number of monthly backups to keep" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_base_path`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`\"{{ matrix_base_data_path }}/postgres-backup\"`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Base path for postgres-backup. Also see `postgres_backup_data_path`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_data_path`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`\"{{ postgres_backup_base_path }}/data\"`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Storage path for postgres-backup database backups" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:27 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:29 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:36 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-postgres-backup.md:17 -msgid "**Note**: for a more complete backup solution (one that includes not only Postgres, but also other configuration/data files), you may wish to look into [BorgBackup](configuring-playbook-backup-borg.md) instead." +#: ../../../docs/configuring-playbook-postgres-backup.md:38 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po index 7ec159a27..f30c1e6be 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,180 +19,126 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:14 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:1 msgid "Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server (optional)" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:16 -msgid "The playbook can install [Prometheus](https://prometheus.io/) with [Grafana](https://grafana.com/) and configure performance metrics of your homeserver with graphs for you." +#: ../../../docs/configuring-playbook-prometheus-grafana.md:3 +msgid "The playbook can install [Grafana](https://grafana.com/) with [Prometheus](https://prometheus.io/) and configure performance metrics of your homeserver with graphs for you." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:18 -msgid "[!WARNING] Metrics and graphs contain a lot of information, and anyone who has access to them can make an educated guess about your server usage patterns. This especially applies to small personal/family scale homeservers, where the number of samples is fairly limited. Analyzing the metrics over time, one might be able to figure out your life cycle, such as when you wake up, go to bed, etc. Before enabling (anonymous) access, you should carefully evaluate the risk, and if you do enable it, it is highly recommended to change your Grafana password from the default one." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:21 -msgid "Most of our Docker containers run with limited system access, but the `prometheus-node-exporter` can access the host network stack and (readonly) root filesystem. If it is fine, you can enable it and have it capture metrics about them (see [below](#enable-metrics-and-graphs-for-generic-system-information-optional) for the instruction). Even if `prometheus-node-exporter` is not enabled, you will still get Synapse homeserver metrics. Note that both of these dashboards are always be enabled, so you can still see historical data even after disabling either source." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:23 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:5 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:25 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:7 msgid "By default, this playbook installs Grafana web user-interface on the `stats.` subdomain (`stats.example.com`) and requires you to create a CNAME record for `stats`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:27 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:9 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:29 -msgid "**Note**: It is possible to install Prometheus without installing Grafana. In this case it is not required to create the CNAME record." +#: ../../../docs/configuring-playbook-prometheus-grafana.md:11 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:31 -msgid "Adjusting the playbook configuration — Prometheus" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:13 +msgid "To enable Grafana and/or Prometheus, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:33 -msgid "Prometheus is an open-source systems monitoring and alerting toolkit. It is a time series database, which holds all the data we're going to talk about." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:35 -msgid "To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:39 +msgid "The retention policy of Prometheus metrics is [15 days by default](https://prometheus.io/docs/prometheus/latest/storage/#operational-aspects). Older data gets deleted automatically." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:41 -msgid "**Note**: the retention policy of Prometheus metrics is [15 days by default](https://prometheus.io/docs/prometheus/latest/storage/#operational-aspects). Older data gets deleted automatically." +msgid "Adjusting the Grafana URL (optional)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:43 -msgid "Enable metrics and graphs for generic system information (optional)" +msgid "By tweaking the `grafana_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:45 -msgid "You can enable the [Node Exporter](https://prometheus.io/docs/guides/node-exporter/), an addon of sorts to Prometheus that collects generic system information such as CPU, memory, filesystem, and even system temperatures." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:47 -#: ../../../docs/configuring-playbook-prometheus-grafana.md:59 -#: ../../../docs/configuring-playbook-prometheus-grafana.md:83 -msgid "To enable it, add the following configuration to your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:53 -msgid "Enable metrics and graphs for Postgres (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:55 -msgid "Expanding on the metrics exposed by the Synapse exporter and the Node exporter, the playbook can also install and configure the [PostgreSQL Server Exporter](https://github.com/prometheus-community/postgres_exporter) that exposes more detailed information about what's happening on your Postgres database." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:57 -msgid "Enabling the exporter sets up the docker container, connects it to the database and adds a 'job' to the Prometheus config which tells Prometheus about this new exporter." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:61 -msgid "**Note**: `prometheus_postgres_exporter_database_username` has nothing to do with your Matrix user ID. It can be any string you'd like." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:75 -msgid "Enable metrics and graphs for nginx logs (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:77 -msgid "The playbook can also install and configure the [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) service for you." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:79 -msgid "It is an addon of sorts to expose nginx logs to Prometheus. The exporter will collect access logs from various nginx reverse-proxies which may be used internally (e.g. `matrix-synapse-reverse-proxy-companion`, if Synapse workers are enabled) and will make them available at a Prometheus-compatible `/metrics` endpoint." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:81 -msgid "See the project's [documentation](https://github.com/martin-helmich/prometheus-nginxlog-exporter/blob/master/README.adoc) to learn what it does and why it might be useful to you." +msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:89 -msgid "If you enable Grafana, a dedicated `NGINX PROXY` Grafana dashboard will be created." +#: ../../../docs/configuring-playbook-prometheus-grafana.md:52 +msgid "After changing the domain, **you may need to adjust your DNS** records to point the Grafana domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:91 -msgid "**Note**: nginx is only used internally by this Ansible playbook. With Traefik being our default reverse-proxy, collecting nginx metrics is less relevant." +#: ../../../docs/configuring-playbook-prometheus-grafana.md:54 +msgid "**Note**: It is possible to install Prometheus without installing Grafana. This case it is not required to create the CNAME record." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:93 -msgid "Docker image compatibility (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:95 -msgid "At the moment of writing only images for `amd64` and `arm64` architectures are available. The playbook currently does not support [self-building](./self-building.md) a container image on other architectures. You can however use a custom-build image by setting:" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:56 +msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:102 -msgid "Extending the configuration" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:58 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:104 -msgid "There are some additional things you may wish to configure about Prometheus and its add-on." +#: ../../../docs/configuring-playbook-prometheus-grafana.md:65 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:106 -msgid "Take a look at:" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:67 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:108 -msgid "[Prometheus role](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus/blob/main/defaults/main.yml) for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `prometheus_configuration_extension_yaml` variable" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:69 +msgid "What does it do?" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:109 -msgid "`roles/galaxy/prometheus_nginxlog_exporter/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Name" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:111 -msgid "Adjusting the playbook configuration — Grafana" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Description" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:113 -msgid "Grafana is an open source visualization and analytics software. To enable it, add the following configuration to your `vars.yml` file. Make sure to replace `USERNAME_HERE` and `PASSWORD_HERE`." +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`prometheus_enabled`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:115 -msgid "**Notes**:" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:116 -msgid "`grafana_default_admin_user` has nothing to do with your Matrix user ID. It can be any string you'd like." +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`prometheus_node_exporter_enabled`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:117 -msgid "Changing the username/password subsequently won't work." +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "[Node Exporter](https://prometheus.io/docs/guides/node-exporter/) is an addon of sorts to Prometheus that collects generic system information such as CPU, memory, filesystem, and even system temperatures" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Name" +msgid "`prometheus_postgres_exporter_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Description" +msgid "[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an addon of sorts to expose Postgres database metrics to Prometheus." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "`grafana_enabled`" +msgid "`matrix_prometheus_nginxlog_exporter_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "[Grafana](https://grafana.com/) is the visual component. It shows (on the `stats.example.com` subdomain) the dashboards with the graphs that we're interested in." +msgid "[NGINX Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose NGINX logs to Prometheus." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "`grafana_default_admin_user`
`grafana_default_admin_password`" +msgid "`grafana_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "By default Grafana creates a user with `admin` as the username and password. You are asked to change the credentials on first login. If you feel this is insecure and you want to change them beforehand, you can do that here." +msgid "[Grafana](https://grafana.com/) is the visual component. It shows (on the `stats.example.com` subdomain) the dashboards with the graphs that we're interested in" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md @@ -203,63 +149,47 @@ msgstr "" msgid "By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:135 -msgid "Adjusting the Grafana URL (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:137 -msgid "By tweaking the `grafana_hostname` variable, you can easily make the service available at a **different hostname** than the default one." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:139 -msgid "Example additional configuration for your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:146 -msgid "After changing the domain, **you may need to adjust your DNS** records to point the Grafana domain to the Matrix server." +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`grafana_default_admin_user`
`grafana_default_admin_password`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:148 -msgid "Installing" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "By default Grafana creates a user with `admin` as the username and password. If you feel this is insecure and you want to change it beforehand, you can do that here" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:150 -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:" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:81 +msgid "Security and privacy" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:157 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:83 +msgid "Metrics and resulting graphs can contain a lot of information. This includes system specs but also usage patterns. This applies especially to small personal/family scale homeservers. Someone might be able to figure out when you wake up and go to sleep by looking at the graphs over time. Think about this before enabling anonymous access. And you should really not forget to change your Grafana password." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:159 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-prometheus-grafana.md:85 +msgid "Most of our docker containers run with limited system access, but the `prometheus-node-exporter` has access to the host network stack and (readonly) root filesystem. This is required to report on them. If you don't like that, you can set `prometheus_node_exporter_enabled: false` (which is actually the default). You will still get Synapse metrics with this container disabled. Both of the dashboards will always be enabled, so you can still look at historical data after disabling either source." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:161 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:87 msgid "Collecting metrics to an external Prometheus server" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:163 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:89 msgid "**If the integrated Prometheus server is enabled** (`prometheus_enabled: true`), metrics are collected by it from each service via communication that happens over the container network. Each service does not need to expose its metrics \"publicly\"." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:165 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:91 msgid "When you'd like **to collect metrics from an external Prometheus server**, you need to expose service metrics outside of the container network." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:167 -msgid "The playbook provides a single endpoint (`https://matrix.example.com/metrics/*`), under which various services may expose their metrics (e.g. `/metrics/node-exporter`, `/metrics/postgres-exporter`, `/metrics/nginxlog`, `/metrics/hookshot`, etc)." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:169 -msgid "To expose all services on this `/metrics/*` feature, you can use `matrix_metrics_exposure_enabled`. When using it, you don't need to expose metrics for individual services one by one. If you think this is too much, refer [this section](#expose-metrics-of-other-services-roles) for details about exposing metrics on a per-service basis." +#: ../../../docs/configuring-playbook-prometheus-grafana.md:93 +msgid "The playbook provides a single endpoint (`https://matrix.example.com/metrics/*`), under which various services may expose their metrics (e.g. `/metrics/node-exporter`, `/metrics/postgres-exporter`, `/metrics/hookshot`, etc). To expose all services on this `/metrics/*` feature, use `matrix_metrics_exposure_enabled`. To protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication), see `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users` below." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:171 -msgid "To protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication), you can use `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`. When enabled, all endpoints beneath `/metrics` will be protected with the same credentials. Alternatively, you can protect each endpoint with dedicated credentials. Refer [the section](#expose-metrics-of-other-services-roles) below for details about it." +#: ../../../docs/configuring-playbook-prometheus-grafana.md:95 +msgid "When using `matrix_metrics_exposure_enabled`, you don't need to expose metrics for individual services one by one." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:173 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:97 msgid "The following variables may be of interest:" msgstr "" @@ -268,7 +198,7 @@ msgid "`matrix_metrics_exposure_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Set this to `true` to **enable metrics exposure for all services** on `https://matrix.example.com/metrics/*`." +msgid "Set this to `true` to **enable metrics exposure for all services** on `https://matrix.example.com/metrics/*`. If you think this is too much, refer to the helpful (but nonexhaustive) list of individual `matrix_SERVICE_metrics_proxying_enabled` (or similar) variables below for exposing metrics on a per-service basis." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md @@ -276,7 +206,7 @@ msgid "`matrix_metrics_exposure_http_basic_auth_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Set this to `true` to protect all `https://matrix.example.com/metrics/*` endpoints with [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) (see the other variables below for supplying the actual credentials)." +msgid "Set this to `true` to protect all `https://matrix.example.com/metrics/*` endpoints with [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) (see the other variables below for supplying the actual credentials). When enabled, all endpoints beneath `/metrics` will be protected with the same credentials" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md @@ -288,137 +218,129 @@ msgid "Set this to the Basic Authentication credentials (raw `htpasswd` file con msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "`prometheus_node_exporter_enabled`" +msgid "`matrix_synapse_metrics_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Set this to `true` to enable the node (general system stats) exporter (locally, on the container network)." +msgid "Set this to `true` to make Synapse expose metrics (locally, on the container network)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "`prometheus_node_exporter_container_labels_metrics_enabled`" +msgid "`matrix_synapse_metrics_proxying_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Set this to `true` to expose the node (general system stats) metrics on `https://matrix.example.com/metrics/node-exporter`." +msgid "Set this to `true` to expose Synapse's metrics on `https://matrix.example.com/metrics/synapse/main-process` and `https://matrix.example.com/metrics/synapse/worker/TYPE-ID`. Read [below](#collecting-synapse-worker-metrics-to-an-external-prometheus-server) if you're running a Synapse worker setup (`matrix_synapse_workers_enabled: true`). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "`prometheus_postgres_exporter_enabled`" +msgid "Set this to `true` to enable the node (general system stats) exporter (locally, on the container network)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Set this to `true` to enable the [Postgres exporter](#enable-metrics-and-graphs-for-postgres-optional) (locally, on the container network)." +msgid "`prometheus_node_exporter_container_labels_traefik_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "`prometheus_postgres_exporter_container_labels_metrics_enabled`" +msgid "Set this to `true` to expose the node (general system stats) metrics on `https://matrix.example.com/metrics/node-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Set this to `true` to expose the [Postgres exporter](#enable-metrics-and-graphs-for-postgres-optional) metrics on `https://matrix.example.com/metrics/postgres-exporter`." +msgid "Set this to `true` to enable the [Postgres exporter](configuring-playbook-prometheus-postgres.md) (locally, on the container network)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "`prometheus_nginxlog_exporter_enabled`" +msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Set this to `true` to enable the [prometheus-nginxlog-exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) (locally, on the container network)." +msgid "Set this to `true` to expose the [Postgres exporter](configuring-playbook-prometheus-postgres.md) metrics on `https://matrix.example.com/metrics/postgres-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "`prometheus_nginxlog_exporter_container_labels_metrics_enabled`" +msgid "Set this to `true` to enable the [NGINX Log exporter](configuring-playbook-prometheus-nginxlog.md) (locally, on the container network)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Set this to `true` to expose the [prometheus-nginxlog-exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) metrics on `https://matrix.example.com/metrics/nginxlog`." +msgid "`matrix_sliding_sync_metrics_enabled`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:187 -msgid "Expose metrics of other services/roles" -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:189 -msgid "Various other services/roles may provide similar `_metrics_enabled` and `_metrics_proxying_enabled` variables for exposing their metrics. Refer to each role for details." +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) expose metrics (locally, on the container network)" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:191 -msgid "To password-protect the metrics of a specific role, you can use `matrix_SERVICE_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_SERVICE_container_labels_metrics_middleware_basic_auth_users` variables provided by the role." +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_sliding_sync_metrics_proxying_enabled`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:193 -msgid "**Note**: alternatively you can use `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users` in order to password-protect the metrics of all services." +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Set this to `true` to expose the [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) metrics on `https://matrix.example.com/metrics/sliding-sync`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:195 -msgid "For example, you can enable and expose metrics for Synapse protecting them with dedicated credentials by adding the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_bridge_hookshot_metrics_enabled`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:213 -msgid "Collecting Synapse worker metrics to an external Prometheus server" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Set this to `true` to make [Hookshot](configuring-playbook-bridge-hookshot.md) expose metrics (locally, on the container network)" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:215 -msgid "If you are using workers (`matrix_synapse_workers_enabled: true`) and have enabled `matrix_synapse_metrics_proxying_enabled` as described above, the playbook will also automatically expose all Synapse worker threads' metrics to `https://matrix.example.com/metrics/synapse/worker/ID`, where `ID` corresponds to the worker `id` as exemplified in `matrix_synapse_workers_enabled_list`." +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_bridge_hookshot_metrics_proxying_enabled`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:217 -msgid "The playbook also generates an exemplary config file (`/matrix/synapse/external_prometheus.yml.template`) with all the correct paths which you can copy to your Prometheus server and adapt to your needs. Make sure to edit the specified `password_file` path and contents and path to your `synapse-v2.rules`. It will look a bit like this:" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Set this to `true` to expose the [Hookshot](configuring-playbook-bridge-hookshot.md) metrics on `https://matrix.example.com/metrics/hookshot`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:245 -msgid "Troubleshooting" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_SERVICE_metrics_proxying_enabled`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:247 -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 the commands below:" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Various other services/roles may provide similar `_metrics_enabled` and `_metrics_proxying_enabled` variables for exposing their metrics. Refer to each role for details. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above or `matrix_SERVICE_container_labels_metrics_middleware_basic_auth_enabled`/`matrix_SERVICE_container_labels_metrics_middleware_basic_auth_users` variables provided by each role." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:248 -msgid "`journalctl -fu matrix-prometheus` for Prometheus" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_media_repo_metrics_enabled`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:249 -msgid "`journalctl -fu matrix-prometheus-node-exporter` for Node Exporter" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Set this to `true` to make media-repo expose metrics (locally, on the container network)" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:250 -msgid "`journalctl -fu matrix-prometheus-postgres-exporter` for PostgreSQL Server Exporter" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:118 +msgid "Collecting Synapse worker metrics to an external Prometheus server" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:251 -msgid "`journalctl -fu matrix-prometheus-nginxlog-exporter` for prometheus-nginxlog-exporter" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:120 +msgid "If you are using workers (`matrix_synapse_workers_enabled: true`) and have enabled `matrix_synapse_metrics_proxying_enabled` as described above, the playbook will also automatically expose all Synapse worker threads' metrics to `https://matrix.example.com/metrics/synapse/worker/ID`, where `ID` corresponds to the worker `id` as exemplified in `matrix_synapse_workers_enabled_list`." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:252 -msgid "`journalctl -fu matrix-grafana` for Grafana" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:122 +msgid "The playbook also generates an exemplary config file (`/matrix/synapse/external_prometheus.yml.template`) with all the correct paths which you can copy to your Prometheus server and adapt to your needs. Make sure to edit the specified `password_file` path and contents and path to your `synapse-v2.rules`. It will look a bit like this:" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:254 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:150 msgid "More information" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:256 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:152 msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:257 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:153 msgid "[Understanding Synapse Performance Issues Through Grafana Graphs](https://element-hq.github.io/synapse/latest/usage/administration/understanding_synapse_through_grafana_graphs.html) at the Synapse Github Wiki" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:258 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:154 msgid "[The Prometheus scraping rules](https://github.com/element-hq/synapse/tree/master/contrib/prometheus) (we use v2)" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:259 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:155 msgid "[The Synapse Grafana dashboard](https://github.com/element-hq/synapse/tree/master/contrib/grafana)" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:260 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:156 msgid "[The Node Exporter dashboard](https://github.com/rfrail3/grafana-dashboards) (for generic non-synapse performance graphs)" msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:261 -msgid "[The PostgreSQL dashboard](https://grafana.com/grafana/dashboards/9628) (generic Postgres dashboard)" -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rageshake.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rageshake.po index cddd275c2..c1cfbd38d 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rageshake.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rageshake.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,112 +19,92 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-rageshake.md:8 +#: ../../../docs/configuring-playbook-rageshake.md:1 msgid "Setting up the rageshake bug report server (optional)" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:10 +#: ../../../docs/configuring-playbook-rageshake.md:3 msgid "The playbook can install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server for you." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:12 +#: ../../../docs/configuring-playbook-rageshake.md:5 msgid "See the project's [documentation](https://github.com/matrix-org/rageshake/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:14 +#: ../../../docs/configuring-playbook-rageshake.md:7 msgid "**Note**: most people don't need to install rageshake to collect bug reports. This component is only useful to people who develop/build their own Matrix client applications themselves." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:16 +#: ../../../docs/configuring-playbook-rageshake.md:9 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:18 +#: ../../../docs/configuring-playbook-rageshake.md:11 msgid "By default, this playbook installs rageshake on the `rageshake.` subdomain (`rageshake.example.com`) and requires you to create a CNAME record for `rageshake`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:20 +#: ../../../docs/configuring-playbook-rageshake.md:13 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:22 +#: ../../../docs/configuring-playbook-rageshake.md:15 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:24 +#: ../../../docs/configuring-playbook-rageshake.md:17 msgid "To enable rageshake, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:30 +#: ../../../docs/configuring-playbook-rageshake.md:23 +msgid "rageshake has various options which don't have dedicated Ansible variables. You can see the full list of options in the [`rageshake.sample.yaml` file](https://github.com/matrix-org/rageshake/blob/master/rageshake.sample.yaml)." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:25 +msgid "To set these, you can make use of the `matrix_rageshake_configuration_extension_yaml` variable like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:35 msgid "Adjusting the rageshake URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:32 +#: ../../../docs/configuring-playbook-rageshake.md:37 msgid "By tweaking the `matrix_rageshake_hostname` and `matrix_rageshake_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:34 +#: ../../../docs/configuring-playbook-rageshake.md:39 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:45 +#: ../../../docs/configuring-playbook-rageshake.md:50 msgid "After changing the domain, **you may need to adjust your DNS** records to point the rageshake domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:47 +#: ../../../docs/configuring-playbook-rageshake.md:52 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:49 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-rageshake.md:51 -msgid "There are some additional things you may wish to configure about the server." -msgstr "" - -#: ../../../docs/configuring-playbook-rageshake.md:53 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-rageshake.md:55 -msgid "`roles/custom/matrix-rageshake/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-rageshake.md:56 -msgid "`roles/custom/matrix-rageshake/templates/config.yaml.j2` for the server's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_rageshake_configuration_extension_yaml` variable" -msgstr "" - -#: ../../../docs/configuring-playbook-rageshake.md:74 +#: ../../../docs/configuring-playbook-rageshake.md:54 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:76 +#: ../../../docs/configuring-playbook-rageshake.md:56 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:83 +#: ../../../docs/configuring-playbook-rageshake.md:63 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:85 +#: ../../../docs/configuring-playbook-rageshake.md:65 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:87 +#: ../../../docs/configuring-playbook-rageshake.md:67 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:89 +#: ../../../docs/configuring-playbook-rageshake.md:69 msgid "Refer to the project's [documentation](https://github.com/matrix-org/rageshake/blob/main/README.md) for available APIs, etc." msgstr "" - -#: ../../../docs/configuring-playbook-rageshake.md:91 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-rageshake.md:93 -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-rageshake`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rest-auth.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rest-auth.po index 718dd330a..df2795e33 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rest-auth.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rest-auth.po @@ -8,63 +8,55 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2026-02-13 10:32+0000\n" +"POT-Creation-Date: 2024-12-20 09:53+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-rest-auth.md:9 +#: ../../../docs/configuring-playbook-rest-auth.md:1 msgid "Setting up the REST authentication password provider module (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:11 +#: ../../../docs/configuring-playbook-rest-auth.md:3 msgid "The playbook can install and configure [matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) for you." msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:13 +#: ../../../docs/configuring-playbook-rest-auth.md:5 msgid "See the project's [documentation](https://github.com/ma1uta/matrix-synapse-rest-password-provider/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:15 +#: ../../../docs/configuring-playbook-rest-auth.md:7 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:17 +#: ../../../docs/configuring-playbook-rest-auth.md:9 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:27 +#: ../../../docs/configuring-playbook-rest-auth.md:19 msgid "Authenticating only using a password provider" msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:29 -msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, you can disable it by adding the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-rest-auth.md:21 +msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:" msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:35 +#: ../../../docs/configuring-playbook-rest-auth.md:27 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:37 +#: ../../../docs/configuring-playbook-rest-auth.md:29 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:44 +#: ../../../docs/configuring-playbook-rest-auth.md:36 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:46 +#: ../../../docs/configuring-playbook-rest-auth.md:38 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-rest-auth.md:48 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-rest-auth.md:50 -msgid "This module does not provide direct integration with any backend. Please prepare one by yourself for it." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po index c222ee2e0..69b21cad4 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,177 +19,165 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-s3-goofys.md:8 -msgid "Storing Synapse media files on Amazon S3 with Goofys (optional)" +#: ../../../docs/configuring-playbook-s3-goofys.md:1 +msgid "Storing Matrix media files on Amazon S3 with Goofys (optional)" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:10 -msgid "The playbook can install and configure [Goofys](https://github.com/kahing/goofys) for you." +#: ../../../docs/configuring-playbook-s3-goofys.md:3 +msgid "If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service), you can let this playbook configure [Goofys](https://github.com/kahing/goofys) for you." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:12 -msgid "Goofys makes it possible to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service) object storage." +#: ../../../docs/configuring-playbook-s3-goofys.md:5 +msgid "Another (and better performing) way to use S3 storage with Synapse is [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md)." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:14 -msgid "See the project's [documentation](https://github.com/kahing/goofys/blob/master/README.md) to learn what it does and why it might be useful to you." +#: ../../../docs/configuring-playbook-s3-goofys.md:7 +msgid "Using a Goofys-backed media store works, but performance may not be ideal. If possible, try to use a region which is close to your Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:16 -msgid "**Note**: as performance of a Goofys-backed media store may not be ideal, you may wish to use [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) instead, another (and better performing) way to mount a S3 bucket for Synapse." +#: ../../../docs/configuring-playbook-s3-goofys.md:9 +msgid "If you'd like to move your locally-stored media store data to Amazon S3 (or another S3-compatible object store), we also provide some migration instructions below." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:18 -msgid "If you'd like to move your locally-stored media store data to Amazon S3 (or another S3-compatible object store), you can refer our migration instructions below." -msgstr "" - -#: ../../../docs/configuring-playbook-s3-goofys.md:20 +#: ../../../docs/configuring-playbook-s3-goofys.md:11 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:22 +#: ../../../docs/configuring-playbook-s3-goofys.md:13 msgid "After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:32 +#: ../../../docs/configuring-playbook-s3-goofys.md:23 msgid "You can use any S3-compatible object store by **additionally** configuring these variables:" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:39 +#: ../../../docs/configuring-playbook-s3-goofys.md:30 msgid "If you have local media store files and wish to migrate to Backblaze B2 subsequently, follow our [migration guide to Backblaze B2](#migrating-to-backblaze-b2) below instead of applying this configuration as-is." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:41 +#: ../../../docs/configuring-playbook-s3-goofys.md:32 msgid "Migrating from local filesystem storage to S3" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:43 +#: ../../../docs/configuring-playbook-s3-goofys.md:34 msgid "It's a good idea to [make a complete server backup](faq.md#how-do-i-back-up-the-data-on-my-server) before migrating your local media store to an S3-backed one." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:45 +#: ../../../docs/configuring-playbook-s3-goofys.md:36 msgid "After making the backup, follow one of the guides below for a migration path from a locally-stored media store to one stored on S3-compatible storage:" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:47 +#: ../../../docs/configuring-playbook-s3-goofys.md:38 msgid "[Migrating to any S3-compatible storage (universal, but likely slow)](#migrating-to-any-s3-compatible-storage-universal-but-likely-slow)" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:48 +#: ../../../docs/configuring-playbook-s3-goofys.md:39 msgid "[Migrating to Backblaze B2](#migrating-to-backblaze-b2)" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:50 +#: ../../../docs/configuring-playbook-s3-goofys.md:41 msgid "Migrating to any S3-compatible storage (universal, but likely slow)" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:52 +#: ../../../docs/configuring-playbook-s3-goofys.md:43 msgid "Proceed with the steps below without stopping Matrix services" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:54 +#: ../../../docs/configuring-playbook-s3-goofys.md:45 msgid "Start by adding the base S3 configuration in your `vars.yml` file (seen above, may be different depending on the S3 provider of your choice)" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:56 +#: ../../../docs/configuring-playbook-s3-goofys.md:47 msgid "In addition to the base configuration you see above, add this to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:62 +#: ../../../docs/configuring-playbook-s3-goofys.md:53 msgid "This enables S3 support, but mounts the S3 storage bucket to `/matrix/s3-media-store` without hooking it to your homeserver yet. Your homeserver will still continue using your local filesystem for its media store." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:64 +#: ../../../docs/configuring-playbook-s3-goofys.md:55 msgid "Run the playbook to apply the changes: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:66 +#: ../../../docs/configuring-playbook-s3-goofys.md:57 msgid "Do an **initial sync of your files** by running this **on the server** (it may take a very long time):" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:72 +#: ../../../docs/configuring-playbook-s3-goofys.md:63 msgid "You may need to install `rsync` manually." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:74 -#: ../../../docs/configuring-playbook-s3-goofys.md:115 +#: ../../../docs/configuring-playbook-s3-goofys.md:65 +#: ../../../docs/configuring-playbook-s3-goofys.md:106 msgid "Stop all Matrix services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:76 +#: ../../../docs/configuring-playbook-s3-goofys.md:67 msgid "Start the S3 service by running this **on the server**: `systemctl start matrix-goofys`" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:78 +#: ../../../docs/configuring-playbook-s3-goofys.md:69 msgid "Sync the files again by re-running the `rsync` command you see in step #5" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:80 +#: ../../../docs/configuring-playbook-s3-goofys.md:71 msgid "Stop the S3 service by running this **on the server**: `systemctl stop matrix-goofys`" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:82 -#: ../../../docs/configuring-playbook-s3-goofys.md:123 +#: ../../../docs/configuring-playbook-s3-goofys.md:73 +#: ../../../docs/configuring-playbook-s3-goofys.md:114 msgid "Get the old media store out of the way by running this command on the server:" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:88 +#: ../../../docs/configuring-playbook-s3-goofys.md:79 msgid "Remove the `matrix_s3_media_store_path` configuration from your `vars.yml` file (undoing step #3 above)" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:90 -#: ../../../docs/configuring-playbook-s3-goofys.md:131 +#: ../../../docs/configuring-playbook-s3-goofys.md:81 +#: ../../../docs/configuring-playbook-s3-goofys.md:122 msgid "Run the playbook: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:92 -#: ../../../docs/configuring-playbook-s3-goofys.md:133 +#: ../../../docs/configuring-playbook-s3-goofys.md:83 +#: ../../../docs/configuring-playbook-s3-goofys.md:124 msgid "You're done! Verify that loading existing (old) media files works and that you can upload new ones." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:94 -#: ../../../docs/configuring-playbook-s3-goofys.md:135 +#: ../../../docs/configuring-playbook-s3-goofys.md:85 +#: ../../../docs/configuring-playbook-s3-goofys.md:126 msgid "When confident that it all works, get rid of the local media store directory: `rm -rf /matrix/synapse/storage/media-store-local-backup`" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:96 +#: ../../../docs/configuring-playbook-s3-goofys.md:87 msgid "Migrating to Backblaze B2" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:98 +#: ../../../docs/configuring-playbook-s3-goofys.md:89 msgid "While all Matrix services are running, run the following command on the server:" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:100 +#: ../../../docs/configuring-playbook-s3-goofys.md:91 msgid "(you need to adjust the 3 `--env` line below with your own data)" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:113 +#: ../../../docs/configuring-playbook-s3-goofys.md:104 msgid "This is some initial file sync, which may take a very long time." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:117 +#: ../../../docs/configuring-playbook-s3-goofys.md:108 msgid "Run the command from step #1 again." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:119 +#: ../../../docs/configuring-playbook-s3-goofys.md:110 msgid "Doing this will sync any new files that may have been created locally in the meantime." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:121 +#: ../../../docs/configuring-playbook-s3-goofys.md:112 msgid "Now that Matrix services aren't running, we're sure to get Backblaze B2 and your local media store fully in sync." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:129 +#: ../../../docs/configuring-playbook-s3-goofys.md:120 msgid "Put the [Backblaze B2 settings](configuring-playbook-s3.md#backblaze-b2) in your `vars.yml` file" msgstr "" - -#: ../../../docs/configuring-playbook-s3-goofys.md:137 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-s3-goofys.md:139 -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-goofys`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3.po index aea8548b1..26200a384 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,196 +19,200 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-s3.md:9 +#: ../../../docs/configuring-playbook-s3.md:1 msgid "Storing Synapse media files on Amazon S3 or another compatible Object Storage (optional)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:11 +#: ../../../docs/configuring-playbook-s3.md:3 msgid "By default, this playbook configures your server to store Synapse's content repository (`media_store`) files on the local filesystem. If that's okay, you can skip this document." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:13 +#: ../../../docs/configuring-playbook-s3.md:5 msgid "As an alternative to storing media files on the local filesystem, you can store them on [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object store." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:15 +#: ../../../docs/configuring-playbook-s3.md:7 msgid "You can do this either by sticking to Synapse's media repository and making that use S3 (read below for this method), or by switching to an external media storage implementation like [matrix-media-repo](configuring-playbook-matrix-media-repo.md)." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:17 +#: ../../../docs/configuring-playbook-s3.md:9 msgid "First, [choose an Object Storage provider](#choosing-an-object-storage-provider)." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:19 +#: ../../../docs/configuring-playbook-s3.md:11 msgid "Then, [create the S3 bucket](#bucket-creation-and-security-configuration)." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:21 +#: ../../../docs/configuring-playbook-s3.md:13 msgid "Finally, [set up S3 storage for Synapse](#setting-up) (with [Goofys](configuring-playbook-s3-goofys.md), [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md), or use s3 datastore with the [matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/configuration/s3-datastore.html))." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:23 +#: ../../../docs/configuring-playbook-s3.md:15 msgid "Choosing an Object Storage provider" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:25 -msgid "You can create [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object storage like [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html), [Wasabi](https://wasabi.com), [Digital Ocean Spaces](https://www.digitalocean.com/products/spaces), [Storj](https://storj.io), etc." +#: ../../../docs/configuring-playbook-s3.md:17 +msgid "You can create [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object storage like [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html), [Storj](https://storj.io), [Wasabi](https://wasabi.com), [Digital Ocean Spaces](https://www.digitalocean.com/products/spaces), etc." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:27 -msgid "Amazon S3 and Backblaze B2 are pay-as-you with no minimum charges for storing too little data. Note that Backblaze egress is free, but for only certain users for up to 3x the amount of data stored. Beyond that you will pay $0.01/GB of egress." +#: ../../../docs/configuring-playbook-s3.md:19 +msgid "Amazon S3, Backblaze B2, and Storj are pay-as-you with no minimum charges for storing too little data." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:29 -msgid "Wasabi has a minimum charge of 1TB if you're storing less than 1TB, which becomes expensive if you need to store less data than that. Likewise, Digital Ocean Spaces has also a minimum charge of 250GB ($5/month as of 2022-10). Though Storj does not set minimum amount of data to be stored, it also charges $5 minimum monthly usage fee since July 1, 2025, if your monthly usage (storage, bandwidth, and segments) totals less than $5." +#: ../../../docs/configuring-playbook-s3.md:21 +msgid "All these providers have different prices, with Storj appearing to be the cheapest (as of 2024-10, storage fee is $0.004 per GB/month, and egress fee is $0.007 per GB). Backblaze egress is free, but for only certain users for up to 3x the amount of data stored. Beyond that you will pay $0.01/GB of egress." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:31 +#: ../../../docs/configuring-playbook-s3.md:23 +msgid "Wasabi has a minimum charge of 1TB if you're storing less than 1TB, which becomes expensive if you need to store less data than that. Likewise, Digital Ocean Spaces has also a minimum charge of 250GB ($5/month as of 2022-10)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:25 msgid "Here are some of the important aspects of choosing the right provider:" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:33 +#: ../../../docs/configuring-playbook-s3.md:27 msgid "if a provider is a company you like and trust (or dislike less than the others)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:34 +#: ../../../docs/configuring-playbook-s3.md:28 msgid "if a provider implements end-to-end encryption of your data" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:35 +#: ../../../docs/configuring-playbook-s3.md:29 msgid "if a provider has a data region close to your Matrix server (if it's farther away, high latency may cause slowdowns)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:36 +#: ../../../docs/configuring-playbook-s3.md:30 msgid "if a provider's infrastructure such as data center is centralized or distributed" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:37 +#: ../../../docs/configuring-playbook-s3.md:31 msgid "if a provider's price model is transparent (whether it includes hidden costs like minimum charge, minimum storage term, etc.)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:38 +#: ../../../docs/configuring-playbook-s3.md:32 msgid "if a provider has free or cheap egress fee (in case you need to get the data out often, for some reason) — likely not too important for the common use-case" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:40 +#: ../../../docs/configuring-playbook-s3.md:34 msgid "Bucket creation and Security Configuration" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:42 +#: ../../../docs/configuring-playbook-s3.md:36 msgid "Now that you've [chosen an Object Storage provider](#choosing-an-object-storage-provider), you need to create a storage bucket." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:44 +#: ../../../docs/configuring-playbook-s3.md:38 msgid "How you do this varies from provider to provider, with Amazon S3 being the most complicated due to its vast number of services and complicated security policies." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:46 +#: ../../../docs/configuring-playbook-s3.md:40 msgid "Below, we provider some guides for common providers. If you don't see yours, look at the others for inspiration or read some guides online about how to create a bucket. Feel free to contribute to this documentation with an update!" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:48 +#: ../../../docs/configuring-playbook-s3.md:42 msgid "Amazon S3" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:50 +#: ../../../docs/configuring-playbook-s3.md:44 msgid "You'll need an Amazon S3 bucket and some IAM user credentials (access key + secret key) with full write access to the bucket. Example IAM security policy:" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:71 +#: ../../../docs/configuring-playbook-s3.md:65 msgid "**Note**: This policy needs to be attached to an IAM user created from the **Security Credentials** menu. This is not a **Bucket Policy**." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:73 +#: ../../../docs/configuring-playbook-s3.md:67 msgid "Backblaze B2" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:75 +#: ../../../docs/configuring-playbook-s3.md:69 msgid "To use [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html) you first need to sign up." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:77 +#: ../../../docs/configuring-playbook-s3.md:71 msgid "You [can't easily change which region (US, Europe) your Backblaze account stores files in](https://old.reddit.com/r/backblaze/comments/hi1v90/make_the_choice_for_the_b2_data_center_region/), so make sure to carefully choose the region when signing up (hint: it's a hard to see dropdown below the username/password fields in the signup form)." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:79 +#: ../../../docs/configuring-playbook-s3.md:73 msgid "After logging in to Backblaze:" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:81 +#: ../../../docs/configuring-playbook-s3.md:75 msgid "create a new **private** bucket through its user interface (you can call it something like `matrix-example-media-store`)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:82 +#: ../../../docs/configuring-playbook-s3.md:76 msgid "note the **Endpoint** for your bucket (something like `s3.us-west-002.backblazeb2.com`)." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:83 +#: ../../../docs/configuring-playbook-s3.md:77 msgid "adjust its Lifecycle Rules to: Keep only the last version of the file" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:84 +#: ../../../docs/configuring-playbook-s3.md:78 msgid "go to [App Keys](https://secure.backblaze.com/app_keys.htm) and use the **Add a New Application Key** to create a new one" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:85 +#: ../../../docs/configuring-playbook-s3.md:79 msgid "restrict it to the previously created bucket (e.g. `matrix-example-media-store`)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:86 +#: ../../../docs/configuring-playbook-s3.md:80 msgid "give it *Read & Write* access" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:88 +#: ../../../docs/configuring-playbook-s3.md:82 msgid "The `keyID` value is your **Access Key** and `applicationKey` is your **Secret Key**." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:90 +#: ../../../docs/configuring-playbook-s3.md:84 msgid "For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3-synapse-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) you will need:" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:92 +#: ../../../docs/configuring-playbook-s3.md:86 msgid "**Endpoint URL** — this is the **Endpoint** value you saw above, but prefixed with `https://`" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:93 +#: ../../../docs/configuring-playbook-s3.md:88 msgid "**Region** — use the value you see in the Endpoint (e.g. `us-west-002`)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:94 +#: ../../../docs/configuring-playbook-s3.md:90 msgid "**Storage Class** — use `STANDARD`. Backblaze B2 does not have different storage classes, so it doesn't make sense to use any other value." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:96 +#: ../../../docs/configuring-playbook-s3.md:92 msgid "Other providers" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:98 -msgid "For other S3-compatible providers, you most likely just need to create an S3 bucket and get some credentials (access key and secret key) for accessing the bucket in a read/write manner. You may not need to configure security policies, etc." +#: ../../../docs/configuring-playbook-s3.md:94 +msgid "For other S3-compatible providers, you may not need to configure security policies, etc. (just like for [Backblaze B2](#backblaze-b2))." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:100 -msgid "For details about setting up a bucket at Storj, please see the instruction [here](https://storj.dev/dcs/getting-started) to get started." +#: ../../../docs/configuring-playbook-s3.md:96 +msgid "You most likely just need to create an S3 bucket and get some credentials (access key and secret key) for accessing the bucket in a read/write manner." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:102 +#: ../../../docs/configuring-playbook-s3.md:98 msgid "Setting up" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:104 +#: ../../../docs/configuring-playbook-s3.md:100 msgid "To set up Synapse to store files in S3, follow the instructions for the method of your choice:" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:106 +#: ../../../docs/configuring-playbook-s3.md:102 msgid "using [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) (recommended)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:107 +#: ../../../docs/configuring-playbook-s3.md:103 msgid "using [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:108 +#: ../../../docs/configuring-playbook-s3.md:104 msgid "using [matrix-media-repo](configuring-playbook-matrix-media-repo.md)" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po index c25e021ea..6622bf13e 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po @@ -10,7 +10,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: 2024-12-20 09:53+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,48 +19,48 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:9 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:1 msgid "Setting up the Shared Secret Auth password provider module (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:11 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:3 msgid "The playbook can install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you." msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:13 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:5 msgid "See the project's [documentation](https://github.com/devture/matrix-synapse-shared-secret-auth/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:15 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:7 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:17 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:9 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:26 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:18 msgid "Authenticating only using a password provider" msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:28 -msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, you can disable it by adding the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-shared-secret-auth.md:20 +msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:" msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:34 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:26 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:36 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:28 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:43 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:35 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:45 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:37 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po index 7569014e7..389cf6dac 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,20 +19,100 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:18 -msgid "Setting up the Sliding Sync proxy (optional, removed)" +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:1 +msgid "Setting up the Sliding Sync proxy (optional)" msgstr "" -#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:20 -msgid "🪦 The playbook used to be able to install and configure the [sliding-sync](https://github.com/matrix-org/sliding-sync) proxy, but no longer includes this component, as it's been replaced with a different method (called Simplified Sliding Sync) integrated to newer homeservers by default (**Conduit** homeserver from version `0.6.0` or **Synapse** from version `1.114`)." +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:3 +msgid "**Note**: The sliding-sync proxy is **not required** anymore as it's been replaced with a different method (called Simplified Sliding Sync) which is integrated into newer homeservers by default (**Conduit** homeserver from version `0.6.0` or **Synapse** from version `1.114`). This component and documentation remain here for historical purposes, but **installing this old sliding-sync proxy is generally not recommended anymore**." msgstr "" -#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:22 -msgid "Uninstalling the proxy manually" +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:5 +msgid "The playbook can install and configure [sliding-sync](https://github.com/matrix-org/sliding-sync) proxy for you." msgstr "" -#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:24 -msgid "If you still have the Sliding Sync proxy 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:" +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:7 +msgid "Sliding Sync is an implementation of [MSC3575](https://github.com/matrix-org/matrix-spec-proposals/blob/kegan/sync-v3/proposals/3575-sync.md) and a prerequisite for running Element X clients ([Element X iOS](https://github.com/element-hq/element-x-ios) and [Element X Android](https://github.com/element-hq/element-x-android)). See the project's [documentation](https://github.com/matrix-org/sliding-sync) to learn more." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:9 +msgid "Adjusting DNS records (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:11 +msgid "By default, this playbook installs the Sliding Sync proxy on the `matrix.` subdomain, at the `/sliding-sync` path (https://matrix.example.com/sliding-sync). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:13 +msgid "If you wish to adjust it, see the section [below](#adjusting-the-sliding-sync-proxy-url-optional) for details about DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:17 +msgid "To enable Sliding Sync proxy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:23 +msgid "Adjusting the Sliding Sync proxy URL (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:25 +msgid "By tweaking the `matrix_sliding_sync_hostname` and `matrix_sliding_sync_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:27 +msgid "Example additional configuration for your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:35 +msgid "If you've changed the default hostname, you may need to create a CNAME record for the Sliding Sync proxy domain (`ss.example.com`), which targets `matrix.example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:37 +msgid "When setting, replace `example.com` with your own." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:39 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:41 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:48 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:50 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:52 +msgid "External databases" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:54 +msgid "Please note that, if your setup utilizes an external database, you must also establish configuration for the sliding sync proxy. Alter the defaults below to suit your configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:64 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:66 +msgid "You **don't need to do anything special** to make use of the Sliding Sync proxy. Simply open your client which supports Sliding Sync (like Element X) and log in." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:68 +msgid "When the Sliding Sync proxy is [installed](#installing), your `/.well-known/matrix/client` file is also updated. A new `org.matrix.msc3575.proxy` section and `url` property are added there and made to point to your Sliding Sync proxy's base URL (e.g. `https://matrix.example.com/sliding-sync`)." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:70 +msgid "This allows clients which support Sliding Sync to detect the Sliding Sync proxy's URL and make use of it." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po index cf6820ead..2dcb66a6e 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,120 +19,108 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-ssl-certificates.md:12 +#: ../../../docs/configuring-playbook-ssl-certificates.md:1 msgid "Adjusting SSL certificate retrieval (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:14 -msgid "By default, the playbook retrieves and automatically renews free SSL certificates from [Let's Encrypt](https://letsencrypt.org/) via [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) for the domains of the services it installs (e.g. `matrix.example.com` and others). Refer this guide if you want to modify settings about how it manages SSL certificates or have the Traefik server use yours." +#: ../../../docs/configuring-playbook-ssl-certificates.md:3 +msgid "By default, this playbook retrieves and auto-renews free SSL certificates from [Let's Encrypt](https://letsencrypt.org/) for the domains it needs (e.g. `matrix.example.com` and others)" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:16 -msgid "**Notes**:" +#: ../../../docs/configuring-playbook-ssl-certificates.md:5 +msgid "This guide is about using the integrated Traefik server and doesn't apply if you're using [your own webserver](configuring-playbook-own-webserver.md)." msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:17 -msgid "This guide is intended to be referred for configuring the integrated Traefik server with regard to SSL certificates retrieval. If you're using [your own webserver](configuring-playbook-own-webserver.md), consult its documentation about how to configure it." -msgstr "" - -#: ../../../docs/configuring-playbook-ssl-certificates.md:18 -msgid "Let's Encrypt ends the expiration notification email service on June 4, 2025 (see: [the official announcement](https://letsencrypt.org/2025/01/22/ending-expiration-emails/)), and it recommends using a third party service for those who want to receive expiration notifications. If you are looking for a self-hosting service, you may be interested in a monitoring tool such as [Update Kuma](https://github.com/louislam/uptime-kuma/)." -msgstr "" - -#: ../../../docs/configuring-playbook-ssl-certificates.md:20 -msgid "The [Mother-of-All-Self-Hosting (MASH)](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook can be used to install and manage an Uptime Kuma instance. See [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/uptime-kuma.md) for the instruction to install it with the playbook. If you are wondering how to use it for your Matrix server, refer to [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/setting-up-services-on-mdad-server.md) for the overview." +#: ../../../docs/configuring-playbook-ssl-certificates.md:7 +msgid "Using staging Let's Encrypt certificates instead of real ones" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:22 -msgid "Use staging Let's Encrypt certificates" +#: ../../../docs/configuring-playbook-ssl-certificates.md:9 +msgid "For testing purposes, you may wish to use staging certificates provide by Let's Encrypt." msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:24 -msgid "For testing purposes, you may wish to use staging certificates provided by Let's Encrypt to avoid hitting [its rate limits](https://letsencrypt.org/docs/rate-limits/)." +#: ../../../docs/configuring-playbook-ssl-certificates.md:11 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:26 -msgid "To use ones, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +#: ../../../docs/configuring-playbook-ssl-certificates.md:17 +msgid "Disabling SSL termination" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:32 -msgid "Disable SSL termination" +#: ../../../docs/configuring-playbook-ssl-certificates.md:19 +msgid "For testing or other purposes, you may wish to install services without SSL termination and have services exposed to `http://` instead of `https://`." msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:34 -msgid "For testing or other purposes, you may wish to install services without SSL termination and have services exposed to `http://` instead of `https://`." +#: ../../../docs/configuring-playbook-ssl-certificates.md:21 +msgid "Add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:36 -msgid "To do so, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-ssl-certificates.md:27 +msgid "Using self-signed SSL certificates" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:42 -msgid "Use self-signed SSL certificates" +#: ../../../docs/configuring-playbook-ssl-certificates.md:29 +msgid "If you'd like to use your own SSL certificates, instead of the default (SSL certificates obtained automatically via [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) from [Let's Encrypt](https://letsencrypt.org/)):" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:44 -msgid "To use self-signed certificates, generate them and follow the documentation below about using your own certificates." +#: ../../../docs/configuring-playbook-ssl-certificates.md:31 +msgid "generate your self-signed certificate files" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:46 -msgid "Use your own SSL certificates" +#: ../../../docs/configuring-playbook-ssl-certificates.md:32 +msgid "follow the [Using your own SSL certificates](#using-your-own-ssl-certificates) documentation below" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:48 -msgid "To use your own certificates, prepare them and follow the steps below:" +#: ../../../docs/configuring-playbook-ssl-certificates.md:34 +msgid "Using your own SSL certificates" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:50 -msgid "Disable [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) / [Let's Encrypt](https://letsencrypt.org/) support" +#: ../../../docs/configuring-playbook-ssl-certificates.md:36 +msgid "To use your own SSL certificates with Traefik, you need to:" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:51 -msgid "Put a custom Traefik configuration file on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually" +#: ../../../docs/configuring-playbook-ssl-certificates.md:38 +msgid "disable [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) / [Let's Encrypt](https://letsencrypt.org/) support" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:52 -msgid "Register your custom configuration file with Traefik, by adding an extra provider of type [file](https://doc.traefik.io/traefik/providers/file/)" +#: ../../../docs/configuring-playbook-ssl-certificates.md:39 +msgid "put a custom Traefik configuration file on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:53 -msgid "Put the SSL files on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually" +#: ../../../docs/configuring-playbook-ssl-certificates.md:40 +msgid "register your custom configuration file with Traefik, by adding an extra provider of type [file](https://doc.traefik.io/traefik/providers/file/)" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:55 -msgid "For those steps, you can add the following configuration to your `vars.yml` file (adapt to your needs). If you will put the custom configuration files manually, make sure to remove the `aux_file_definitions` variable." +#: ../../../docs/configuring-playbook-ssl-certificates.md:41 +msgid "put the SSL files on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:103 -msgid "Use a DNS-01 ACME challenge type, instead of HTTP-01" +#: ../../../docs/configuring-playbook-ssl-certificates.md:89 +msgid "Using a DNS-01 ACME challenge type, instead of HTTP-01" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:105 -msgid "You can configure Traefik to use the [DNS-01 challenge type](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) for Let's Encrypt. This is less commonly used than the default [HTTP-01 challenge type](https://letsencrypt.org/docs/challenge-types/#http-01-challenge), but can be helpful to:" +#: ../../../docs/configuring-playbook-ssl-certificates.md:91 +msgid "You can configure Traefik to use the [DNS-01 challenge type](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) for Let's Encrypt. This is less commonly used than the default [HTTP-01 challenge type](https://letsencrypt.org/docs/challenge-types/#http-01-challenge), but it can be helpful to:" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:107 +#: ../../../docs/configuring-playbook-ssl-certificates.md:93 msgid "hide your public IP from Let's Encrypt logs" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:108 +#: ../../../docs/configuring-playbook-ssl-certificates.md:94 msgid "allow you to obtain SSL certificates for servers which are not accessible (via HTTP) from the public internet (and for which the HTTP-01 challenge would fail)" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:110 -msgid "Example: Cloudflare" -msgstr "" - -#: ../../../docs/configuring-playbook-ssl-certificates.md:112 -msgid "Here is an example for configurations on the `vars.yml` file for Cloudflare. Please adjust it as necessary before applying it." +#: ../../../docs/configuring-playbook-ssl-certificates.md:96 +msgid "This is an example for how to edit the `vars.yml` file if you're using Cloudflare:" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:127 +#: ../../../docs/configuring-playbook-ssl-certificates.md:111 msgid "Make sure to change the value of \"provider\" to your particular DNS solution, and provide the appropriate environment variables. The full list of supported providers is available [here](https://doc.traefik.io/traefik/https/acme/#providers)." msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:129 +#: ../../../docs/configuring-playbook-ssl-certificates.md:113 msgid "This example assumes you're using Cloudflare to manage your DNS zone. Note that it requires the use of two tokens: one for reading all zones (`CF_ZONE_API_TOKEN`) and another that must be able to edit the particular domain you're using (`CF_DNS_API_TOKEN`). For security, it's recommended that you create two fine-grained tokens for this purpose, but you might choose to use the same token for both." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sygnal.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sygnal.po index 1dfba34a3..7b1318358 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sygnal.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sygnal.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,140 +19,132 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-sygnal.md:8 +#: ../../../docs/configuring-playbook-sygnal.md:1 msgid "Setting up the Sygnal push gateway (optional)" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:10 +#: ../../../docs/configuring-playbook-sygnal.md:3 msgid "The playbook can install and configure the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:12 +#: ../../../docs/configuring-playbook-sygnal.md:5 msgid "See the project's [documentation](https://github.com/matrix-org/sygnal/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:14 +#: ../../../docs/configuring-playbook-sygnal.md:7 msgid "**Note**: most people don't need to install their own gateway. As Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) documentation says:" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:16 +#: ../../../docs/configuring-playbook-sygnal.md:9 msgid "It is not feasible to allow end-users to configure their own Sygnal instance, because the Sygnal instance needs the appropriate FCM or APNs secrets that belong to the application." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:18 +#: ../../../docs/configuring-playbook-sygnal.md:11 msgid "This optional playbook component is only useful to people who develop/build their own Matrix client applications themselves." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:20 +#: ../../../docs/configuring-playbook-sygnal.md:13 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:22 +#: ../../../docs/configuring-playbook-sygnal.md:15 msgid "By default, this playbook installs Sygnal on the `sygnal.` subdomain (`sygnal.example.com`) and requires you to create a CNAME record for `sygnal`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:24 +#: ../../../docs/configuring-playbook-sygnal.md:17 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:26 +#: ../../../docs/configuring-playbook-sygnal.md:19 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:28 +#: ../../../docs/configuring-playbook-sygnal.md:21 msgid "To enable Sygnal, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:56 +#: ../../../docs/configuring-playbook-sygnal.md:49 msgid "Configuring [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/) is easier, as it only requires that you provide some config values." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:58 +#: ../../../docs/configuring-playbook-sygnal.md:51 msgid "To configure [APNS](https://developer.apple.com/notifications/) (Apple Push Notification Service), you'd need to provide one or more certificate files. To do that, the above example configuration:" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:60 +#: ../../../docs/configuring-playbook-sygnal.md:53 msgid "makes use of the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) (and its `aux_file_definitions` variable) to make the playbook install files into `/matrix/sygnal/data` (the `matrix_sygnal_data_path` variable). See [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml) of the `aux` role for usage examples. It also makes sure the files are owned by `matrix:matrix`, so that Sygnal can read them. Of course, you can also install these files manually yourself, if you'd rather not use `aux`." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:62 +#: ../../../docs/configuring-playbook-sygnal.md:55 msgid "references these files in the Sygnal configuration (`matrix_sygnal_apps`) using a path like `/data/…` (the `/matrix/sygnal/data` directory on the host system is mounted into the `/data` directory inside the container)" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:64 +#: ../../../docs/configuring-playbook-sygnal.md:57 msgid "Adjusting the Sygnal URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:66 +#: ../../../docs/configuring-playbook-sygnal.md:59 msgid "By tweaking the `matrix_sygnal_hostname` and `matrix_sygnal_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:68 +#: ../../../docs/configuring-playbook-sygnal.md:61 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:79 +#: ../../../docs/configuring-playbook-sygnal.md:72 msgid "After changing the domain, **you may need to adjust your DNS** records to point the Sygnal domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:81 +#: ../../../docs/configuring-playbook-sygnal.md:74 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:83 +#: ../../../docs/configuring-playbook-sygnal.md:76 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:85 +#: ../../../docs/configuring-playbook-sygnal.md:78 msgid "There are some additional things you may wish to configure about the component." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:87 +#: ../../../docs/configuring-playbook-sygnal.md:80 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:89 +#: ../../../docs/configuring-playbook-sygnal.md:82 msgid "`roles/custom/matrix-sygnal/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:90 +#: ../../../docs/configuring-playbook-sygnal.md:83 msgid "`roles/custom/matrix-sygnal/templates/config.yaml.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_sygnal_configuration_extension_yaml` variable" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:92 +#: ../../../docs/configuring-playbook-sygnal.md:85 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:94 +#: ../../../docs/configuring-playbook-sygnal.md:87 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:101 +#: ../../../docs/configuring-playbook-sygnal.md:94 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:103 +#: ../../../docs/configuring-playbook-sygnal.md:96 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:105 +#: ../../../docs/configuring-playbook-sygnal.md:98 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:107 +#: ../../../docs/configuring-playbook-sygnal.md:100 msgid "To make use of your Sygnal installation, you'd need to build your own Matrix client application, which uses the same API keys (for [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/)) and certificates (for [APNS](https://developer.apple.com/notifications/)) and is to your Sygnal URL endpoint (e.g. `https://sygnal.example.com`)." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:109 +#: ../../../docs/configuring-playbook-sygnal.md:102 msgid "Refer to Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) document." msgstr "" - -#: ../../../docs/configuring-playbook-sygnal.md:111 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-sygnal.md:113 -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-sygnal`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po new file mode 100644 index 000000000..df6fad1c4 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po @@ -0,0 +1,126 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +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" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: bg\n" +"Language-Team: bg \n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.16.0\n" + +#: ../../../docs/configuring-playbook-synapse-admin.md:1 +msgid "Setting up Synapse Admin (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:3 +msgid "The playbook can install and configure [etkecc/synapse-admin](https://github.com/etkecc/synapse-admin) (a [feature-rich](https://github.com/etkecc/synapse-admin#fork-differences) fork of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin), community room: [#synapse-admin:etke.cc](https://matrix.to/#/#synapse-admin:etke.cc)) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:5 +msgid "synapse-admin is a web UI tool you can use to **administrate users, rooms, media, etc. on your Matrix server**. It's designed to work with the Synapse homeserver implementation and WON'T work with Dendrite because [Dendrite Admin API](https://element-hq.github.io/dendrite/administration/adminapi) differs from [Synapse Admin API](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:7 +msgid "💡 **Note**: the latest version of synapse-admin is hosted by [etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). If you only need this service occasionally and trust giving your admin credentials to a 3rd party Single Page Application, you can consider using it from there and avoiding the (small) overhead of self-hosting." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:9 +msgid "Adjusting DNS records (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:11 +msgid "By default, this playbook installs Synapse Admin on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:13 +msgid "If you wish to adjust it, see the section [below](#adjusting-the-synapse-admin-url-optional) for details about DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:17 +msgid "To enable Synapse Admin, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:23 +msgid "**Note**: Synapse Admin requires Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to function. Access to them is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, for additional security, we normally leave them unexposed, following [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). Because Synapse Admin needs these APIs to function, when installing Synapse Admin, the playbook **automatically** exposes the Synapse Admin API publicly for you. Depending on the homeserver implementation you're using (Synapse, Dendrite), this is equivalent to:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:25 +msgid "for [Synapse](./configuring-playbook-synapse.md) (our default homeserver implementation): `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:26 +msgid "for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:28 +msgid "By default, synapse-admin installation will be [restricted to only work with one homeserver](https://github.com/etkecc/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) — the one managed by the playbook. To adjust these restrictions, tweak the `matrix_synapse_admin_config_restrictBaseUrl` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:30 +msgid "[!WARNING] If you're using [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS) for authentication, you will be able to [log into synapse-admin with an access token](https://github.com/etkecc/synapse-admin/pull/58), but certain synapse-admin features (especially those around user management) will be limited or not work at all." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:33 +msgid "Adjusting the Synapse Admin URL (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:35 +msgid "By tweaking the `matrix_synapse_admin_hostname` and `matrix_synapse_admin_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:37 +msgid "Example additional configuration for your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:45 +msgid "If you've changed the default hostname, you may need to create a CNAME record for the Synapse Admin domain (`admin.example.com`), which targets `matrix.example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:47 +msgid "When setting, replace `example.com` with your own." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:49 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:51 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:58 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:60 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:62 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:64 +msgid "After installation, Synapse Admin will be accessible at: `https://matrix.example.com/synapse-admin/`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:66 +msgid "To use Synapse Admin, you need to have [registered at least one administrator account](registering-users.md) on your server." +msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po index 524362091..4267425c2 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,20 +19,56 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:18 -msgid "Setting up Synapse Auto Invite Accept (optional, removed)" +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:1 +msgid "Setting up Synapse Auto Invite Accept (optional)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:20 -msgid "🪦 The playbook used to be able to install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite), but no longer includes this component, as the same functionality [has been integrated](https://github.com/element-hq/synapse/pull/17147) to Synapse since [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0)." +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:3 +msgid "The playbook can install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) for you." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:22 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:5 +msgid "In short, it automatically accepts room invites. You can specify that only 1:1 room invites are auto-accepted. Defaults to false if not specified." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:7 +msgid "See the project's [documentation](https://github.com/matrix-org/synapse-auto-accept-invite/blob/main/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:9 +msgid "**Note**: Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0), the same feature [has been merged](https://github.com/element-hq/synapse/pull/17147) into Synapse (see the [Native alternative](#native-alternative) section below). You'd better use the native feature, instead of the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) 3rd party module." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:13 +msgid "If you decide that you'd like to let this playbook install the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite module for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:21 +msgid "Synapse worker deployments" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:23 +msgid "In a [workerized Synapse deployment](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/c9a842147e09647c355799ca024d65a5de66b099/docs/configuring-playbook-synapse.md#load-balancing-with-workers) it is possible to run this module on a worker to reduce the load on the main process (Default is `null`). For example, add this to your configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:29 +msgid "There might be an [issue with federation](https://github.com/matrix-org/synapse-auto-accept-invite/issues/18)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:31 msgid "Native alternative" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:24 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:33 +msgid "Since Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0), the functionality provided by the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) 3rd party module [has been made](https://github.com/element-hq/synapse/pull/17147) part of Synapse." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:35 msgid "Here's example configuration for using the **native** Synapse feature:" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po index 2250a17be..a186c7e20 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,104 +19,68 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:9 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:1 msgid "Setting up synapse-auto-compressor (optional)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:11 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:3 msgid "The playbook can install and configure [synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) for you." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:13 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:5 msgid "It's a CLI tool that automatically compresses Synapse's `state_groups` database table in the background." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:15 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:7 msgid "See the project's [documentation](https://github.com/matrix-org/rust-synapse-compress-state/blob/master/README.md#automated-tool-synapse_auto_compressor) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:17 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:9 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:19 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:11 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:25 -msgid "Edit the schedule (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:27 -msgid "By default the task will around 0 a.m. every day based on the `matrix_synapse_auto_compressor_schedule` variable with a randomized delay of 6 hours (controlled by the `matrix_synapse_auto_compressor_schedule_randomized_delay_sec` variable). It is defined in the format of systemd timer calendar." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:29 -msgid "To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs):" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:38 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:40 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:42 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:44 -msgid "`roles/custom/matrix-synapse-auto-compressor/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:46 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:17 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:48 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:19 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:55 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:26 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:57 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:28 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:59 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:30 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:61 -msgid "After installation, `synapse_auto_compressor` will run automatically every day at `00:00:00` (as defined in `matrix_synapse_auto_compressor_schedule` by default)." +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:32 +msgid "After installation, `synapse_auto_compressor` will run automatically every day at `00:00:00` (as defined in `matrix_synapse_auto_compressor_calendar` by default)." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:63 -msgid "Manually start the task" +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:34 +msgid "Manually execute compression" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:65 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:36 msgid "Sometimes it can be helpful to execute compression as you'd like, avoiding to wait until 00:00, like when you test your configuration." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:67 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:38 msgid "If you want to execute it immediately, log in to the server with SSH and run `systemctl start matrix-synapse-auto-compressor`." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:69 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:40 msgid "This will not return until the compression is done, so it can possibly take a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable." msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:71 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:73 -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-auto-compressor`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po index e440d3b3e..956b08b1c 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,292 +19,260 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:10 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:1 msgid "Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider (optional)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:12 -msgid "The playbook can install and configure the [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) for you." +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:3 +msgid "If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service), you can use the [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) media provider module for Synapse." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:14 -msgid "It is a media provider module for Synapse to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service) object storage." +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:5 +msgid "An alternative (which has worse performance) is to use [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:16 -msgid "See the project's [documentation](https://github.com/matrix-org/synapse-s3-storage-provider/blob/main/README.md) to learn what it does and why it might be useful to you." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:18 -msgid "**Note**: alternatively you can use [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md) despite worse performance." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:20 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:7 msgid "How it works?" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:22 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:9 msgid "Summarized writings here are inspired by [this article](https://quentin.dufour.io/blog/2021-09-14/matrix-synapse-s3-storage/)." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:24 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:11 msgid "The way media storage providers in Synapse work has some caveats:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:26 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:13 msgid "Synapse still continues to use locally-stored files (for creating thumbnails, serving files, etc)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:27 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:14 msgid "the media storage provider is just an extra storage mechanism (in addition to the local filesystem)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:28 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:15 msgid "all files are stored locally at first, and then copied to the media storage provider (either synchronously or asynchronously)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:29 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:16 msgid "if a file is not available on the local filesystem, it's pulled from a media storage provider" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:31 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:18 msgid "You may be thinking **if all files are stored locally as well, what's the point**?" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:33 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:20 msgid "You can run some scripts to delete the local files once in a while (which we do automatically by default — see [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem)), thus freeing up local disk space. If these files are needed in the future (for serving them to users, etc.), Synapse will pull them from the media storage provider on demand." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:35 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:22 msgid "While you will need some local disk space around, it's only to accommodate usage, etc., and won't grow as large as your S3 store." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:37 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:24 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:39 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:26 msgid "After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:61 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:48 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:63 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:50 msgid "There are some additional things you may wish to configure about the server." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:65 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:52 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:67 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:54 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-s3-storage-provider.md:69 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:71 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:78 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:80 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:82 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:56 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:84 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:58 msgid "If you have existing files in Synapse's media repository (`/matrix/synapse/storage/media-store/…`):" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:86 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:60 msgid "new files will start being stored both locally and on the S3 store" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:87 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:61 msgid "the existing files will remain on the local filesystem only until [migrating them to the S3 store](#migrating-your-existing-media-files-to-the-s3-store)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:88 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:62 msgid "at some point (and periodically in the future), you can delete local files which have been uploaded to the S3 store already" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:90 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:64 msgid "Regardless of whether you need to [Migrate your existing files to the S3 store](#migrating-your-existing-media-files-to-the-s3-store) or not, make sure you've familiarized yourself with [How it works?](#how-it-works) above and [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem) below." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:92 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:66 msgid "Migrating your existing media files to the S3 store" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:94 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:68 msgid "Migrating your existing data can happen in multiple ways:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:96 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:70 msgid "[using the `s3_media_upload` script from `synapse-s3-storage-provider`](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (very slow when dealing with lots of data)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:97 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:71 msgid "[using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload) (quicker when dealing with lots of data)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:99 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:73 msgid "💡 **Note**: instead of using `s3_media_upload` directly, which is very slow and painful for an initial data migration, we recommend [using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload)." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:101 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:75 msgid "Using the `s3_media_upload` script from `synapse-s3-storage-provider`" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:103 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:77 msgid "To copy your existing files, SSH into the server and run `/matrix/synapse/ext/s3-storage-provider/bin/shell`." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:105 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:79 msgid "This launches a Synapse container, which has access to the local media store, Postgres database, S3 store and has some convenient environment variables configured for you to use (`MEDIA_PATH`, `BUCKET`, `ENDPOINT`, `UPDATE_DB_DAYS`, etc)." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:107 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:81 msgid "Then use the following commands (`$` values come from environment variables — they're **not placeholders** that you need to substitute):" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:109 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:83 msgid "`s3_media_upload update-db $UPDATE_DB_DURATION` — create a local SQLite database (`cache.db`) with a list of media repository files (from the `synapse` Postgres database) eligible for operating on" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:110 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:84 msgid "`$UPDATE_DB_DURATION` is influenced by the `matrix_synapse_ext_synapse_s3_storage_provider_update_db_day_count` variable (defaults to `0`)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:111 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:85 msgid "`$UPDATE_DB_DURATION` defaults to `0d` (0 days), which means **include files which haven't been accessed for more than 0 days** (that is, **all files will be included**)." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:112 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:86 msgid "`s3_media_upload check-deleted $MEDIA_PATH` — check whether files in the local cache still exist in the local media repository directory" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:113 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:87 msgid "`s3_media_upload upload $MEDIA_PATH $BUCKET --delete --storage-class $STORAGE_CLASS --endpoint-url $ENDPOINT` — uploads locally-stored files to S3 and deletes them from the local media repository directory" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:115 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:89 msgid "The `s3_media_upload upload` command may take a lot of time to complete." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:117 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:91 msgid "Instead of running the above commands manually in the shell, you can also run the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script which will run the same commands automatically. We demonstrate how to do it manually, because:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:119 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:93 msgid "it's what the upstream project demonstrates and it teaches you how to use the `s3_media_upload` tool" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:120 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:94 msgid "allows you to check and verify the output of each command, to catch mistakes" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:121 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:95 msgid "includes progress bars and detailed output for each command" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:122 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:96 msgid "allows you to easily interrupt slow-running commands, etc. (the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container without interactive TTY support, so `Ctrl+C` may not work and you and require killing via `docker kill …`)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:124 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:98 msgid "Using another tool in combination with `s3_media_upload`" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:126 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:100 msgid "To migrate your existing local data to S3, we recommend to:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:128 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:102 msgid "**first** use another tool ([`aws s3`](#copying-data-to-amazon-s3) or [`b2 sync`](#copying-data-to-backblaze-b2), etc.) to copy the local files to the S3 bucket" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:130 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:104 msgid "**only then** [use the `s3_media_upload` tool to finish the migration](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (this checks to ensure all files are uploaded and then deletes the local files)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:132 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:106 msgid "Copying data to Amazon S3" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:134 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:108 msgid "To copy to AWS S3, start a container on the Matrix server like this:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:146 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:120 msgid "Copying data to an S3 alternative using the aws-s3 tool" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:148 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:122 msgid "To copy to a provider other than AWS S3 (e.g. Storj, Wasabi, Digital Ocean Spaces, etc.), you can use the command for [Copying data to Amazon S3](#copying-data-to-amazon-s3) with an added `--endpoint-url=$ENDPOINT` argument." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:150 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:124 msgid "Add this argument to the command **as-is** (`$ENDPOINT` is an environment variable corresponding to `matrix_synapse_ext_synapse_s3_storage_provider_config_endpoint_url`, so you don't need to touch it). Make sure to add the argument **before** the final quote (`'`) of the command." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:152 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:126 msgid "Copying data to Backblaze B2" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:154 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:128 msgid "You can copy files to Backblaze B2 either by following the [Copying data to an S3 alternative using the aws-s3 tool](#copying-data-to-an-s3-alternative-using-the-aws-s3-tool) or by using the B2-specific [b2 command-line tool](https://www.backblaze.com/b2/docs/quick_command_line.html) as described below." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:156 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:130 msgid "To copy the data using the `b2` tool, start a container on the Matrix server like this:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:170 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:144 msgid "Periodically cleaning up the local filesystem" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:172 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:146 msgid "As described in [How it works?](#how-it-works) above, when new media is uploaded to the Synapse homeserver, it's first stored locally and then also stored on the remote S3 storage." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:174 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:148 msgid "By default, we periodically ensure that all local files are uploaded to S3 and are then removed from the local filesystem. This is done automatically using:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:176 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:150 msgid "the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:177 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:151 msgid "… invoked via the `matrix-synapse-s3-storage-provider-migrate.service` service" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:178 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:152 msgid "… triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` timer, every day at 05:00" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:180 -msgid "The same `migrate` script also prunes empty directories in the local media repository (`remote_content` and `remote_thumbnail`) after upload/delete operations." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:182 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:154 msgid "So… you don't need to perform any maintenance yourself." msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:184 -msgid "The schedule is defined in the format of systemd timer calendar. To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs):" -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po index fb7953500..d4be5dc5e 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po @@ -10,7 +10,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: 2024-12-20 09:53+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,44 +19,28 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:8 +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:1 msgid "Setting up Synapse Simple Antispam (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:10 +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:3 msgid "The playbook can install and configure [synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) for you." msgstr "" -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:12 -msgid "It lets you fight invite-spam by automatically blocking invitations from a list of servers specified by you (blacklisting)." +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:5 +msgid "It lets you fight invite-spam by automatically blocking invitiations from a list of servers specified by you (blacklisting)." msgstr "" -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:14 +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:7 msgid "See the project's [documentation](https://github.com/t2bot/synapse-simple-antispam/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:16 +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:9 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:18 +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:11 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" - -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:28 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:30 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:37 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:39 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po index 3a54c3ff8..892191376 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,128 +19,92 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:9 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:1 msgid "Enabling synapse-usage-exporter for Synapse usage statistics (optional)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:11 -msgid "The playbook can install and configure [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) for you." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:13 -msgid "It allows you to export the usage statistics of a Synapse homeserver to this container service and for the collected metrics to later be scraped by Prometheus." +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:3 +msgid "[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) allows you to export the usage statistics of a Synapse homeserver to this container service and for the collected metrics to later be scraped by Prometheus." msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:15 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:5 msgid "Synapse does not include usage statistics in its Prometheus metrics. They can be reported to an HTTP `PUT` endpoint 5 minutes after startup and from then on at a fixed interval of once every three hours. This role integrates a simple [Flask](https://flask.palletsprojects.com) project that offers an HTTP `PUT` endpoint and holds the most recent received record available to be scraped by Prometheus." msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:17 -msgid "See the project's [documentation](https://github.com/loelkes/synapse-usage-exporter/blob/main/README.md) to learn what it does and why it might be useful to you." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:19 -msgid "What does it do?" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:21 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:7 msgid "Enabling this service will automatically:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:23 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:9 msgid "install the synapse-usage-exporter service" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:24 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:10 msgid "re-configure Synapse to push (via HTTP `PUT`) usage statistics information to synapse-usage-exporter" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:25 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:11 msgid "re-configure [Prometheus](./configuring-playbook-prometheus-grafana.md) (if Prometheus is enabled), to periodically scrape metrics from synapse-usage-exporter" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:26 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:12 msgid "add a new [Grafana](./configuring-playbook-prometheus-grafana.md) dashboard (if Grafana is enabled) containing Synapse usage statistics" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:28 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:14 msgid "Adjusting DNS records (optional)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:30 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:16 msgid "By default, this playbook installs synapse-usage-exporter on the `matrix.` subdomain, at the `/report-usage-stats/push` path (https://matrix.example.com/report-usage-stats/push). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:32 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:18 msgid "If you wish to adjust it, see the section [below](#adjusting-the-synapse-usage-exporter-url-optional) for details about DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:34 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:20 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:36 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:22 msgid "To enable synapse-usage-exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:48 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:34 msgid "Adjusting the synapse-usage-exporter URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:50 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:36 msgid "By tweaking the `matrix_synapse_usage_exporter_hostname` and `matrix_synapse_usage_exporter_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:52 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:38 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:61 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:47 msgid "If you've changed the default hostname, you may need to create a CNAME record for the synapse-usage-exporter domain (`sue.example.com`), which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:63 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:49 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:65 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:67 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:69 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:71 -msgid "`roles/custom/matrix-synapse-usage-exporter/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:73 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:51 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:75 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:53 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:82 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:60 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:84 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:62 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:86 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:88 -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-usage-exporter`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-traefik.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-traefik.po index 8a0a30844..bbbe447eb 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-traefik.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-traefik.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,181 +19,121 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-traefik.md:10 +#: ../../../docs/configuring-playbook-traefik.md:1 msgid "Configuring the Traefik reverse-proxy (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:12 -msgid "By default, this playbook installs and manages a [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered by the [ansible-role-traefik](https://github.com/mother-of-all-self-hosting/ansible-role-traefik) Ansible role for you. If that's okay, you can skip this document." +#: ../../../docs/configuring-playbook-traefik.md:3 +msgid "By default, this playbook installs and manages a [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered by the [ansible-role-traefik](https://github.com/mother-of-all-self-hosting/ansible-role-traefik) Ansible role." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:14 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:16 +#: ../../../docs/configuring-playbook-traefik.md:5 msgid "This Ansible role support various configuration options. Feel free to consult its `default/main.yml` variables file." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:18 -msgid "Disable access logs" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:20 -msgid "To disable access logging, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +#: ../../../docs/configuring-playbook-traefik.md:7 +msgid "Adjusting SSL certificate retrieval" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:26 -msgid "Enable Traefik Dashboard" +#: ../../../docs/configuring-playbook-traefik.md:9 +msgid "See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:28 -msgid "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:" +#: ../../../docs/configuring-playbook-traefik.md:11 +msgid "Increase logging verbosity" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:37 -msgid "Generate the `traefik_dashboard_basicauth_htpasswd` value on your local machine with a command like `htpasswd -nb YOUR_USERNAME_HERE YOUR_PASSWORD_HERE`." +#: ../../../docs/configuring-playbook-traefik.md:17 +msgid "Disable access logs" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:39 -msgid "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." +#: ../../../docs/configuring-playbook-traefik.md:19 +msgid "This will disable access logging." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:41 -msgid "[!WARNING] Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts." +#: ../../../docs/configuring-playbook-traefik.md:25 +msgid "Enable Traefik Dashboard" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:44 -msgid "Extending the configuration" +#: ../../../docs/configuring-playbook-traefik.md:27 +msgid "This will enable a Traefik [Dashboard](https://doc.traefik.io/traefik/operations/dashboard/) UI at `https://matrix.example.com/dashboard/` (note the trailing `/`)." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:46 -msgid "There are some additional things you may wish to configure about the component." +#: ../../../docs/configuring-playbook-traefik.md:37 +msgid "[!WARNING] Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:48 -msgid "Take a look at:" +#: ../../../docs/configuring-playbook-traefik.md:40 +msgid "Additional configuration" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:50 -msgid "[Traefik role](https://github.com/mother-of-all-self-hosting/ansible-role-traefik)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-traefik/blob/main/defaults/main.yml) for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `traefik_configuration_extension_yaml` variable" +#: ../../../docs/configuring-playbook-traefik.md:42 +msgid "Use the `traefik_configuration_extension_yaml` variable provided by the Traefik Ansible role to override or inject additional settings, even when no dedicated variable exists." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:52 -msgid "For example, to enable and secure the Dashboard, you can add the following configuration to your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:54 -msgid "**Note**: this is a contrived example as you can enable and secure the Dashboard using the dedicated variables. See above for details." -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:72 msgid "Reverse-proxying another service behind Traefik" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:74 +#: ../../../docs/configuring-playbook-traefik.md:54 msgid "The preferred way to reverse-proxy additional services behind Traefik would be to start the service as another container, configure the container with the corresponding Traefik [container labels](https://docs.docker.com/config/labels-custom-metadata/) (see [Traefik & Docker](https://doc.traefik.io/traefik/routing/providers/docker/)), and connect the service to the `traefik` network. Some services are also already available via the compatible [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook), but take a look at the minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md)." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:76 +#: ../../../docs/configuring-playbook-traefik.md:56 msgid "However, if your service does not run on a container or runs on another machine, the following configuration might be what you are looking for." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:78 +#: ../../../docs/configuring-playbook-traefik.md:58 msgid "Reverse-proxying a remote HTTP/HTTPS service behind Traefik" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:80 +#: ../../../docs/configuring-playbook-traefik.md:60 msgid "If you want to host another webserver would be reachable via `my-fancy-website.example.net` from the internet and via `https://:` from inside your network, you can make the playbook's integrated Traefik instance reverse-proxy the traffic to the correct host." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:82 +#: ../../../docs/configuring-playbook-traefik.md:62 msgid "Prerequisites: DNS and routing for the domain `my-fancy-website.example.net` need to be set up correctly. In this case, you'd be pointing the domain name to your Matrix server — `my-fancy-website.example.net` would be a CNAME going to `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:84 +#: ../../../docs/configuring-playbook-traefik.md:64 msgid "First, we have to adjust the static configuration of Traefik, so that we can add additional configuration files:" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:98 +#: ../../../docs/configuring-playbook-traefik.md:78 msgid "If you are using a self-signed certificate on your webserver, you can tell Traefik to trust your own backend servers by adding more configuration to the static configuration file. If you do so, bear in mind the security implications of disabling the certificate validity checks towards your back end." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:112 +#: ../../../docs/configuring-playbook-traefik.md:92 msgid "Next, you have to add a new dynamic configuration file for Traefik that contains the actual information of the server using the `aux_file_definitions` variable. In this example, we will terminate SSL at the Traefik instance and connect to the other server via HTTPS. Traefik will now take care of managing the certificates." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:131 -#: ../../../docs/configuring-playbook-traefik.md:154 +#: ../../../docs/configuring-playbook-traefik.md:111 +#: ../../../docs/configuring-playbook-traefik.md:134 msgid "Changing the `url` to one with an `http://` prefix would allow to connect to the server via HTTP." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:133 +#: ../../../docs/configuring-playbook-traefik.md:113 msgid "Reverse-proxying another service behind Traefik without terminating SSL" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:135 +#: ../../../docs/configuring-playbook-traefik.md:115 msgid "If you do not want to terminate SSL at the Traefik instance (for example, because you're already terminating SSL at other webserver), you need to adjust the static configuration in the same way as in the previous chapter in order to be able to add our own dynamic configuration files. Afterwards, you can add the following configuration to your `vars.yml` configuration file:" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:156 +#: ../../../docs/configuring-playbook-traefik.md:136 msgid "With these changes, all TCP traffic will be reverse-proxied to the target system." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:158 +#: ../../../docs/configuring-playbook-traefik.md:138 msgid "[!WARNING] This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:161 +#: ../../../docs/configuring-playbook-traefik.md:141 msgid "Traefik behind a `proxy_protocol` reverse-proxy" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:163 -msgid "If you run a reverse-proxy which speaks `proxy_protocol`, add the following configuration to your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:182 -msgid "Other configurations" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:184 -msgid "Adjusting SSL certificate retrieval" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:186 -msgid "See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page." -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:188 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:190 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.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-traefik.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. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:201 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:203 -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-traefik`." -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:205 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:207 -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:" +#: ../../../docs/configuring-playbook-traefik.md:143 +msgid "If you run a reverse-proxy which speaks `proxy_protocol`, add the following to your configuration file:" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-turn.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-turn.po index 897d6ab10..fd8c3bac6 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-turn.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-turn.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,220 +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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-turn.md:14 +#: ../../../docs/configuring-playbook-turn.md:1 msgid "Configuring a TURN server (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:16 -msgid "By default, the [coturn](https://github.com/coturn/coturn) TURN server component is enabled automatically only when [Jitsi](configuring-playbook-jitsi.md) is enabled. If you're not using Jitsi, coturn is not enabled by default." +#: ../../../docs/configuring-playbook-turn.md:3 +msgid "By default, this playbook installs and configures the [coturn](https://github.com/coturn/coturn) as a TURN server, through which clients can make audio/video calls even from [NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed networks. It also configures the Synapse chat server by default, so that it points to the coturn TURN server installed by the playbook. If that's okay, you can skip this document." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:18 -msgid "If you explicitly need coturn while not using Jitsi, enable it with:" +#: ../../../docs/configuring-playbook-turn.md:5 +msgid "If you'd like to stop the playbook installing the server, see the section [below](#disabling-coturn) to check the configuration for disabling it." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:24 -msgid "and configure its IP-related settings in the section below." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:26 -msgid "If you'd like coturn to stay disabled even when Jitsi is enabled, or if you prefer to use an external TURN provider, see [disabling coturn](#disabling-coturn) section below." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:28 -msgid "When Coturn is not enabled, homeservers (like Synapse) would not point to TURN servers and *legacy* audio/video call functionality may fail. If you're using [Matrix RTC](configuring-playbook-matrix-rtc.md) (for [Element Call](configuring-playbook-element-call.md)), you likely don't have a need to enable coturn." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:30 -msgid "Adjusting firewall rules" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:32 -msgid "To ensure Coturn functions correctly, the following firewall rules and port forwarding settings are required when coturn is enabled:" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:34 -msgid "`3478/tcp`: STUN/TURN over TCP" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:35 -msgid "`3478/udp`: STUN/TURN over UDP" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:36 -msgid "`5349/tcp`: TURN over TCP" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:37 -msgid "`5349/udp`: TURN over UDP" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:38 -msgid "`49152-49172/udp`: TURN/UDP relay range" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:40 -msgid "If LiveKit's embedded TURN is enabled at the same time (for MatrixRTC/Element Call), keep the Coturn relay range distinct from LiveKit's relay range (`livekit_server_config_turn_relay_range_start`/`livekit_server_config_turn_relay_range_end`)." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:42 -msgid "💡 Docker configures the server's internal firewall for you. In most cases, you don't need to do anything special on the host itself." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:44 +#: ../../../docs/configuring-playbook-turn.md:7 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:46 +#: ../../../docs/configuring-playbook-turn.md:9 msgid "Define public IP manually (optional)" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:48 -msgid "If you enable coturn (either via Jitsi or manually), we recommend that you configure the public IP addresses of your server in the `vars.yml` file:" +#: ../../../docs/configuring-playbook-turn.md:11 +msgid "In the `hosts` file we explicitly ask for your server's external IP address when defining `ansible_host`, because the same value is used for configuring coturn." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:55 -msgid "If you'd like to rely on external IP address auto-detection (not recommended unless you need it), avoid configuring this variable. The playbook will automatically contact an [echoip](https://github.com/mpolden/echoip)-compatible service (`https://ifconfig.co/json` by default) to determine your server's IP address. This API endpoint is configurable via the `coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable." +#: ../../../docs/configuring-playbook-turn.md:13 +msgid "If you'd rather use a local IP for `ansible_host`, add the following configuration to your `vars.yml` file. Make sure to replace `YOUR_PUBLIC_IP` with the pubic IP used by the server." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:57 -msgid "[!NOTE] You can self-host the echoip service by using the [Mother-of-All-Self-Hosting (MASH)](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook. See [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/echoip.md) for the instruction to install it with the playbook. If you are wondering how to use it for your Matrix server, refer to [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/setting-up-services-on-mdad-server.md) for the overview." +#: ../../../docs/configuring-playbook-turn.md:19 +msgid "If you'd like to rely on external IP address auto-detection (not recommended unless you need it), set an empty value to the variable. The playbook will automatically contact an [EchoIP](https://github.com/mpolden/echoip)-compatible service (`https://ifconfig.co/json` by default) to determine your server's IP address. This API endpoint is configurable via the `matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:60 +#: ../../../docs/configuring-playbook-turn.md:21 +msgid "If your server has multiple external IP addresses, the coturn role offers a different variable for specifying them:" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:28 msgid "Change the authentication mechanism (optional)" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:62 +#: ../../../docs/configuring-playbook-turn.md:30 msgid "The playbook uses the [`auth-secret` authentication method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L186-L199) by default, but you may switch to the [`lt-cred-mech` method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L178) which [some report](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3191) to be working better." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:64 +#: ../../../docs/configuring-playbook-turn.md:32 msgid "To do so, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:70 +#: ../../../docs/configuring-playbook-turn.md:38 msgid "Regardless of the selected authentication method, the playbook generates secrets automatically and passes them to the homeserver and coturn." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:72 +#: ../../../docs/configuring-playbook-turn.md:40 msgid "If [Jitsi](configuring-playbook-jitsi.md) is installed, note that switching to `lt-cred-mech` will disable the integration between Jitsi and your coturn server, as Jitsi seems to support the `auth-secret` authentication method only." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:74 -msgid "Customize the Coturn hostname (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:76 -msgid "By default, Coturn uses the same hostname as your Matrix homeserver (the value of `matrix_server_fqn_matrix`, which is typically `matrix.example.com`)." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:78 -msgid "If you'd like to use a custom subdomain for Coturn (e.g., `turn.example.com` or `t.matrix.example.com`), add the following configuration to your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:84 -msgid "The playbook will automatically:" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:85 -msgid "Configure Coturn to use this hostname" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:86 -msgid "Obtain an SSL certificate for the custom domain via Traefik" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:87 -msgid "Update all TURN URIs to point to the custom domain" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:89 -msgid "**Note**: Make sure the custom hostname resolves to your server's IP address via DNS before running the playbook." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:91 +#: ../../../docs/configuring-playbook-turn.md:42 msgid "Use your own external coturn server (optional)" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:93 +#: ../../../docs/configuring-playbook-turn.md:44 msgid "If you'd like to use another TURN server (be it coturn or some other one), add the following configuration to your `vars.yml` file. Make sure to replace `HOSTNAME_OR_IP` with your own." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:107 +#: ../../../docs/configuring-playbook-turn.md:58 msgid "If you have or want to enable Jitsi, you might want to enable the TURN server there too. If you do not do it, Jitsi will fall back to an upstream service." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:114 +#: ../../../docs/configuring-playbook-turn.md:65 msgid "You can put multiple host/port combinations if you'd like to." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:116 -msgid "Edit the reloading schedule (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:118 -msgid "By default the service is reloaded on 6:30 a.m. every day based on the `coturn_reload_schedule` variable so that new SSL certificates can kick in. It is defined in the format of systemd timer calendar." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:120 -msgid "To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs):" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:126 -msgid "**Note**: the actual job may run with a delay. See `coturn_reload_schedule_randomized_delay_sec` for its default value." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:128 +#: ../../../docs/configuring-playbook-turn.md:67 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:130 +#: ../../../docs/configuring-playbook-turn.md:69 msgid "There are some additional things you may wish to configure about the TURN server." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:132 +#: ../../../docs/configuring-playbook-turn.md:71 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:134 -msgid "`roles/galaxy/coturn/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +#: ../../../docs/configuring-playbook-turn.md:73 +msgid "`roles/custom/matrix-coturn/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:136 +#: ../../../docs/configuring-playbook-turn.md:75 msgid "Disabling coturn" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:138 -msgid "Coturn is only enabled by default when [Jitsi](configuring-playbook-jitsi.md) is enabled. In most instances, you don't need to explicitly disable it." +#: ../../../docs/configuring-playbook-turn.md:77 +msgid "If, for some reason, you'd like for the playbook to not install coturn (or to uninstall it if it was previously installed), add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:140 -msgid "To force the playbook to not install Coturn (even when Jitsi is enabled), add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-turn.md:83 +msgid "In that case, Synapse would not point to any coturn servers and audio/video call functionality may fail." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:146 +#: ../../../docs/configuring-playbook-turn.md:85 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:148 +#: ../../../docs/configuring-playbook-turn.md:87 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:155 +#: ../../../docs/configuring-playbook-turn.md:94 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:157 +#: ../../../docs/configuring-playbook-turn.md:96 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:159 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:161 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-coturn`." -msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po index b9c00d651..8c838b570 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po @@ -8,247 +8,247 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2026-02-13 10:32+0000\n" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-well-known.md:14 +#: ../../../docs/configuring-well-known.md:1 msgid "Configuring Service Discovery via .well-known" msgstr "" -#: ../../../docs/configuring-well-known.md:16 +#: ../../../docs/configuring-well-known.md:3 msgid "This documentation page explains how to configure Service discovery via `/.well-known/` files. Service discovery is a way for the Matrix network to discover where a Matrix server is." msgstr "" -#: ../../../docs/configuring-well-known.md:18 +#: ../../../docs/configuring-well-known.md:5 msgid "Types of well-known service discovery mechanism" msgstr "" -#: ../../../docs/configuring-well-known.md:20 +#: ../../../docs/configuring-well-known.md:7 msgid "There are 3 types of well-known service discovery mechanism that Matrix makes use of:" msgstr "" -#: ../../../docs/configuring-well-known.md:22 +#: ../../../docs/configuring-well-known.md:9 msgid "(important) **Federation Server discovery** (`/.well-known/matrix/server`) — assists other servers in the Matrix network with finding your server. With the default playbook configuration specified on the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), this is necessary for federation to work. Without a proper configuration, your server will effectively not be part of the Matrix network." msgstr "" -#: ../../../docs/configuring-well-known.md:24 +#: ../../../docs/configuring-well-known.md:11 msgid "(less important) **Client Server discovery** (`/.well-known/matrix/client`) — assists programs that you use to connect to your server (e.g. Element Web), so that they can make it more convenient for you by automatically configuring the \"Homeserver URL\" and \"Identity Server URL\" addresses." msgstr "" -#: ../../../docs/configuring-well-known.md:26 +#: ../../../docs/configuring-well-known.md:13 msgid "(optional) **Support service discovery** (`/.well-known/matrix/support`) — returns server admin contact and support page of the domain." msgstr "" -#: ../../../docs/configuring-well-known.md:28 +#: ../../../docs/configuring-well-known.md:15 msgid "Federation Server Discovery" msgstr "" -#: ../../../docs/configuring-well-known.md:30 +#: ../../../docs/configuring-well-known.md:17 msgid "All services created by this playbook are meant to be installed on their own server (such as `matrix.example.com`), instead of the base domain (`example.com`)." msgstr "" -#: ../../../docs/configuring-well-known.md:32 +#: ../../../docs/configuring-well-known.md:19 msgid "As [per the Server-Server specification](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), in order to use a short Matrix user ID like `@alice:example.com` instead of `@alice:matrix.example.com` while hosting services on a subdomain such as `matrix.example.com`, the Matrix network needs to be instructed of [server delegation](howto-server-delegation.md) / redirection." msgstr "" -#: ../../../docs/configuring-well-known.md:34 +#: ../../../docs/configuring-well-known.md:21 msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file." msgstr "" -#: ../../../docs/configuring-well-known.md:36 +#: ../../../docs/configuring-well-known.md:23 msgid "If you set up the DNS SRV record for server delegation instead, take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)" msgstr "" -#: ../../../docs/configuring-well-known.md:38 +#: ../../../docs/configuring-well-known.md:25 msgid "Client Server Discovery" msgstr "" -#: ../../../docs/configuring-well-known.md:40 +#: ../../../docs/configuring-well-known.md:27 msgid "Client Server Service discovery lets various client programs which support it, to receive a full user ID (e.g. `@alice:example.com`) and determine where the Matrix server is automatically (e.g. `https://matrix.example.com`)." msgstr "" -#: ../../../docs/configuring-well-known.md:42 +#: ../../../docs/configuring-well-known.md:29 msgid "This lets you (and your users) easily connect to your Matrix server without having to customize connection URLs. When using client programs that support it, you won't need to point them to `https://matrix.example.com` in Custom Server options manually anymore. The connection URL would be discovered automatically from your full username." msgstr "" -#: ../../../docs/configuring-well-known.md:44 +#: ../../../docs/configuring-well-known.md:31 msgid "Without /.well-known/matrix/client, the client will make the wrong \"homeserver URL\" assumption (it will default to using https://example.com, and users will need to notice and adjust it manually (changing it to https://matrix.example.com)." msgstr "" -#: ../../../docs/configuring-well-known.md:46 +#: ../../../docs/configuring-well-known.md:33 msgid "As [per the Client-Server specification](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery) Matrix does Client Server service discovery using a `/.well-known/matrix/client` file hosted on the base domain (e.g. `example.com`)." msgstr "" -#: ../../../docs/configuring-well-known.md:48 +#: ../../../docs/configuring-well-known.md:35 msgid "However, this playbook installs your Matrix server on another domain (e.g. `matrix.example.com`) and not on the base domain (e.g. `example.com`), so it takes a little extra manual effort to set up the file." msgstr "" -#: ../../../docs/configuring-well-known.md:50 +#: ../../../docs/configuring-well-known.md:37 msgid "Support Service Discovery (optional)" msgstr "" -#: ../../../docs/configuring-well-known.md:52 +#: ../../../docs/configuring-well-known.md:39 msgid "[MSC 1929](https://github.com/matrix-org/matrix-spec-proposals/pull/1929), which was added to [Matrix Specification version v1.10](https://spec.matrix.org/v1.10/client-server-api/#getwell-knownmatrixsupport), specifies a way to add contact details of admins, as well as a link to a support page for users who are having issues with the service. Automated services may also index this information and use it for abuse reports, etc." msgstr "" -#: ../../../docs/configuring-well-known.md:54 +#: ../../../docs/configuring-well-known.md:41 msgid "To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-well-known.md:75 +#: ../../../docs/configuring-well-known.md:62 msgid "Installing well-known files on the base domain's server" msgstr "" -#: ../../../docs/configuring-well-known.md:77 +#: ../../../docs/configuring-well-known.md:64 msgid "To implement the service discovery mechanisms, your base domain's server (e.g. `example.com`) needs to run an HTTPS-capable webserver." msgstr "" -#: ../../../docs/configuring-well-known.md:79 +#: ../../../docs/configuring-well-known.md:66 msgid "Serving the base domain from the Matrix server via the playbook" msgstr "" -#: ../../../docs/configuring-well-known.md:81 +#: ../../../docs/configuring-well-known.md:68 msgid "If you don't have a server for your base domain at all, you can use the Matrix server for this. If you don't need the base domain (e.g. `example.com`) for anything else (hosting a website, etc.), you can point it to the Matrix server's IP address and tell the playbook to configure it." msgstr "" -#: ../../../docs/configuring-well-known.md:83 +#: ../../../docs/configuring-well-known.md:70 msgid "**This is the easiest way to set up well-known serving** — letting the playbook handle the whole base domain for you (including SSL certificates, etc.) and take care to serve the appropriate well-known files automatically." msgstr "" -#: ../../../docs/configuring-well-known.md:85 +#: ../../../docs/configuring-well-known.md:72 msgid "If you decide to go this route, you don't need to read ahead in this document. Instead, go to [Serving the base domain](configuring-playbook-base-domain-serving.md) to learn how the playbook can help you set it up." msgstr "" -#: ../../../docs/configuring-well-known.md:87 +#: ../../../docs/configuring-well-known.md:74 msgid "However, if you need to use the base domain for other things, this method is less suitable than the one explained below." msgstr "" -#: ../../../docs/configuring-well-known.md:89 +#: ../../../docs/configuring-well-known.md:76 msgid "Manually installing well-known files on the base domain's server" msgstr "" -#: ../../../docs/configuring-well-known.md:91 +#: ../../../docs/configuring-well-known.md:78 msgid "If you're managing the base domain by yourself somehow, you'll need to set up serving of some `/.well-known/matrix/*` files from it via HTTPS." msgstr "" -#: ../../../docs/configuring-well-known.md:93 +#: ../../../docs/configuring-well-known.md:80 msgid "To make things easy for you to set up, this playbook generates and hosts a few well-known files on the Matrix domain's server. The files are generated at the `/matrix/static-files/public/.well-known/matrix/` path on the server and hosted at URLs like `https://matrix.example.com/.well-known/matrix/server` and `https://matrix.example.com/.well-known/matrix/client`, even though this is the wrong place to host them." msgstr "" -#: ../../../docs/configuring-well-known.md:95 +#: ../../../docs/configuring-well-known.md:82 msgid "You have two options when it comes to installing the files on the base domain's server:" msgstr "" -#: ../../../docs/configuring-well-known.md:97 +#: ../../../docs/configuring-well-known.md:84 msgid "(Option 1): **Copying the files manually** to your base domain's server" msgstr "" -#: ../../../docs/configuring-well-known.md:99 +#: ../../../docs/configuring-well-known.md:86 msgid "**Hint**: Option 2 is generally a better way to do this. Make sure to go with it, if possible." msgstr "" -#: ../../../docs/configuring-well-known.md:101 +#: ../../../docs/configuring-well-known.md:88 msgid "All you need to do is:" msgstr "" -#: ../../../docs/configuring-well-known.md:103 +#: ../../../docs/configuring-well-known.md:90 msgid "copy `/.well-known/matrix/server` and `/.well-known/matrix/client` from the Matrix server (e.g. `matrix.example.com`) to your base domain's server (`example.com`). You can find these files in the `/matrix/static-files/.well-known/matrix` directory on the Matrix server. They are also accessible on URLs like this: `https://matrix.example.com/.well-known/matrix/server` (same for `client`)." msgstr "" -#: ../../../docs/configuring-well-known.md:105 +#: ../../../docs/configuring-well-known.md:92 msgid "set up the server at your base domain (e.g. `example.com`) so that it adds an extra HTTP header when serving the `/.well-known/matrix/client` file. [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS), the `Access-Control-Allow-Origin` header should be set with a value of `*`. If you don't do this step, web-based Matrix clients (like Element Web) may fail to work. Setting up headers for the `/.well-known/matrix/server` file is not necessary, as this file is only consumed by non-browsers, which don't care about CORS." msgstr "" -#: ../../../docs/configuring-well-known.md:107 +#: ../../../docs/configuring-well-known.md:94 msgid "This is relatively easy to do and possibly your only choice if you can only host static files from the base domain's server. It is, however, **a little fragile**, as future updates performed by this playbook may regenerate the well-known files and you may need to notice that and copy them over again." msgstr "" -#: ../../../docs/configuring-well-known.md:109 +#: ../../../docs/configuring-well-known.md:96 msgid "(Option 2): **Setting up reverse-proxying** of the well-known files from the base domain's server to the Matrix server" msgstr "" -#: ../../../docs/configuring-well-known.md:111 +#: ../../../docs/configuring-well-known.md:98 msgid "This option is less fragile and generally better." msgstr "" -#: ../../../docs/configuring-well-known.md:113 -msgid "On the base domain's server (e.g. `example.com`), you can set up reverse-proxying (or simply a 302 redirect), so that any access for the `/.well-known/matrix` location prefix is forwarded to the Matrix domain's server (e.g. `matrix.example.com`)." +#: ../../../docs/configuring-well-known.md:100 +msgid "On the base domain's server (e.g. `example.com`), you can set up reverse-proxying, so that any access for the `/.well-known/matrix` location prefix is forwarded to the Matrix domain's server (e.g. `matrix.example.com`)." msgstr "" -#: ../../../docs/configuring-well-known.md:115 +#: ../../../docs/configuring-well-known.md:102 msgid "With this method, you **don't need** to add special HTTP headers for [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) reasons (like `Access-Control-Allow-Origin`), because your Matrix server (where requests ultimately go) will be configured by this playbook correctly." msgstr "" -#: ../../../docs/configuring-well-known.md:117 +#: ../../../docs/configuring-well-known.md:104 msgid "**For nginx**, it would be something like this:" msgstr "" -#: ../../../docs/configuring-well-known.md:134 +#: ../../../docs/configuring-well-known.md:121 msgid "**For Apache2**, it would be something like this:" msgstr "" -#: ../../../docs/configuring-well-known.md:148 +#: ../../../docs/configuring-well-known.md:135 msgid "**For Caddy 2**, it would be something like this:" msgstr "" -#: ../../../docs/configuring-well-known.md:158 +#: ../../../docs/configuring-well-known.md:145 msgid "**For HAProxy**, it would be something like this:" msgstr "" -#: ../../../docs/configuring-well-known.md:177 +#: ../../../docs/configuring-well-known.md:164 msgid "**For Netlify**, configure a [redirect](https://docs.netlify.com/routing/redirects/) using a `_redirects` file in the [publish directory](https://docs.netlify.com/configure-builds/overview/#definitions) with contents like this:" msgstr "" -#: ../../../docs/configuring-well-known.md:183 +#: ../../../docs/configuring-well-known.md:170 msgid "**For AWS CloudFront**" msgstr "" -#: ../../../docs/configuring-well-known.md:185 +#: ../../../docs/configuring-well-known.md:172 msgid "Add a custom origin with matrix.example.com to your distribution" msgstr "" -#: ../../../docs/configuring-well-known.md:186 +#: ../../../docs/configuring-well-known.md:173 msgid "Add two behaviors, one for `.well-known/matrix/client` and one for `.well-known/matrix/server` and point them to your new origin." msgstr "" -#: ../../../docs/configuring-well-known.md:188 +#: ../../../docs/configuring-well-known.md:175 msgid "Make sure to:" msgstr "" -#: ../../../docs/configuring-well-known.md:190 +#: ../../../docs/configuring-well-known.md:177 msgid "**replace `example.com`** in the server configuration with your actual domain name" msgstr "" -#: ../../../docs/configuring-well-known.md:191 +#: ../../../docs/configuring-well-known.md:178 msgid "and: to **do this for the HTTPS-enabled server block**, as that's where Matrix expects the file to be" msgstr "" -#: ../../../docs/configuring-well-known.md:193 +#: ../../../docs/configuring-well-known.md:180 msgid "Confirming it works" msgstr "" -#: ../../../docs/configuring-well-known.md:195 +#: ../../../docs/configuring-well-known.md:182 msgid "No matter which method you've used to set up the well-known files, if you've done it correctly you should be able to see a JSON file at these URLs:" msgstr "" -#: ../../../docs/configuring-well-known.md:197 +#: ../../../docs/configuring-well-known.md:184 msgid "`https://example.com/.well-known/matrix/server`" msgstr "" -#: ../../../docs/configuring-well-known.md:198 +#: ../../../docs/configuring-well-known.md:185 msgid "`https://example.com/.well-known/matrix/client`" msgstr "" -#: ../../../docs/configuring-well-known.md:199 +#: ../../../docs/configuring-well-known.md:186 msgid "`https://example.com/.well-known/matrix/support`" msgstr "" -#: ../../../docs/configuring-well-known.md:201 -msgid "You can also check if everything is configured correctly, by [checking if services work](maintenance-and-troubleshooting.md#how-to-check-if-services-work)." +#: ../../../docs/configuring-well-known.md:188 +msgid "You can also check if everything is configured correctly, by [checking if services work](maintenance-checking-services.md)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/faq.po b/i18n/locales/bg/LC_MESSAGES/docs/faq.po index 90a5c1a73..6ebcf4d73 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/faq.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/faq.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,824 +19,876 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/faq.md:13 +#: ../../../docs/faq.md:1 msgid "Frequently Asked Questions" msgstr "" -#: ../../../docs/faq.md:15 +#: ../../../docs/faq.md:3 msgid "This documentation page tries to answer various Frequently Asked Questions about all things [Matrix](https://matrix.org/), with a focus on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work))." msgstr "" -#: ../../../docs/faq.md:17 +#: ../../../docs/faq.md:5 msgid "This FAQ page does not intend to replace the [matrix.org FAQ](https://matrix.org/faq/) (please see that one too)." msgstr "" -#: ../../../docs/faq.md:19 +#: ../../../docs/faq.md:7 msgid "We've only started this FAQ recently, so it's still somewhat empty." msgstr "" -#: ../../../docs/faq.md:21 +#: ../../../docs/faq.md:9 msgid "Also, we encourage you to not dig yourself into a hole by reading way too much. When you've heard enough, proceed to installation. To get started, see [below](#how-do-i-run-the-installation) about our installation guides." msgstr "" -#: ../../../docs/faq.md:23 +#: ../../../docs/faq.md:11 msgid "Introductory" msgstr "" -#: ../../../docs/faq.md:25 +#: ../../../docs/faq.md:13 msgid "Where do I find more questions and answers about Matrix?" msgstr "" -#: ../../../docs/faq.md:27 +#: ../../../docs/faq.md:15 msgid "This is a Frequently Asked Questions page focused on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work)) for deploying a [Matrix](https://matrix.org/) server." msgstr "" -#: ../../../docs/faq.md:29 +#: ../../../docs/faq.md:17 msgid "For a lot more generic questions and answers, see the [matrix.org FAQ](https://matrix.org/faq/)." msgstr "" -#: ../../../docs/faq.md:31 +#: ../../../docs/faq.md:19 msgid "What is Matrix? What is Element? What is Synapse? Why are you confusing me with so many terms?" msgstr "" -#: ../../../docs/faq.md:33 +#: ../../../docs/faq.md:21 msgid "[Matrix](https://matrix.org/) is a new type of realtime communication (chat) network, the closest analogy to which is probably \"email\"." msgstr "" -#: ../../../docs/faq.md:35 +#: ../../../docs/faq.md:23 msgid "You don't just use the \"email\" protocols (SMTP, POP3, IMAP) directly though. There's a *server* somewhere which stores your data (`@gmail.com`, `@yahoo.com`, `@hotmail.com`, `@your-company.com`) and you access it by using these \"email\" protocols via some *client* program (Outlook, Thunderbird, some website, etc)." msgstr "" -#: ../../../docs/faq.md:37 +#: ../../../docs/faq.md:25 msgid "In the world of the Matrix chat protocol, there are various client programs. The first and currently most full-featured one is called [Element](https://element.io/) (used to be called Riot.im and Vector.im in the past). There are [many other clients](https://matrix.org/clients/). You can switch clients as much as you want until you find the one that is right for you on a given platform (you may use Element Desktop on your desktop, but Fluffychat on your phone, etc)." msgstr "" -#: ../../../docs/faq.md:39 +#: ../../../docs/faq.md:27 msgid "Matrix is also like email due to the fact that there are many servers around the world which can all talk to each other (you can send email from `@gmail.com` addresses to `@yahoo.com` and `@hotmail.com` addresses). It's the same with Matrix (`@bob:example.com` can talk to `@alice:example.org`)." msgstr "" -#: ../../../docs/faq.md:41 +#: ../../../docs/faq.md:29 msgid "If someone else is hosting your Matrix server (you being `@alice:matrix.org` or some other public server like this), all you need is a Matrix client program, like Element Web or Element X Android." msgstr "" -#: ../../../docs/faq.md:43 +#: ../../../docs/faq.md:31 msgid "If you'd like to host your own server (you being `@alice:example.com`), you'd need to set up a Matrix server program, like Synapse." msgstr "" -#: ../../../docs/faq.md:45 +#: ../../../docs/faq.md:33 msgid "In short:" msgstr "" -#: ../../../docs/faq.md:47 +#: ../../../docs/faq.md:35 msgid "Matrix is the protocol — a set of rules about how the chat network operates" msgstr "" -#: ../../../docs/faq.md:48 +#: ../../../docs/faq.md:36 msgid "Element is a client program you can use to participate on the Matrix chat network via some server (yours or someone else's). There are also [many other client programs](https://matrix.org/clients/)." msgstr "" -#: ../../../docs/faq.md:49 +#: ../../../docs/faq.md:37 msgid "Synapse is a server program you can use to host your very own Matrix server." msgstr "" -#: ../../../docs/faq.md:51 +#: ../../../docs/faq.md:39 msgid "This FAQ here mostly focuses on installing various Matrix services using the Ansible automation tool. You can learn much more about Matrix in the [matrix.org FAQ](https://matrix.org/faq/)." msgstr "" -#: ../../../docs/faq.md:53 +#: ../../../docs/faq.md:41 msgid "People I wish to talk to are not on Matrix. Can I talk to them?" msgstr "" -#: ../../../docs/faq.md:55 +#: ../../../docs/faq.md:43 msgid "You most likely can. Besides Matrix-native chats, Matrix also supports the concept of \"bridging\", which allows you to plug other networks into it." msgstr "" -#: ../../../docs/faq.md:57 +#: ../../../docs/faq.md:45 msgid "This Ansible playbook can help you install [tens of bridges for various networks](configuring-playbook.md#bridging-other-networks)." msgstr "" -#: ../../../docs/faq.md:59 +#: ../../../docs/faq.md:47 msgid "Besides setting up your own bridges (preferable), you can also use some [public bridges hosted by others](https://publiclist.anchel.nl/#bridges)." msgstr "" -#: ../../../docs/faq.md:61 +#: ../../../docs/faq.md:49 msgid "How do I get started with Matrix?" msgstr "" -#: ../../../docs/faq.md:63 +#: ../../../docs/faq.md:51 msgid "One of [Matrix](https://matrix.org/)'s distinguishing strengths (compared to other chat networks) is its decentralized nature. There's not just one entity (company, organization) controlling the servers. Rather there's thousands of servers operated by different people — one server being insecure, slow or disrespective toward its users does not affect the rest of the network. To participate in that decentralization in its fullest, consider hosting your own server or using some public server other than the largest/default one (`matrix.org`)." msgstr "" -#: ../../../docs/faq.md:65 +#: ../../../docs/faq.md:53 msgid "There are 3 ways to get into Matrix, depending on your technical ability and needs:" msgstr "" -#: ../../../docs/faq.md:67 +#: ../../../docs/faq.md:55 msgid "**using the existing default server** — the easiest way is to use an existing server. The largest public Matrix server is `matrix.org` and it's configured as a default server in clients such as [Element Web](https://app.element.io) and many others. Just use Element Web on the browser via that link (or [download client apps for your Desktop or smartphone](https://element.io/app-for-productivity)), create an account and start chatting." msgstr "" -#: ../../../docs/faq.md:69 +#: ../../../docs/faq.md:57 msgid "**using some other server** — instead of using the largest public server (`matrix.org`), you can use another public one. Here's a [list of public Matrix servers](https://joinmatrix.org/servers/) to choose from. Go to [Element Web](https://app.element.io) or download [some other client](https://matrix.org/clients/) of your choosing and adjust the homeserver URL during login." msgstr "" -#: ../../../docs/faq.md:71 +#: ../../../docs/faq.md:59 msgid "**using your own server** — running your own server puts you in ultimate control of your data. It also lets you have your own user IDs (e.g. `@bob:example.com`). See [How do I set up my own Matrix server](#how-do-i-set-up-my-own-matrix-server)." msgstr "" -#: ../../../docs/faq.md:73 +#: ../../../docs/faq.md:61 msgid "How do I set up my own Matrix server?" msgstr "" -#: ../../../docs/faq.md:75 +#: ../../../docs/faq.md:63 msgid "Normally, you'd first choose the [Matrix](https://matrix.org/) server software you'd like to run. At the time of this writing (January/2021), there's only one fully-featured server program, so there's only one reasonable choice. That's [Synapse](https://github.com/element-hq/synapse)." msgstr "" -#: ../../../docs/faq.md:77 +#: ../../../docs/faq.md:65 msgid "There are [many guides about installing Synapse](https://matrix.org/docs/guides/#installing-synapse). Using this Ansible playbook is just one way of doing it." msgstr "" -#: ../../../docs/faq.md:79 +#: ../../../docs/faq.md:67 msgid "Naturally, we're biased, so our usual recommendation is to go with this [Ansible](https://www.ansible.com/) playbook, instead of installing Synapse (and many many other things around it) manually." msgstr "" -#: ../../../docs/faq.md:81 +#: ../../../docs/faq.md:69 msgid "To get started with the playbook, check out the [Quick start](quick-start.md) or full installation guide (starting at the [Prerequisites](prerequisites.md) page)." msgstr "" -#: ../../../docs/faq.md:83 +#: ../../../docs/faq.md:71 msgid "What is Ansible? How does it work?" msgstr "" -#: ../../../docs/faq.md:85 +#: ../../../docs/faq.md:73 msgid "[Ansible](https://www.ansible.com/) is an automation program. This \"playbook\" is a collection of tasks/scripts that will set up a [Matrix](https://matrix.org/) server for you, so you don't have to perform these tasks manually." msgstr "" -#: ../../../docs/faq.md:87 +#: ../../../docs/faq.md:75 msgid "We have written these automated tasks for you and all you need to do is execute them using the Ansible program." msgstr "" -#: ../../../docs/faq.md:89 +#: ../../../docs/faq.md:77 msgid "You can install Ansible and this playbook code repository on your own computer and tell it to install Matrix services at the server living at `matrix.example.com`. We recommend installing Ansible on your own computer." msgstr "" -#: ../../../docs/faq.md:91 +#: ../../../docs/faq.md:79 msgid "Alternatively, you can download Ansible and the playbook itself directly on the `matrix.example.com` server." msgstr "" -#: ../../../docs/faq.md:93 +#: ../../../docs/faq.md:81 msgid "To learn more, see our [dedicated Ansible documentation page](ansible.md)." msgstr "" -#: ../../../docs/faq.md:95 +#: ../../../docs/faq.md:83 msgid "What is `just`?" msgstr "" -#: ../../../docs/faq.md:97 +#: ../../../docs/faq.md:85 msgid "[`just`](https://github.com/casey/just) is a modern command-runner alternative to [make](https://www.gnu.org/software/make/). It can be used to invoke commands with less typing." msgstr "" -#: ../../../docs/faq.md:99 +#: ../../../docs/faq.md:87 msgid "The `just` utility executes shortcut commands (called \"recipes\"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile)." msgstr "" -#: ../../../docs/faq.md:101 +#: ../../../docs/faq.md:89 msgid "For details about `just` commands, take a look at: [Running `just` commands](just.md)." msgstr "" -#: ../../../docs/faq.md:103 +#: ../../../docs/faq.md:91 msgid "The playbook also contains a `Makefile` for the `make` tool, but most of the just recipes are not available as targets in the `Makefile`." msgstr "" -#: ../../../docs/faq.md:105 +#: ../../../docs/faq.md:93 msgid "Why use this playbook and not install Synapse and other things manually?" msgstr "" -#: ../../../docs/faq.md:107 +#: ../../../docs/faq.md:95 msgid "There are various guides telling you how easy it is to install [Synapse](https://github.com/element-hq/synapse)." msgstr "" -#: ../../../docs/faq.md:109 +#: ../../../docs/faq.md:97 msgid "Reading the documentation of this Ansible playbook, you may also be thinking:" msgstr "" -#: ../../../docs/faq.md:111 +#: ../../../docs/faq.md:99 msgid "I don't know what [Ansible](https://www.ansible.com/) is. I don't know what [Docker](https://www.docker.com/) is. This looks more complicated." msgstr "" -#: ../../../docs/faq.md:113 +#: ../../../docs/faq.md:101 msgid "… so you may be leaning toward [installing Synapse manually](https://github.com/element-hq/synapse/blob/master/INSTALL.md)." msgstr "" -#: ../../../docs/faq.md:115 +#: ../../../docs/faq.md:103 msgid "The problem with a manual installation is:" msgstr "" -#: ../../../docs/faq.md:117 +#: ../../../docs/faq.md:105 msgid "Synapse is written in Python. If not packaged for your distribution, you'd need to install various Python modules, etc., and keep them updated." msgstr "" -#: ../../../docs/faq.md:118 +#: ../../../docs/faq.md:106 msgid "Synapse requires a [Postgres](https://www.postgresql.org/) database (it can run on SQLite, but that's very much discouraged). So you'd need to install Postgres as well." msgstr "" -#: ../../../docs/faq.md:119 +#: ../../../docs/faq.md:107 msgid "you may also need a reverse-proxy server in front of it (nginx, Apache), so you'd need to be familiar with that" msgstr "" -#: ../../../docs/faq.md:120 +#: ../../../docs/faq.md:108 msgid "SSL is required, so you'd need to obtain Let's Encrypt (or other free or non-free) certificates for one or more domain names. You'd need to be familiar with [certbot](https://certbot.eff.org/) (when using Let's Encrypt) or similar software." msgstr "" -#: ../../../docs/faq.md:121 +#: ../../../docs/faq.md:109 msgid "for each additional component you'd like to add (client like [Element](https://element.io), bridge to some other chat network, integration manager (stickers, other services, Identity Manager, etc.), you'll need to spend extra time installing and wiring it with the rest of the system in a way that works." msgstr "" -#: ../../../docs/faq.md:122 +#: ../../../docs/faq.md:110 msgid "you'll likely get slower updates for all of these components, depending on your distro packaging or your own time and ability" msgstr "" -#: ../../../docs/faq.md:124 +#: ../../../docs/faq.md:112 msgid "The playbook, on the other hand, installs a bunch of components for you by default, obtains SSL certificates for you, etc. If you'd like, you can enable various bridges and other services with very little effort. All the components are wired to work together." msgstr "" -#: ../../../docs/faq.md:126 +#: ../../../docs/faq.md:114 msgid "All services run in Docker containers (most being officially provided by each component's developers), so we're not at the mercy of distro packaging." msgstr "" -#: ../../../docs/faq.md:128 +#: ../../../docs/faq.md:116 msgid "Why use this playbook and not just use the Docker image directly?" msgstr "" -#: ../../../docs/faq.md:130 +#: ../../../docs/faq.md:118 msgid "Reasons are similar to the reasons for not installing manually." msgstr "" -#: ../../../docs/faq.md:132 +#: ../../../docs/faq.md:120 msgid "Besides Synapse, you'd need other things — a Postgres database, likely the [Element](https://element.io) client, etc., etc." msgstr "" -#: ../../../docs/faq.md:134 +#: ../../../docs/faq.md:122 msgid "Using the playbook, you get all these components in a way that works well together out of the box." msgstr "" -#: ../../../docs/faq.md:136 +#: ../../../docs/faq.md:124 msgid "Occasionally I see some people are talking about \"MDAD\". What is it?" msgstr "" -#: ../../../docs/faq.md:138 +#: ../../../docs/faq.md:126 msgid "It is the acronym of us: **m**atrix-**d**ocker-**a**nsible-**d**eploy." msgstr "" -#: ../../../docs/faq.md:140 +#: ../../../docs/faq.md:128 msgid "What's different about this Ansible playbook compared to [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy)?" msgstr "" -#: ../../../docs/faq.md:142 +#: ../../../docs/faq.md:130 msgid "This is similar to the [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy) Ansible deployment, but:" msgstr "" -#: ../../../docs/faq.md:144 +#: ../../../docs/faq.md:132 msgid "this one is a complete Ansible playbook (instead of just a role), so it's **easier to run** — especially for folks not familiar with Ansible" msgstr "" -#: ../../../docs/faq.md:146 +#: ../../../docs/faq.md:134 msgid "this one installs and hooks together **a lot more Matrix-related services** for you (see above)" msgstr "" -#: ../../../docs/faq.md:148 +#: ../../../docs/faq.md:136 msgid "this one **can be executed more than once** without causing trouble" msgstr "" -#: ../../../docs/faq.md:150 +#: ../../../docs/faq.md:138 msgid "works on various distros: **CentOS** (7.0+), Debian-based distributions (**Debian** 10/Buster+, **Ubuntu** 18.04+), **Archlinux**" msgstr "" -#: ../../../docs/faq.md:152 +#: ../../../docs/faq.md:140 msgid "this one installs everything in a single directory (`/matrix` by default) and **doesn't \"contaminate\" your server** with files all over the place" msgstr "" -#: ../../../docs/faq.md:154 +#: ../../../docs/faq.md:142 msgid "this one **doesn't necessarily take over** ports 80 and 443. By default, it sets up [Traefik](https://doc.traefik.io/traefik/) for you there, but you can also [use your own webserver](configuring-playbook-own-webserver.md)" msgstr "" -#: ../../../docs/faq.md:156 +#: ../../../docs/faq.md:144 msgid "this one **runs everything in Docker containers**, so it's likely more predictable and less fragile (see [Docker images used by this playbook](container-images.md))" msgstr "" -#: ../../../docs/faq.md:158 +#: ../../../docs/faq.md:146 msgid "this one retrieves and automatically renews free [Let's Encrypt](https://letsencrypt.org/) **SSL certificates** for you" msgstr "" -#: ../../../docs/faq.md:160 +#: ../../../docs/faq.md:148 msgid "this one optionally can store the `media_store` content repository files on [Amazon S3](https://aws.amazon.com/s3/) (but defaults to storing files on the server's filesystem)" msgstr "" -#: ../../../docs/faq.md:162 +#: ../../../docs/faq.md:150 msgid "this one optionally **allows you to use an external PostgreSQL server** for Synapse's database (but defaults to running one in a container)" msgstr "" -#: ../../../docs/faq.md:164 +#: ../../../docs/faq.md:152 msgid "helps you **import data from a previous installation** (so you can migrate your manual virtualenv/Docker setup to a more managed one)" msgstr "" -#: ../../../docs/faq.md:166 +#: ../../../docs/faq.md:154 msgid "this one is actually **maintained**" msgstr "" -#: ../../../docs/faq.md:168 +#: ../../../docs/faq.md:156 msgid "Server-related" msgstr "" -#: ../../../docs/faq.md:170 +#: ../../../docs/faq.md:158 msgid "What kind of server do I need to install Matrix using this Ansible playbook?" msgstr "" -#: ../../../docs/faq.md:172 +#: ../../../docs/faq.md:160 msgid "We list our server requirements in [Prerequisites](prerequisites.md)." msgstr "" -#: ../../../docs/faq.md:174 +#: ../../../docs/faq.md:162 msgid "Why not run Matrix on Kubernetes?" msgstr "" -#: ../../../docs/faq.md:176 +#: ../../../docs/faq.md:164 msgid "There's no reason not to run Matrix on [Kubernetes](https://kubernetes.io/)." msgstr "" -#: ../../../docs/faq.md:178 +#: ../../../docs/faq.md:166 msgid "However, that's overly complicated for thousands of us who just want to run a single small (and sometimes not so small) Matrix server, either using \"cloud\" servers or even a [Raspberry Pi](https://www.raspberrypi.org/) at home." msgstr "" -#: ../../../docs/faq.md:180 +#: ../../../docs/faq.md:168 msgid "For us, a Kubernetes-based setup which requires a cluster of multiple computers and is more technically-involved is a no-go." msgstr "" -#: ../../../docs/faq.md:182 +#: ../../../docs/faq.md:170 msgid "There are others working on automating a Matrix-on-Kubernetes setup, such as this [Helm](https://helm.sh/) chart: https://github.com/dacruz21/matrix-chart." msgstr "" -#: ../../../docs/faq.md:184 +#: ../../../docs/faq.md:172 msgid "Why don't you use Podman instead of Docker?" msgstr "" -#: ../../../docs/faq.md:186 +#: ../../../docs/faq.md:174 msgid "We like the philosophy of a daemonless container runtime, but [Podman](https://podman.io) is just not ready for our use case yet." msgstr "" -#: ../../../docs/faq.md:188 +#: ../../../docs/faq.md:176 msgid "Learn more about our past experiences/attempts to give Podman a chance, by reading [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/520)." msgstr "" -#: ../../../docs/faq.md:190 +#: ../../../docs/faq.md:178 msgid "In short, `alias podman=docker` is a lie (for us)." msgstr "" -#: ../../../docs/faq.md:192 +#: ../../../docs/faq.md:180 msgid "Why use Docker?" msgstr "" -#: ../../../docs/faq.md:194 +#: ../../../docs/faq.md:182 msgid "[Docker](https://www.docker.com/) is one of our 2 hard dependencies (the other one being [systemd](https://systemd.io/))." msgstr "" -#: ../../../docs/faq.md:196 +#: ../../../docs/faq.md:184 msgid "It lets us run services in an isolated manner and independently of the (usually old) packages available for distributions." msgstr "" -#: ../../../docs/faq.md:198 +#: ../../../docs/faq.md:186 msgid "It also lets us have a unified setup which runs the same across various supported distros (see them on [Prerequisites](prerequisites.md))." msgstr "" -#: ../../../docs/faq.md:200 +#: ../../../docs/faq.md:188 msgid "Is Docker a hard requirement?" msgstr "" -#: ../../../docs/faq.md:202 +#: ../../../docs/faq.md:190 msgid "Yes. See [Why don't you use Podman instead of Docker?](#why-dont-you-use-podman-instead-of-docker) for why we're not using another container runtime." msgstr "" -#: ../../../docs/faq.md:204 +#: ../../../docs/faq.md:192 msgid "All of our services run in containers. It's how we achieve predictability and also how we support tens of different services across lots of distros." msgstr "" -#: ../../../docs/faq.md:206 +#: ../../../docs/faq.md:194 msgid "The only thing we need on the distro is systemd and Python (we install Docker ourselves, unless you ask us not to)." msgstr "" -#: ../../../docs/faq.md:208 +#: ../../../docs/faq.md:196 msgid "Why don't you use docker-compose?" msgstr "" -#: ../../../docs/faq.md:210 +#: ../../../docs/faq.md:198 msgid "Instead of using [docker-compose](https://docs.docker.com/compose/), we prefer installing systemd services and scheduling those independently." msgstr "" -#: ../../../docs/faq.md:212 +#: ../../../docs/faq.md:200 msgid "There are people who have worked on turning this setup into a docker-compose-based one. See these experiments [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/64#issuecomment-603164625). There is also a demo project ([element-docker-demo](https://github.com/element-hq/element-docker-demo)) by Element." msgstr "" -#: ../../../docs/faq.md:214 +#: ../../../docs/faq.md:202 msgid "Can I run this on a distro without systemd?" msgstr "" -#: ../../../docs/faq.md:216 +#: ../../../docs/faq.md:204 msgid "No. [systemd](https://systemd.io/) is one of our 2 hard dependencies (the other one being [Docker](https://www.docker.com/))." msgstr "" -#: ../../../docs/faq.md:218 +#: ../../../docs/faq.md:206 msgid "Can I install this on a Raspberry Pi?" msgstr "" -#: ../../../docs/faq.md:220 +#: ../../../docs/faq.md:208 msgid "Yes, you can. See our [Alternative Architectures](alternative-architectures.md) documentation page." msgstr "" -#: ../../../docs/faq.md:222 +#: ../../../docs/faq.md:210 msgid "Whether a Raspberry Pi has enough power to give you a good experience is another question. It depends on your use case." msgstr "" -#: ../../../docs/faq.md:224 +#: ../../../docs/faq.md:212 msgid "Also see: [What kind of server specs do I need?](#what-kind-of-server-specs-do-i-need)." msgstr "" -#: ../../../docs/faq.md:226 +#: ../../../docs/faq.md:214 msgid "What kind of server specs do I need?" msgstr "" -#: ../../../docs/faq.md:228 +#: ../../../docs/faq.md:216 msgid "This largely depends on your use case. It's not so much the number of users that you plan to host, but rather the number of large rooms they will join." msgstr "" -#: ../../../docs/faq.md:230 +#: ../../../docs/faq.md:218 msgid "Federated rooms with lots of history and containing hundreds of other servers are very heavy CPU-wise and memory-wise." msgstr "" -#: ../../../docs/faq.md:232 +#: ../../../docs/faq.md:220 msgid "You can probably use a 1 CPU + 1GB memory server to host hundreds of local users just fine, but as soon as one of them joins a federated room like `#matrix:matrix.org` (Matrix HQ) or some IRC-bridged room (say `##linux`), your server will get the need for a lot more power (at least 2GB RAM, etc)." msgstr "" -#: ../../../docs/faq.md:234 +#: ../../../docs/faq.md:222 msgid "Running Matrix on a server with 1GB of memory is possible (especially if you disable some not-so-important services). See [How do I optimize this setup for a low-power server?](#how-do-i-optimize-this-setup-for-a-low-power-server)." msgstr "" -#: ../../../docs/faq.md:236 +#: ../../../docs/faq.md:224 msgid "**We recommend starting with a server having at least 2GB of memory** and even then using it sparingly. If you know for sure you'll be joining various large rooms, etc., then going for 4GB of memory or more is a good idea." msgstr "" -#: ../../../docs/faq.md:238 -msgid "Besides the regular Matrix stuff, we also support things like video-conferencing using [Jitsi](configuring-playbook-jitsi.md) and other additional services which (when installed) may use up a lot of memory. Things do add up. Besides the Synapse Matrix server, Jitsi is especially notorious for consuming a lot of resources. If you plan on running Jitsi, we recommend a server with at least 2GB of memory (preferably more). See our [Jitsi documentation page](configuring-playbook-jitsi.md) to learn how to optimize its memory/CPU usage." +#: ../../../docs/faq.md:226 +msgid "Besides the regular Matrix stuff, we also support things like video-conferencing using [Jitsi](configuring-playbook-jitsi.md) and other additional services which (when installed) may use up a lot of memory. Things do add up. Besides the Synapse Matrix server, Jitsi is especially notorious for consuming a lot of resources. If you plan on running Jitsi, we recommend a server with at least 2GB of memory (preferrably more). See our [Jitsi documentation page](configuring-playbook-jitsi.md) to learn how to optimize its memory/CPU usage." msgstr "" -#: ../../../docs/faq.md:240 +#: ../../../docs/faq.md:228 msgid "Can I run this in an LXC container?" msgstr "" -#: ../../../docs/faq.md:242 +#: ../../../docs/faq.md:230 msgid "If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container." msgstr "" -#: ../../../docs/faq.md:244 +#: ../../../docs/faq.md:232 msgid "Configuration" msgstr "" -#: ../../../docs/faq.md:246 +#: ../../../docs/faq.md:234 msgid "Why install my server at matrix.example.com and not at the base domain?" msgstr "" -#: ../../../docs/faq.md:248 +#: ../../../docs/faq.md:236 msgid "It's the same with email servers. Your email address is likely `name@company.com`, not `name@mail.company.com`, even though it's `mail.company.com` that is really handling your data for `@company.com` email to work." msgstr "" -#: ../../../docs/faq.md:250 +#: ../../../docs/faq.md:238 msgid "Using a separate domain name is easier to manage (although it's a little hard to get right at first) and keeps your Matrix server isolated from your website (if you have one), from your email server (if you have one), etc. Therefore, this playbook sets up services on your Matrix server (`matrix.example.com`) by default." msgstr "" -#: ../../../docs/faq.md:252 +#: ../../../docs/faq.md:240 msgid "I don't control anything on the base domain and can't set up delegation to matrix.example.com. What do I do?" msgstr "" -#: ../../../docs/faq.md:254 +#: ../../../docs/faq.md:242 msgid "If you're not in control of your base domain (or the server handling it) at all, you can take a look at [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" msgstr "" -#: ../../../docs/faq.md:256 +#: ../../../docs/faq.md:244 msgid "I can't set up HTTPS on the base domain. How will I get Matrix federating?" msgstr "" -#: ../../../docs/faq.md:258 +#: ../../../docs/faq.md:246 msgid "If you really can't obtain an HTTPS certificate for your base domain, you can take a look at [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" msgstr "" -#: ../../../docs/faq.md:260 +#: ../../../docs/faq.md:248 msgid "How do I install on matrix.example.com without involving the base domain?" msgstr "" -#: ../../../docs/faq.md:262 +#: ../../../docs/faq.md:250 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/faq.md:283 +#: ../../../docs/faq.md:271 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/faq.md:290 +#: ../../../docs/faq.md:278 msgid "**Notes**:" msgstr "" -#: ../../../docs/faq.md:292 +#: ../../../docs/faq.md:280 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/faq.md:294 +#: ../../../docs/faq.md:282 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/faq.md:296 +#: ../../../docs/faq.md:284 msgid "Without setting up [server delegation](howto-server-delegation.md) to `matrix.example.com`, your user IDs will be like `@alice:matrix.example.com`. This is equivalent to having an email address like `bob@mail.company.com`, instead of just `bob@company.com`." msgstr "" -#: ../../../docs/faq.md:298 +#: ../../../docs/faq.md:286 msgid "I don't use the base domain for anything. How am I supposed to set up Server Delegation for Matrix services?" msgstr "" -#: ../../../docs/faq.md:300 +#: ../../../docs/faq.md:288 msgid "If you don't use your base domain for anything, then it's hard for you to \"serve files over HTTPS\" on it — something we ask you to do for the [.well-known](configuring-well-known.md) setup (needed for [Server Delegation](howto-server-delegation.md))." msgstr "" -#: ../../../docs/faq.md:302 +#: ../../../docs/faq.md:290 msgid "Luckily, the playbook can set up your Matrix server (at `matrix.example.com`) to also handle traffic for the base domain (`example.com`)." msgstr "" -#: ../../../docs/faq.md:304 +#: ../../../docs/faq.md:292 msgid "See [Serving the base domain](configuring-playbook-base-domain-serving.md)." msgstr "" -#: ../../../docs/faq.md:306 +#: ../../../docs/faq.md:294 msgid "How do I optimize this setup for a low-power server?" msgstr "" -#: ../../../docs/faq.md:308 -msgid "For a low-power server, it's best to use an alternative homeserver implementation (other than [Synapse](configuring-playbook-synapse.md))." +#: ../../../docs/faq.md:296 +msgid "You can disable some not-so-important services to save on memory." msgstr "" -#: ../../../docs/faq.md:310 -msgid "You can disable some not-so-important services to save on memory." +#: ../../../docs/faq.md:318 +msgid "You can also consider implementing a restriction on room complexity, in order to prevent users from joining very heavy rooms:" msgstr "" -#: ../../../docs/faq.md:317 +#: ../../../docs/faq.md:328 msgid "If you've installed [Jitsi](configuring-playbook-jitsi.md) (not installed by default), there are additional optimizations listed on its documentation page that you can perform." msgstr "" -#: ../../../docs/faq.md:320 -msgid "Synapse-specific optimizations" +#: ../../../docs/faq.md:330 +msgid "I already have Docker on my server. Can you stop installing Docker via the playbook?" msgstr "" -#: ../../../docs/faq.md:322 -msgid "If you're using [Synapse](configuring-playbook-synapse.md), you can also consider the following optimizations:" +#: ../../../docs/faq.md:332 +msgid "Yes, we can stop installing Docker ourselves. Just use this in your `vars.yml` file:" msgstr "" -#: ../../../docs/faq.md:332 -msgid "You can also consider [implementing a restriction on room complexity](configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts), in order to prevent users from joining very heavy rooms:" +#: ../../../docs/faq.md:338 +msgid "I run another webserver on the same server where I wish to install Matrix. What now?" msgstr "" #: ../../../docs/faq.md:340 -msgid "I already have Docker on my server. Can you stop installing Docker via the playbook?" +msgid "By default, we install a webserver for you ([Traefik](https://doc.traefik.io/traefik/)), but you can also use [your own webserver](configuring-playbook-own-webserver.md)." msgstr "" #: ../../../docs/faq.md:342 -msgid "Yes, we can stop installing Docker ourselves. Just use this in your `vars.yml` file:" +msgid "How is the effective configuration determined?" +msgstr "" + +#: ../../../docs/faq.md:344 +msgid "Configuration variables are defined in multiple places in this playbook and are considered in this order:" +msgstr "" + +#: ../../../docs/faq.md:346 +msgid "there are defaults coming from each role's defaults file (`role/matrix*/defaults/main.yml`). These variable values aim to be good defaults for when the role is used standalone (outside of this collection of roles, also called playbook)." msgstr "" #: ../../../docs/faq.md:348 -msgid "I run another webserver on the same server where I wish to install Matrix. What now?" +msgid "then, there are overrides in `group_vars/matrix_servers`, which aim to adjust these \"standalone role defaults\" to something which better fits the playbook in its entirety." msgstr "" #: ../../../docs/faq.md:350 -msgid "By default, we install a webserver for you ([Traefik](https://doc.traefik.io/traefik/)), but you can also use [your own webserver](configuring-playbook-own-webserver.md)." +msgid "finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` file, which is the ultimate override" msgstr "" #: ../../../docs/faq.md:352 -msgid "How is the effective configuration determined?" +msgid "What configuration variables are available?" msgstr "" #: ../../../docs/faq.md:354 -msgid "Configuration variables are defined in multiple places in this playbook and are considered in this order:" +msgid "You can discover the variables you can override in each role (`roles/*/*/defaults/main.yml`)." msgstr "" #: ../../../docs/faq.md:356 -msgid "there are defaults coming from each role's defaults file (`role/matrix*/defaults/main.yml`). These variable values aim to be good defaults for when the role is used standalone (outside of this collection of roles, also called playbook)." +msgid "As described in [How is the effective configuration determined?](#how-is-the-effective-configuration-determined), these role-defaults may be overriden by values defined in `group_vars/matrix_servers`." msgstr "" #: ../../../docs/faq.md:358 -msgid "then, there are overrides in `group_vars/matrix_servers`, which aim to adjust these \"standalone role defaults\" to something which better fits the playbook in its entirety." +msgid "Refer to both of these for inspiration. Still, as mentioned in [Configuring the playbook](configuring-playbook.md), you're only ever supposed to edit your own `inventory/host_vars/matrix.example.com/vars.yml` file and nothing else inside the playbook (unless you're meaning to contribute new features)." msgstr "" -#: ../../../docs/faq.md:360 -msgid "finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` file, which is the ultimate override" +#: ../../../docs/faq.md:360 ../../../docs/faq.md:372 +msgid "**Note**: some of the roles (`roles/galaxy/*`) live in separate repositories and are only installed after your run `just roles` (or `make roles`) or `just update` (which automatically does `git pull` and `just roles`)." msgstr "" #: ../../../docs/faq.md:362 -msgid "What configuration variables are available?" +msgid "I'd like to adjust some configuration which doesn't have a corresponding variable. How do I do it?" msgstr "" #: ../../../docs/faq.md:364 -msgid "You can discover the variables you can override in each role (`roles/*/*/defaults/main.yml`)." +msgid "The playbook doesn't aim to expose all configuration settings for all services using variables. Doing so would amount to hundreds of variables that we have to create and maintain." msgstr "" #: ../../../docs/faq.md:366 -msgid "As described in [How is the effective configuration determined?](#how-is-the-effective-configuration-determined), these role-defaults may be overridden by values defined in `group_vars/matrix_servers`." +msgid "Instead, we only try to make some important basics configurable using dedicated variables you can see in each role. See [What configuration variables are available?](#what-configuration-variables-are-available)." msgstr "" #: ../../../docs/faq.md:368 -msgid "Refer to both of these for inspiration. Still, as mentioned in [Configuring the playbook](configuring-playbook.md), you're only ever supposed to edit your own `inventory/host_vars/matrix.example.com/vars.yml` file and nothing else inside the playbook (unless you're meaning to contribute new features)." -msgstr "" - -#: ../../../docs/faq.md:370 ../../../docs/faq.md:382 -msgid "**Note**: some of the roles (`roles/galaxy/*`) live in separate repositories and are only installed after your run `just roles` (or `make roles`) or `just update` (which automatically does `git pull` and `just roles`)." +msgid "Besides that, each role (component) aims to provide a `matrix_SOME_COMPONENT_configuration_extension_yaml` (or `matrix_SOME_COMPONENT_configuration_extension_json`) variable, which can be used to override the configuration." msgstr "" -#: ../../../docs/faq.md:372 -msgid "I'd like to adjust some configuration which doesn't have a corresponding variable. How do I do it?" +#: ../../../docs/faq.md:370 +msgid "Check each role's `roles/*/*/defaults/main.yml` for the corresponding variable and an example for how use it." msgstr "" #: ../../../docs/faq.md:374 -msgid "The playbook doesn't aim to expose all configuration settings for all services using variables. Doing so would amount to hundreds of variables that we have to create and maintain." +msgid "Installation" msgstr "" #: ../../../docs/faq.md:376 -msgid "Instead, we only try to make some important basics configurable using dedicated variables you can see in each role. See [What configuration variables are available?](#what-configuration-variables-are-available)." +msgid "How do I run the installation?" msgstr "" #: ../../../docs/faq.md:378 -msgid "Besides that, each role (component) aims to provide a `matrix_SOME_COMPONENT_configuration_extension_yaml` (or `matrix_SOME_COMPONENT_configuration_extension_json`) variable, which can be used to override the configuration." +msgid "See [Installing](installing.md) to learn how to use Ansible to install Matrix services." msgstr "" #: ../../../docs/faq.md:380 -msgid "Check each role's `roles/*/*/defaults/main.yml` for the corresponding variable and an example for how use it." +msgid "However, we recommend you to follow our installation guide, instead of jumping straight to installing." +msgstr "" + +#: ../../../docs/faq.md:382 +msgid "There are two guides available:" msgstr "" #: ../../../docs/faq.md:384 -msgid "Installation" +msgid "⚡ **[Quick start](quick-start.md)** (for beginners): this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"." msgstr "" #: ../../../docs/faq.md:386 -msgid "How do I run the installation?" +msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide by starting with the **[Prerequisites](prerequisites.md)** documentation page." msgstr "" #: ../../../docs/faq.md:388 -msgid "See [Installing](installing.md) to learn how to use Ansible to install Matrix services." +msgid "I installed Synapse some other way. Can I migrate such a setup to the playbook?" msgstr "" #: ../../../docs/faq.md:390 -msgid "However, we recommend you to follow our installation guide, instead of jumping straight to installing." +msgid "Yes, you can." msgstr "" #: ../../../docs/faq.md:392 -msgid "There are two guides available:" +msgid "You generally need to do a playbook installation. It's recommended to follow the full installation guide (starting at the [Prerequisites](prerequisites.md) page), not the [Quick start](quick-start.md) guide. The full installation guide will tell you when it's time to import your existing data into the newly-prepared server." msgstr "" #: ../../../docs/faq.md:394 -msgid "⚡ **[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\"." +msgid "This Ansible playbook guides you into installing a server for `example.com` (user IDs are like this: `@alice:example.com`), while the server is at `matrix.example.com`. If your existing setup has a server name (`server_name` configuration setting in Synapse's `homeserver.yaml` file) other than the base `example.com`, you may need to tweak some additional variables. This FAQ entry may be of use if you're dealing with a more complicated setup — [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" msgstr "" #: ../../../docs/faq.md:396 -msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide by starting with the **[Prerequisites](prerequisites.md)** documentation page." +msgid "After configuring the playbook and installing and **before starting** services (done with `ansible-playbook … --tags=start`) you'd import [your SQLite](importing-synapse-sqlite.md) (or [Postgres](importing-postgres.md)) database and also [import your media store](importing-synapse-media-store.md)." msgstr "" #: ../../../docs/faq.md:398 -msgid "I installed Synapse some other way. Can I migrate such a setup to the playbook?" +msgid "I've downloaded Ansible and the playbook on the server. It can't connect using SSH." msgstr "" #: ../../../docs/faq.md:400 -msgid "Yes, you can." +msgid "If you're using the playbook directly on the server, then Ansible doesn't need to connect using SSH." msgstr "" #: ../../../docs/faq.md:402 -msgid "You generally need to do a playbook installation. It's recommended to follow the full installation guide (starting at the [Prerequisites](prerequisites.md) page), not the [Quick start](quick-start.md) guide. The full installation guide will tell you when it's time to import your existing data into the newly-prepared server." +msgid "It can perform a local connection instead. Just set `ansible_connection=local` at the end of the server line in `inventory/hosts` and re-run the playbook." msgstr "" #: ../../../docs/faq.md:404 -msgid "This Ansible playbook guides you into installing a server for `example.com` (user IDs are like this: `@alice:example.com`), while the server is at `matrix.example.com`. If your existing setup has a server name (`server_name` configuration setting in Synapse's `homeserver.yaml` file) other than the base `example.com`, you may need to tweak some additional variables. This FAQ entry may be of use if you're dealing with a more complicated setup — [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" +msgid "If you're running Ansible from within a container (one of the possibilities we list on our [dedicated Ansible documentation page](ansible.md)), then using `ansible_connection=local` is not possible." msgstr "" #: ../../../docs/faq.md:406 -msgid "After configuring the playbook and installing and **before starting** services (done with `ansible-playbook … --tags=start`) you'd import [your SQLite](importing-synapse-sqlite.md) (or [Postgres](importing-postgres.md)) database and also [import your media store](importing-synapse-media-store.md)." +msgid "Troubleshooting" msgstr "" #: ../../../docs/faq.md:408 -msgid "I've downloaded Ansible and the playbook on the server. It can't connect using SSH." +msgid "I get \"Error response from daemon: configured logging driver does not support reading\" when I do `docker logs matrix-synapse`." msgstr "" #: ../../../docs/faq.md:410 -msgid "If you're using the playbook directly on the server, then Ansible doesn't need to connect using SSH." +msgid "See [How can I see the logs?](#how-can-i-see-the-logs)." msgstr "" #: ../../../docs/faq.md:412 -msgid "It can perform a local connection instead. Just set `ansible_connection=local` at the end of the server line in `inventory/hosts` and re-run the playbook." +msgid "How can I see the logs?" msgstr "" #: ../../../docs/faq.md:414 -msgid "If you're running Ansible from within a container (one of the possibilities we list on our [dedicated Ansible documentation page](ansible.md)), then using `ansible_connection=local` is not possible." +msgid "We utilize [systemd/journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html#Description) for logging." msgstr "" #: ../../../docs/faq.md:416 -msgid "Maintenance and Troubleshooting" +msgid "To see logs for Synapse, run `journalctl -fu matrix-synapse.service`. You may wish to see the [manual page for journalctl](https://www.commandlinux.com/man-page/man1/journalctl.1.html)." msgstr "" #: ../../../docs/faq.md:418 -msgid "💡 Also see this page for generic information about maintaining the services and troubleshooting: [Maintenance and Troubleshooting](maintenance-and-troubleshooting.md)" +msgid "Available service names can be seen by doing `ls /etc/systemd/system/matrix*.service` on the server." msgstr "" #: ../../../docs/faq.md:420 -msgid "Do I need to do anything to keep my Matrix server updated?" +msgid "Some services also log to files in `/matrix/*/data/..`, but we're slowly moving away from that." msgstr "" #: ../../../docs/faq.md:422 -msgid "Yes. We don't update anything for you automatically." +msgid "We also disable Docker logging, so you can't use `docker logs matrix-*` either. We do this to prevent useless double (or even triple) logging and to avoid having to rotate log files." msgstr "" #: ../../../docs/faq.md:424 -msgid "See our [documentation page about upgrading services](maintenance-upgrading-services.md)." +msgid "We just simply delegate logging to journald and it takes care of persistence and expiring old data." msgstr "" #: ../../../docs/faq.md:426 -msgid "How do I move my existing installation to another (VM) server?" +msgid "Also see: [How long do systemd/journald logs persist for?](#how-long-do-systemdjournald-logs-persist-for)" msgstr "" #: ../../../docs/faq.md:428 -msgid "If you have an existing installation done using this Ansible playbook, you can easily migrate that to another server following [our dedicated server migration guide](maintenance-migrating.md)." +msgid "How long do systemd/journald logs persist for?" msgstr "" #: ../../../docs/faq.md:430 -msgid "If your previous installation is done in some other way (not using this Ansible playbook), see [I installed Synapse some other way. Can I migrate such a setup to the playbook?](#i-installed-synapse-some-other-way-can-i-migrate-such-a-setup-to-the-playbook)." +msgid "On some distros, the journald logs are just in-memory and not persisted to disk." msgstr "" #: ../../../docs/faq.md:432 -msgid "What is this `/matrix/postgres/data-auto-upgrade-backup` directory that is taking up so much space?" +msgid "Consult (and feel free to adjust) your distro's journald logging configuration in `/etc/systemd/journald.conf`." msgstr "" #: ../../../docs/faq.md:434 -msgid "When you [perform a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql), we save the the old data files in `/matrix/postgres/data-auto-upgrade-backup`, just so you could easily restore them should something have gone wrong." +msgid "To enable persistence and put some limits on how large the journal log files can become, adjust your configuration like this:" msgstr "" -#: ../../../docs/faq.md:436 -msgid "After verifying that everything still works after the Postgres upgrade, you can safely delete `/matrix/postgres/data-auto-upgrade-backup`" +#: ../../../docs/faq.md:445 +msgid "Maintenance" msgstr "" -#: ../../../docs/faq.md:438 -msgid "I get \"Error response from daemon: configured logging driver does not support reading\" when I run `docker logs matrix-synapse`. Why?" +#: ../../../docs/faq.md:447 +msgid "Do I need to do anything to keep my Matrix server updated?" msgstr "" -#: ../../../docs/faq.md:440 -msgid "To prevent double-logging, Docker logging is disabled by explicitly passing `--log-driver=none` to all containers. Due to this, you cannot view logs using `docker logs matrix-*`." +#: ../../../docs/faq.md:449 +msgid "Yes. We don't update anything for you automatically." msgstr "" -#: ../../../docs/faq.md:442 -msgid "See [this section](maintenance-and-troubleshooting.md#how-to-see-the-logs) on the page for maintenance and troubleshooting for more details to see the logs." +#: ../../../docs/faq.md:451 +msgid "See our [documentation page about upgrading services](maintenance-upgrading-services.md)." msgstr "" -#: ../../../docs/faq.md:444 -msgid "The server fails to start due to the `Unable to start service matrix-coturn.service` error. Why and how to solve it?" +#: ../../../docs/faq.md:453 +msgid "How do I move my existing installation to another (VM) server?" msgstr "" -#: ../../../docs/faq.md:446 -msgid "The error is most likely because Traefik cannot obtain SSL certificates due to certain reasons such as wrong domain name configuration or port 80 being unavailable due to other services." +#: ../../../docs/faq.md:455 +msgid "If you have an existing installation done using this Ansible playbook, you can easily migrate that to another server using [our dedicated server migration guide](maintenance-migrating.md)." msgstr "" -#: ../../../docs/faq.md:448 -msgid "If Traefik fails to obtain an SSL certificate for domain names such as `matrix.`, Traefik Certs Dumper cannot extract the SSL certificate out of there, and coturn cannot be started and the error occurs. Refer to these comments for details:" +#: ../../../docs/faq.md:457 +msgid "If your previous installation is done in some other way (not using this Ansible playbook), see [I installed Synapse some other way. Can I migrate such a setup to the playbook?](#i-installed-synapse-some-other-way-can-i-migrate-such-a-setup-to-the-playbook)." msgstr "" -#: ../../../docs/faq.md:450 -msgid "" +#: ../../../docs/faq.md:459 +msgid "How do I back up the data on my server?" msgstr "" -#: ../../../docs/faq.md:451 -msgid "" +#: ../../../docs/faq.md:461 +msgid "We haven't documented this properly yet, but the general advice is to:" msgstr "" -#: ../../../docs/faq.md:453 -msgid "If you are not sure what the problem is, at first make sure that you have set the \"base domain\" (`example.com`, **not `matrix.example.com`**) to `matrix_domain`. You should be able to find it at the top of your `vars.yml`." +#: ../../../docs/faq.md:463 +msgid "back up Postgres by making a database dump. See [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql)" msgstr "" -#: ../../../docs/faq.md:455 -msgid "If it is correctly specified, look Traefik's logs (`journalctl -fu matrix-traefik.service`) for errors by Let's Encrypt for troubleshooting." +#: ../../../docs/faq.md:465 +msgid "back up all `/matrix` files, except for `/matrix/postgres/data` (you already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` (this directory may exist and contain your old data if you've [performed a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql))." msgstr "" -#: ../../../docs/faq.md:457 +#: ../../../docs/faq.md:467 +msgid "You can later restore these by:" +msgstr "" + +#: ../../../docs/faq.md:469 +msgid "Restoring the `/matrix` directory and files on the new server manually" +msgstr "" + +#: ../../../docs/faq.md:470 +msgid "Following the instruction described on [Installing a server into which you'll import old data](installing.md#installing-a-server-into-which-youll-import-old-data)" +msgstr "" + +#: ../../../docs/faq.md:472 +msgid "If your server's IP address has changed, you may need to [set up DNS](configuring-dns.md) again." +msgstr "" + +#: ../../../docs/faq.md:474 +msgid "What is this `/matrix/postgres/data-auto-upgrade-backup` directory that is taking up so much space?" +msgstr "" + +#: ../../../docs/faq.md:476 +msgid "When you [perform a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql), we save the the old data files in `/matrix/postgres/data-auto-upgrade-backup`, just so you could easily restore them should something have gone wrong." +msgstr "" + +#: ../../../docs/faq.md:478 +msgid "After verifying that everything still works after the Postgres upgrade, you can safely delete `/matrix/postgres/data-auto-upgrade-backup`" +msgstr "" + +#: ../../../docs/faq.md:480 +msgid "How do I debug or force SSL certificate renewal?" +msgstr "" + +#: ../../../docs/faq.md:482 +msgid "SSL certificates are managed automatically by the [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server." +msgstr "" + +#: ../../../docs/faq.md:484 +msgid "If you're having trouble with SSL certificate renewal, check the Traefik logs (`journalctl -fu matrix-traefik`)." +msgstr "" + +#: ../../../docs/faq.md:486 +msgid "If you're [using your own webserver](configuring-playbook-own-webserver.md) instead of the integrated one (Traefik), you should investigate in another way." +msgstr "" + +#: ../../../docs/faq.md:488 msgid "Miscellaneous" msgstr "" -#: ../../../docs/faq.md:459 +#: ../../../docs/faq.md:490 msgid "I would like to see this favorite service of mine integrated and become available on my Matrix server. How can I request it?" msgstr "" -#: ../../../docs/faq.md:461 -msgid "You can freely create an issue for feature request on the repository at GitHub [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/new/choose). Note this is a community project with no financial backing, and there is not assurance that your request would be eventually picked up by others and the requested feature would become available. The easiest way to get a feature into this project is to just develop it yourself." +#: ../../../docs/faq.md:492 +msgid "You can freely create an issue for feature request on the repository at GitHub [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/new). Note this is a community project with no financial backing, and there is not assurance that your request would be eventually picked up by others and the requested feature would become available. The easiest way to get a feature into this project is to just develop it yourself." msgstr "" -#: ../../../docs/faq.md:463 +#: ../../../docs/faq.md:494 msgid "Also, please note that this playbook intends to focus solely on Matrix and Matrix-related services. If your request is not specific to Matrix, you may as well to consider to submit it to the [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook), maintained by the members behind this matrix-docker-ansible-deploy project. [This document on the interoperability](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md) describes how to deploy services along with the Matrix services easily." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/getting-the-playbook.po b/i18n/locales/bg/LC_MESSAGES/docs/getting-the-playbook.po index 13ebf0346..f381493e5 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/getting-the-playbook.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/getting-the-playbook.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,68 +19,68 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/getting-the-playbook.md:8 +#: ../../../docs/getting-the-playbook.md:1 msgid "Getting the playbook" msgstr "" -#: ../../../docs/getting-the-playbook.md:10 -msgid "[Prerequisites](prerequisites.md) > [Configuring DNS settings](configuring-dns.md) > Getting the playbook > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)" +#: ../../../docs/getting-the-playbook.md:3 +msgid "[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > Getting the playbook > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)" msgstr "" -#: ../../../docs/getting-the-playbook.md:12 +#: ../../../docs/getting-the-playbook.md:5 msgid "This Ansible playbook is meant to be executed on your own computer (not the Matrix server)." msgstr "" -#: ../../../docs/getting-the-playbook.md:14 +#: ../../../docs/getting-the-playbook.md:7 msgid "In special cases (if your computer cannot run Ansible, etc.) you may put the playbook on the server as well." msgstr "" -#: ../../../docs/getting-the-playbook.md:16 +#: ../../../docs/getting-the-playbook.md:9 msgid "You can retrieve the playbook's source code by:" msgstr "" -#: ../../../docs/getting-the-playbook.md:17 +#: ../../../docs/getting-the-playbook.md:11 msgid "[Using git to get the playbook](#using-git-to-get-the-playbook) (recommended)" msgstr "" -#: ../../../docs/getting-the-playbook.md:18 +#: ../../../docs/getting-the-playbook.md:13 msgid "[Downloading the playbook as a ZIP archive](#downloading-the-playbook-as-a-zip-archive) (not recommended)" msgstr "" -#: ../../../docs/getting-the-playbook.md:20 +#: ../../../docs/getting-the-playbook.md:15 msgid "Using git to get the playbook" msgstr "" -#: ../../../docs/getting-the-playbook.md:22 +#: ../../../docs/getting-the-playbook.md:17 msgid "We recommend using the [git](https://git-scm.com/) tool to get the playbook's source code, because it lets you easily keep up to date in the future when [Maintaining services](maintenance-upgrading-services.md)." msgstr "" -#: ../../../docs/getting-the-playbook.md:24 +#: ../../../docs/getting-the-playbook.md:19 msgid "Once you've installed git on your computer, you can go to any directory of your choosing and run the following command to retrieve the playbook's source code:" msgstr "" -#: ../../../docs/getting-the-playbook.md:30 +#: ../../../docs/getting-the-playbook.md:25 msgid "This will create a new `matrix-docker-ansible-deploy` directory. You're supposed to execute all other installation commands inside that directory." msgstr "" -#: ../../../docs/getting-the-playbook.md:32 +#: ../../../docs/getting-the-playbook.md:27 msgid "Downloading the playbook as a ZIP archive" msgstr "" -#: ../../../docs/getting-the-playbook.md:34 +#: ../../../docs/getting-the-playbook.md:29 msgid "Alternatively, you can download the playbook as a ZIP archive. This is not recommended, as it's not easy to keep up to date with future updates. We suggest you [use git](#using-git-to-get-the-playbook) instead." msgstr "" -#: ../../../docs/getting-the-playbook.md:36 +#: ../../../docs/getting-the-playbook.md:31 msgid "The latest version is always at the following URL: https://github.com/spantaleev/matrix-docker-ansible-deploy/archive/master.zip" msgstr "" -#: ../../../docs/getting-the-playbook.md:38 +#: ../../../docs/getting-the-playbook.md:33 msgid "You can extract this archive anywhere. You'll get a directory called `matrix-docker-ansible-deploy-master`. You're supposed to execute all other installation commands inside that directory." msgstr "" -#: ../../../docs/getting-the-playbook.md:42 +#: ../../../docs/getting-the-playbook.md:37 msgid "[▶️](configuring-playbook.md) No matter which method you've used to download the playbook, you can proceed by [Configuring the playbook](configuring-playbook.md)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/howto-srv-server-delegation.po b/i18n/locales/bg/LC_MESSAGES/docs/howto-srv-server-delegation.po index d945de448..8a38862f9 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/howto-srv-server-delegation.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/howto-srv-server-delegation.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,132 +19,132 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/howto-srv-server-delegation.md:9 +#: ../../../docs/howto-srv-server-delegation.md:1 msgid "Server Delegation via a DNS SRV record (advanced)" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:11 +#: ../../../docs/howto-srv-server-delegation.md:3 msgid "**Reminder** : unless you are affected by the [Downsides of well-known-based Server Delegation](howto-server-delegation.md#downsides-of-well-known-based-server-delegation), we suggest you **stay on the simple/default path**: [Server Delegation](howto-server-delegation.md) by [configuring well-known files](configuring-well-known.md) at the base domain." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:13 +#: ../../../docs/howto-srv-server-delegation.md:5 msgid "This guide is about configuring Server Delegation using DNS SRV records (for the [Traefik](https://doc.traefik.io/traefik/) webserver). This method has special requirements when it comes to SSL certificates, so various changes are required." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:15 +#: ../../../docs/howto-srv-server-delegation.md:7 msgid "Prerequisites" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:17 +#: ../../../docs/howto-srv-server-delegation.md:9 msgid "SRV delegation while still using the playbook provided Traefik to get / renew the certificate requires a wildcard certificate." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:19 +#: ../../../docs/howto-srv-server-delegation.md:11 msgid "To obtain / renew one from [Let's Encrypt](https://letsencrypt.org/), one needs to use a [DNS-01 challenge](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) method instead of the default [HTTP-01](https://letsencrypt.org/docs/challenge-types/#http-01-challenge)." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:21 +#: ../../../docs/howto-srv-server-delegation.md:13 msgid "This means that this is **limited to the list of DNS providers supported by Traefik**, unless you bring in your own certificate." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:23 +#: ../../../docs/howto-srv-server-delegation.md:15 msgid "The up-to-date list can be accessed on [traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers)" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:25 +#: ../../../docs/howto-srv-server-delegation.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:27 +#: ../../../docs/howto-srv-server-delegation.md:19 msgid "**Note**: the changes below instruct you how to do this for a basic Synapse installation. You will need to adapt the variable name and the content of the labels:" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:29 -msgid "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))" +#: ../../../docs/howto-srv-server-delegation.md:21 +msgid "if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md), [conduwuit](./configuring-playbook-conduwuit.md) or [Dendrite](./configuring-playbook-dendrite.md))" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:30 +#: ../../../docs/howto-srv-server-delegation.md:22 msgid "if you're using [Synapse with workers enabled](./configuring-playbook-synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled: true`). In that case, it's actually the `matrix-synapse-reverse-proxy-companion` service which has Traefik labels attached" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:32 +#: ../../../docs/howto-srv-server-delegation.md:24 msgid "Also, all instructions below are from an older version of the playbook and may not work anymore." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:34 +#: ../../../docs/howto-srv-server-delegation.md:26 msgid "Federation Endpoint" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:41 +#: ../../../docs/howto-srv-server-delegation.md:33 msgid "This is because with SRV federation, some servers / tools (one of which being the federation tester) try to access the federation API using the resolved IP address instead of the domain name (or they are not using SNI). This change will make Traefik route all traffic for which the path match this rule go to the federation endpoint." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:43 +#: ../../../docs/howto-srv-server-delegation.md:35 msgid "Tell Traefik which certificate to serve for the federation endpoint" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:45 -msgid "Now that the federation endpoint is not bound to a domain anymore we need to explicitly tell Traefik to use a wildcard certificate in addition to one containing the base name." +#: ../../../docs/howto-srv-server-delegation.md:37 +msgid "Now that the federation endpoint is not bound to a domain anymore we need to explicitely tell Traefik to use a wildcard certificate in addition to one containing the base name." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:47 +#: ../../../docs/howto-srv-server-delegation.md:39 msgid "This is because the Matrix specification expects the federation endpoint to be served using a certificate compatible with the base domain, however, the other resources on the endpoint still need a valid certificate to work." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:56 +#: ../../../docs/howto-srv-server-delegation.md:48 msgid "Configure the DNS-01 challenge for let's encrypt" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:58 +#: ../../../docs/howto-srv-server-delegation.md:50 msgid "Since we're now requesting a wildcard certificate, we need to change the ACME challenge method. To request a wildcard certificate from Let's Encrypt we are required to use the DNS-01 challenge." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:60 +#: ../../../docs/howto-srv-server-delegation.md:52 msgid "This will need 3 changes:" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:61 +#: ../../../docs/howto-srv-server-delegation.md:53 msgid "Add a new certificate resolver that works with DNS-01" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:62 +#: ../../../docs/howto-srv-server-delegation.md:54 msgid "Configure the resolver to allow access to the DNS zone to configure the records to answer the challenge (refer to [Traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers) to know which environment variables to set)" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:63 +#: ../../../docs/howto-srv-server-delegation.md:55 msgid "Tell the playbook to use the new resolver as default" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:65 +#: ../../../docs/howto-srv-server-delegation.md:57 msgid "We cannot just disable the default resolver as that would disable SSL in quite a few places in the playbook." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:93 +#: ../../../docs/howto-srv-server-delegation.md:86 msgid "Adjust coturn's configuration" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:95 +#: ../../../docs/howto-srv-server-delegation.md:88 msgid "The last step is to alter the generated coturn configuration." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:97 +#: ../../../docs/howto-srv-server-delegation.md:90 msgid "By default, coturn is configured to wait on the certificate for the `matrix.` subdomain using an [instantiated systemd service](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Service%20Templates) using the domain name as the parameter for this service. However, we need to serve the wildcard certificate, which is incompatible with systemd, it will try to expand the `*`, which will break and prevent coturn from starting." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:99 +#: ../../../docs/howto-srv-server-delegation.md:92 msgid "We also need to indicate to coturn where the wildcard certificate is." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:101 +#: ../../../docs/howto-srv-server-delegation.md:94 msgid "⚠️ **Warning** : On first start of the services, coturn might still fail to start because Traefik is still in the process of obtaining the certificates. If you still get an error, make sure Traefik obtained the certificates and restart the coturn service (`just start-group coturn`)." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:103 +#: ../../../docs/howto-srv-server-delegation.md:96 msgid "This should not happen again afterwards as Traefik will renew certificates well before their expiry date, and the coturn service is setup to restart periodically." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:129 +#: ../../../docs/howto-srv-server-delegation.md:122 msgid "Full example of a working configuration" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/importing-postgres.po b/i18n/locales/bg/LC_MESSAGES/docs/importing-postgres.po index 911ae7a3f..38bac600c 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/importing-postgres.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/importing-postgres.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,141 +19,132 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/importing-postgres.md:10 +#: ../../../docs/importing-postgres.md:1 msgid "Importing an existing Postgres database from another installation (optional)" msgstr "" -#: ../../../docs/importing-postgres.md:12 -msgid "You can manually import your database from a previous default installation of Synapse." -msgstr "" - -#: ../../../docs/importing-postgres.md:14 -#: ../../../docs/importing-postgres.md:38 -msgid "**Notes**:" -msgstr "" - -#: ../../../docs/importing-postgres.md:15 -msgid "Don't forget to import your Synapse `media_store` files as well — see [the importing-synapse-media-store guide](importing-synapse-media-store.md) for more details." +#: ../../../docs/importing-postgres.md:3 +msgid "Run this if you'd like to import your database from a previous installation. (don't forget to import your Synapse `media_store` files as well — see [the importing-synape-media-store guide](importing-synapse-media-store.md))." msgstr "" -#: ../../../docs/importing-postgres.md:16 -msgid "If you have an existing installation done using this Ansible playbook, you can easily migrate that to another server following [our dedicated server migration guide](maintenance-migrating.md)." -msgstr "" - -#: ../../../docs/importing-postgres.md:18 +#: ../../../docs/importing-postgres.md:6 msgid "Prerequisites" msgstr "" -#: ../../../docs/importing-postgres.md:20 +#: ../../../docs/importing-postgres.md:8 msgid "For this to work, **the database name in Postgres must match** what this playbook uses. This playbook uses a Postgres database name of `synapse` by default (controlled by the `matrix_synapse_database_database` variable). If your database name differs, be sure to change `matrix_synapse_database_database` to your desired name and to re-run the playbook before proceeding." msgstr "" -#: ../../../docs/importing-postgres.md:22 +#: ../../../docs/importing-postgres.md:10 msgid "The playbook supports importing Postgres dump files in **text** (e.g. `pg_dump > dump.sql`) or **gzipped** formats (e.g. `pg_dump | gzip -c > dump.sql.gz`). Importing multiple databases (as dumped by `pg_dumpall`) is also supported." msgstr "" -#: ../../../docs/importing-postgres.md:24 +#: ../../../docs/importing-postgres.md:12 msgid "The migration might be a good moment, to \"reset\" a not properly working bridge. Be aware, that it might affect all users (new link to bridge, new rooms, …)" msgstr "" -#: ../../../docs/importing-postgres.md:26 +#: ../../../docs/importing-postgres.md:14 msgid "Before doing the actual import, **you need to upload your Postgres dump file to the server** (any path is okay)." msgstr "" -#: ../../../docs/importing-postgres.md:28 +#: ../../../docs/importing-postgres.md:16 msgid "Importing" msgstr "" -#: ../../../docs/importing-postgres.md:30 +#: ../../../docs/importing-postgres.md:18 msgid "To import, run this command (make sure to replace `SERVER_PATH_TO_POSTGRES_DUMP_FILE` with a file path on your server):" msgstr "" -#: ../../../docs/importing-postgres.md:40 +#: ../../../docs/importing-postgres.md:26 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/importing-postgres.md:28 msgid "`SERVER_PATH_TO_POSTGRES_DUMP_FILE` must be a file path to a Postgres dump file on the server (not on your local machine!)" msgstr "" -#: ../../../docs/importing-postgres.md:41 +#: ../../../docs/importing-postgres.md:29 msgid "`postgres_default_import_database` defaults to `matrix`, which is useful for importing multiple databases (for dumps made with `pg_dumpall`). If you're importing a single database (e.g. `synapse`), consider changing `postgres_default_import_database` accordingly" msgstr "" -#: ../../../docs/importing-postgres.md:42 +#: ../../../docs/importing-postgres.md:30 msgid "after importing a large database, it's a good idea to run [an `ANALYZE` operation](https://www.postgresql.org/docs/current/sql-analyze.html) to make Postgres rebuild its database statistics and optimize its query planner. You can easily do this via the playbook by running `just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze` (see [Vacuuming PostgreSQL](maintenance-postgres.md#vacuuming-postgresql) for more details)." msgstr "" -#: ../../../docs/importing-postgres.md:44 +#: ../../../docs/importing-postgres.md:32 msgid "Troubleshooting" msgstr "" -#: ../../../docs/importing-postgres.md:46 +#: ../../../docs/importing-postgres.md:34 msgid "Table Ownership" msgstr "" -#: ../../../docs/importing-postgres.md:48 +#: ../../../docs/importing-postgres.md:36 msgid "A table ownership issue can occur if you are importing from a Synapse installation which was both:" msgstr "" -#: ../../../docs/importing-postgres.md:50 +#: ../../../docs/importing-postgres.md:38 msgid "migrated from SQLite to Postgres, and" msgstr "" -#: ../../../docs/importing-postgres.md:51 +#: ../../../docs/importing-postgres.md:39 msgid "used a username other than 'synapse'" msgstr "" -#: ../../../docs/importing-postgres.md:53 +#: ../../../docs/importing-postgres.md:41 msgid "In this case you may run into the following error during the import task:" msgstr "" -#: ../../../docs/importing-postgres.md:59 +#: ../../../docs/importing-postgres.md:47 msgid "where `synapse_user` is the database username from the previous Synapse installation." msgstr "" -#: ../../../docs/importing-postgres.md:61 +#: ../../../docs/importing-postgres.md:49 msgid "This can be verified by examining the dump for ALTER TABLE statements which set OWNER TO that username:" msgstr "" -#: ../../../docs/importing-postgres.md:73 +#: ../../../docs/importing-postgres.md:61 msgid "It can be worked around by changing the username to `synapse`, for example by using `sed`:" msgstr "" -#: ../../../docs/importing-postgres.md:79 +#: ../../../docs/importing-postgres.md:67 msgid "This uses sed to perform an 'in-place' (`-i`) replacement globally (`/g`), searching for `synapse_user` and replacing with `synapse` (`s/synapse_user/synapse`). If your database username was different, change `synapse_user` to that username instead. Expand search/replace statement as shown in example above, in case of old user name like `matrix` — replacing `matrix` only would… well — you can imagine." msgstr "" -#: ../../../docs/importing-postgres.md:81 +#: ../../../docs/importing-postgres.md:69 msgid "Note that if the previous import failed with an error it may have made changes which are incompatible with re-running the import task right away; if you do so it may fail with an error such as:" msgstr "" -#: ../../../docs/importing-postgres.md:87 +#: ../../../docs/importing-postgres.md:75 msgid "Repeat import" msgstr "" -#: ../../../docs/importing-postgres.md:89 +#: ../../../docs/importing-postgres.md:77 msgid "In this case you can use the command suggested in the import task to clear the database before retrying the import:" msgstr "" -#: ../../../docs/importing-postgres.md:97 +#: ../../../docs/importing-postgres.md:85 msgid "Now on your local machine run `just run-tags setup-postgres` to prepare the database roles etc." msgstr "" -#: ../../../docs/importing-postgres.md:99 +#: ../../../docs/importing-postgres.md:87 msgid "If not, you probably get this error. `synapse` is the correct table owner, but the role is missing in database." msgstr "" -#: ../../../docs/importing-postgres.md:105 +#: ../../../docs/importing-postgres.md:93 msgid "Once the database is clear and the ownership of the tables has been fixed in the SQL file, the import task should succeed." msgstr "" -#: ../../../docs/importing-postgres.md:107 +#: ../../../docs/importing-postgres.md:95 msgid "Check, if `--dbname` is set to `synapse` (not `matrix`) and replace paths (or even better, copy this line from your terminal)" msgstr "" -#: ../../../docs/importing-postgres.md:113 +#: ../../../docs/importing-postgres.md:101 msgid "Hints" msgstr "" -#: ../../../docs/importing-postgres.md:115 +#: ../../../docs/importing-postgres.md:103 msgid "To open psql terminal run `/matrix/postgres/bin/cli`" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-media-store.po b/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-media-store.po index 1cecde157..345710043 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-media-store.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-media-store.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,44 +19,44 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/importing-synapse-media-store.md:8 +#: ../../../docs/importing-synapse-media-store.md:1 msgid "Importing `media_store` data files from an existing Synapse installation (optional)" msgstr "" -#: ../../../docs/importing-synapse-media-store.md:10 -msgid "You can manually import your `media_store` files from a previous installation of Synapse." +#: ../../../docs/importing-synapse-media-store.md:3 +msgid "Run this if you'd like to import your `media_store` files from a previous installation of Synapse." msgstr "" -#: ../../../docs/importing-synapse-media-store.md:12 +#: ../../../docs/importing-synapse-media-store.md:5 msgid "Prerequisites" msgstr "" -#: ../../../docs/importing-synapse-media-store.md:14 +#: ../../../docs/importing-synapse-media-store.md:7 msgid "Before doing the actual data restore, **you need to upload your media store directory to the server** (any path is okay)." msgstr "" -#: ../../../docs/importing-synapse-media-store.md:16 +#: ../../../docs/importing-synapse-media-store.md:9 msgid "If you are [storing Matrix media files on Amazon S3](configuring-playbook-s3.md) (optional), restoring with this tool is not possible right now." msgstr "" -#: ../../../docs/importing-synapse-media-store.md:18 +#: ../../../docs/importing-synapse-media-store.md:11 msgid "As an alternative, you can perform a manual restore using the [AWS CLI tool](https://aws.amazon.com/cli/) (e.g. `aws s3 sync /path/to/server/media_store/. s3://name-of-bucket/`)" msgstr "" -#: ../../../docs/importing-synapse-media-store.md:20 +#: ../../../docs/importing-synapse-media-store.md:13 msgid "**Note for Mac users**: Due to case-sensitivity issues on certain Mac filesystems (HFS or HFS+), filename corruption may occur if you copy a `media_store` directory to your Mac. If you're transferring a `media_store` directory between 2 servers, make sure you do it directly (from server to server with a tool such as [rsync](https://rsync.samba.org/)), and not by downloading the files to your Mac." msgstr "" -#: ../../../docs/importing-synapse-media-store.md:22 +#: ../../../docs/importing-synapse-media-store.md:15 msgid "Importing" msgstr "" -#: ../../../docs/importing-synapse-media-store.md:24 +#: ../../../docs/importing-synapse-media-store.md:17 msgid "Run this command (make sure to replace `` with a path on your server):" msgstr "" -#: ../../../docs/importing-synapse-media-store.md:30 +#: ../../../docs/importing-synapse-media-store.md:23 msgid "**Note**: `` must be a file path to a `media_store` directory on the server (not on your local machine!)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-sqlite.po b/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-sqlite.po index 94306422a..a17efdad4 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-sqlite.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-sqlite.po @@ -8,71 +8,67 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2026-02-13 10:32+0000\n" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/importing-synapse-sqlite.md:9 +#: ../../../docs/importing-synapse-sqlite.md:1 msgid "Importing an existing SQLite database from another Synapse installation (optional)" msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:11 -msgid "You can manually import your database from a previous default installation of Synapse." +#: ../../../docs/importing-synapse-sqlite.md:3 +msgid "Run this if you'd like to import your database from a previous default installation of Synapse (don't forget to import your `media_store` files as well — see [the importing-synapse-media-store guide](importing-synapse-media-store.md))." msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:13 +#: ../../../docs/importing-synapse-sqlite.md:5 msgid "While this playbook only supports running Synapse in combination with PostgreSQL, a Synapse instance installed manually usually defaults to using an SQLite database." msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:15 +#: ../../../docs/importing-synapse-sqlite.md:7 msgid "If you have such a Synapse setup and wish to migrate it to one managed by the playbook (and over to PostgreSQL), this documentation page is for you." msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:17 -msgid "**Note**: don't forget to import your Synapse `media_store` files as well — see [the importing-synapse-media-store guide](importing-synapse-media-store.md) for more details." -msgstr "" - -#: ../../../docs/importing-synapse-sqlite.md:19 +#: ../../../docs/importing-synapse-sqlite.md:9 msgid "Prerequisites" msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:21 +#: ../../../docs/importing-synapse-sqlite.md:11 msgid "Before doing the actual import:" msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:23 +#: ../../../docs/importing-synapse-sqlite.md:13 msgid "**ensure you have NOT started Synapse yet**. That is, make sure you have followed the [Installing step](installing.md), but haven't run the playbook's `start` tag yet. If you had started your new Synapse instance, it may have already initialized your Postgres database and importing onto it may not work. In such cases, you may need to clean up the `synapse` database first." msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:24 +#: ../../../docs/importing-synapse-sqlite.md:14 msgid "**ensure you have uploaded your SQLite database file to the server** (any path is okay)" msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:25 +#: ../../../docs/importing-synapse-sqlite.md:15 msgid "if you're using the integrated Postgres server (**by default, you are** using it, unless you've explicitly switched to [Using an external PostgreSQL server](configuring-playbook-external-postgres.md)), **make sure Postgres is started** by running `just start-group postgres`" msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:27 +#: ../../../docs/importing-synapse-sqlite.md:17 msgid "Importing" msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:29 +#: ../../../docs/importing-synapse-sqlite.md:19 msgid "Run this command (make sure to replace `` with a file path on your server):" msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:35 +#: ../../../docs/importing-synapse-sqlite.md:25 msgid "**Notes**:" msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:37 +#: ../../../docs/importing-synapse-sqlite.md:27 msgid "`` must be replaced with a file path to a `homeserver.db` **file on the server** (not on your local machine!)." msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:38 +#: ../../../docs/importing-synapse-sqlite.md:28 msgid "if the SQLite database is from an older version of Synapse, the **importing procedure may run migrations on it to bring it up to date**. That is, your SQLite database file may get modified and become unusable with your older Synapse version. Keeping a copy of the original is probably wise." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/installing.po b/i18n/locales/bg/LC_MESSAGES/docs/installing.po index f9b6010d6..b2e838185 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/installing.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/installing.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,296 +19,288 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/installing.md:15 +#: ../../../docs/installing.md:1 msgid "Installing" msgstr "" -#: ../../../docs/installing.md:17 -msgid "[Prerequisites](prerequisites.md) > [Configuring DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > Installing" +#: ../../../docs/installing.md:3 +msgid "[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > Installing" msgstr "" -#: ../../../docs/installing.md:19 +#: ../../../docs/installing.md:5 msgid "If you've configured your DNS records and the playbook, you can start the installation procedure." msgstr "" -#: ../../../docs/installing.md:21 +#: ../../../docs/installing.md:7 msgid "Update Ansible roles" msgstr "" -#: ../../../docs/installing.md:23 +#: ../../../docs/installing.md:9 msgid "Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside." msgstr "" -#: ../../../docs/installing.md:25 +#: ../../../docs/installing.md:11 msgid "To update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file), run:" msgstr "" -#: ../../../docs/installing.md:27 +#: ../../../docs/installing.md:13 msgid "either: `just update`" msgstr "" -#: ../../../docs/installing.md:28 +#: ../../../docs/installing.md:14 msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)" msgstr "" -#: ../../../docs/installing.md:30 +#: ../../../docs/installing.md:16 msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`" msgstr "" -#: ../../../docs/installing.md:32 +#: ../../../docs/installing.md:18 msgid "For details about `just` commands, take a look at: [Running `just` commands](just.md)." msgstr "" -#: ../../../docs/installing.md:34 +#: ../../../docs/installing.md:20 msgid "Install Matrix server and services" msgstr "" -#: ../../../docs/installing.md:36 +#: ../../../docs/installing.md:22 msgid "The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks." msgstr "" -#: ../../../docs/installing.md:38 +#: ../../../docs/installing.md:24 msgid "The general command syntax for installation (and also maintenance) is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`. It is recommended to get yourself familiar with the [playbook tags](playbook-tags.md) before proceeding." msgstr "" -#: ../../../docs/installing.md:40 +#: ../../../docs/installing.md:26 msgid "If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the all Ansible commands." msgstr "" -#: ../../../docs/installing.md:42 +#: ../../../docs/installing.md:28 msgid "If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to all Ansible commands." msgstr "" -#: ../../../docs/installing.md:44 +#: ../../../docs/installing.md:30 msgid "There 2 ways to start the installation process — depending on whether you're [Installing a brand new server (without importing data)](#installing-a-brand-new-server-without-importing-data) or [Installing a server into which you'll import old data](#installing-a-server-into-which-youll-import-old-data)." msgstr "" -#: ../../../docs/installing.md:46 +#: ../../../docs/installing.md:32 msgid "**Note**: if you are migrating from an old server to a new one, take a look at [this guide](maintenance-migrating.md) instead. This is an easier and more straightforward way than installing a server and importing old data into it." msgstr "" -#: ../../../docs/installing.md:48 +#: ../../../docs/installing.md:34 msgid "Installing a brand new server (without importing data)" msgstr "" -#: ../../../docs/installing.md:50 +#: ../../../docs/installing.md:36 msgid "If this is **a brand new** Matrix server and you **won't be importing old data into it**, run all these tags:" msgstr "" -#: ../../../docs/installing.md:56 +#: ../../../docs/installing.md:42 msgid "This will do a full installation and start all Matrix services." msgstr "" -#: ../../../docs/installing.md:58 +#: ../../../docs/installing.md:44 msgid "**Note**: if the command does not work as expected, make sure that you have properly installed and configured software required to run the playbook, as described on [Prerequisites](prerequisites.md)." msgstr "" -#: ../../../docs/installing.md:60 +#: ../../../docs/installing.md:46 msgid "Installing a server into which you'll import old data" msgstr "" -#: ../../../docs/installing.md:62 +#: ../../../docs/installing.md:48 msgid "If you will be importing data into your newly created Matrix server, install it, but **do not** start its services just yet. Starting its services or messing with its database now will affect your data import later on." msgstr "" -#: ../../../docs/installing.md:64 +#: ../../../docs/installing.md:50 msgid "To do the installation **without** starting services, run `ansible-playbook` with the `install-all` tag only:" msgstr "" -#: ../../../docs/installing.md:70 +#: ../../../docs/installing.md:56 msgid "[!WARNING] Do not run the just \"recipe\" `just install-all` instead, because it automatically starts services at the end of execution. See: [Difference between playbook tags and shortcuts](just.md#difference-between-playbook-tags-and-shortcuts)" msgstr "" -#: ../../../docs/installing.md:73 +#: ../../../docs/installing.md:59 msgid "When this command completes, services won't be running yet." msgstr "" -#: ../../../docs/installing.md:75 +#: ../../../docs/installing.md:61 msgid "You can now:" msgstr "" -#: ../../../docs/installing.md:77 +#: ../../../docs/installing.md:63 msgid "[Importing an existing SQLite database (from another Synapse installation)](importing-synapse-sqlite.md) (optional)" msgstr "" -#: ../../../docs/installing.md:79 +#: ../../../docs/installing.md:65 msgid "[Importing an existing Postgres database (from another installation)](importing-postgres.md) (optional)" msgstr "" -#: ../../../docs/installing.md:81 +#: ../../../docs/installing.md:67 msgid "[Importing `media_store` data files from an existing Synapse installation](importing-synapse-media-store.md) (optional)" msgstr "" -#: ../../../docs/installing.md:83 +#: ../../../docs/installing.md:69 msgid "… and then proceed to starting all services:" msgstr "" -#: ../../../docs/installing.md:89 +#: ../../../docs/installing.md:75 msgid "Create your user account" msgstr "" -#: ../../../docs/installing.md:91 +#: ../../../docs/installing.md:77 msgid "ℹ️ *You can skip this step if you have installed a server and imported old data to it.*" msgstr "" -#: ../../../docs/installing.md:93 +#: ../../../docs/installing.md:79 msgid "As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server." msgstr "" -#: ../../../docs/installing.md:95 +#: ../../../docs/installing.md:81 msgid "After creating the user account, you can log in to it with [Element Web](configuring-playbook-client-element-web.md) that this playbook has installed for you at this URL: `https://element.example.com/`." msgstr "" -#: ../../../docs/installing.md:97 +#: ../../../docs/installing.md:83 msgid "To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer." msgstr "" -#: ../../../docs/installing.md:99 +#: ../../../docs/installing.md:85 msgid "**Notes**:" msgstr "" -#: ../../../docs/installing.md:100 +#: ../../../docs/installing.md:86 msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`" msgstr "" -#: ../../../docs/installing.md:101 +#: ../../../docs/installing.md:87 msgid "For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)" msgstr "" -#: ../../../docs/installing.md:102 +#: ../../../docs/installing.md:88 msgid "Use `admin=yes` to make your user account an administrator of the Matrix server" msgstr "" -#: ../../../docs/installing.md:110 +#: ../../../docs/installing.md:96 msgid "Feel free to create as many accounts (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your account only (with `admin=yes`), and others should be created with `admin=no`." msgstr "" -#: ../../../docs/installing.md:112 +#: ../../../docs/installing.md:98 msgid "For more information, see the documentation for [registering users](registering-users.md)." msgstr "" -#: ../../../docs/installing.md:114 +#: ../../../docs/installing.md:100 msgid "Finalize the installation" msgstr "" -#: ../../../docs/installing.md:116 +#: ../../../docs/installing.md:102 msgid "Now you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network." msgstr "" -#: ../../../docs/installing.md:118 +#: ../../../docs/installing.md:104 msgid "This is required for federation to work! Without a proper configuration, your server will effectively not be part of the Matrix network." msgstr "" -#: ../../../docs/installing.md:120 +#: ../../../docs/installing.md:106 msgid "To configure the delegation, you have these two options. Choose one of them according to your situation." msgstr "" -#: ../../../docs/installing.md:122 +#: ../../../docs/installing.md:108 msgid "If you can afford to point the base domain at the Matrix server, follow the instructions below which guide you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server. It will enable you to use a Matrix user ID like `@alice:example.com` while hosting services on a subdomain like `matrix.example.com`." msgstr "" -#: ../../../docs/installing.md:123 +#: ../../../docs/installing.md:109 msgid "Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot \"serve the base domain\" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server), but feel free to familiarize yourself with all [server delegation (redirection) options](howto-server-delegation.md)." msgstr "" -#: ../../../docs/installing.md:125 +#: ../../../docs/installing.md:111 msgid "To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/installing.md:131 +#: ../../../docs/installing.md:117 msgid "After configuring the playbook, run the command below:" msgstr "" -#: ../../../docs/installing.md:137 -msgid "**If an error is not returned, the installation has completed and the services have been started successfully**🎉" -msgstr "" - -#: ../../../docs/installing.md:139 +#: ../../../docs/installing.md:123 msgid "Things to do next" msgstr "" -#: ../../../docs/installing.md:141 -msgid "After completing the installation, you can:" +#: ../../../docs/installing.md:125 +msgid "After finilizing the installation, you can:" msgstr "" -#: ../../../docs/installing.md:143 -msgid "[check if services work](maintenance-and-troubleshooting.md#how-to-check-if-services-work)" +#: ../../../docs/installing.md:127 +msgid "[check if services work](maintenance-checking-services.md)" msgstr "" -#: ../../../docs/installing.md:144 +#: ../../../docs/installing.md:128 msgid "or [set up additional services](configuring-playbook.md#other-configuration-options) (bridges to other chat networks, bots, etc.)" msgstr "" -#: ../../../docs/installing.md:145 +#: ../../../docs/installing.md:129 msgid "or learn how to [upgrade services when new versions are released](maintenance-upgrading-services.md)" msgstr "" -#: ../../../docs/installing.md:146 +#: ../../../docs/installing.md:130 msgid "or learn how to [maintain your server](faq.md#maintenance)" msgstr "" -#: ../../../docs/installing.md:147 +#: ../../../docs/installing.md:131 msgid "or join some Matrix rooms:" msgstr "" -#: ../../../docs/installing.md:148 -msgid "via the *Explore rooms* feature in Element Web or some other clients, or by discovering them using this [matrix-static list](https://view.matrix.org). **Note**: joining large rooms may overload small servers. For tuning guidance on constrained hosts, see [Limit joining heavy rooms on constrained hosts](configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts)." +#: ../../../docs/installing.md:132 +msgid "via the *Explore rooms* feature in Element Web or some other clients, or by discovering them using this [matrix-static list](https://view.matrix.org). **Note**: joining large rooms may overload small servers." msgstr "" -#: ../../../docs/installing.md:150 +#: ../../../docs/installing.md:133 msgid "or come say Hi in our support room — [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting." msgstr "" -#: ../../../docs/installing.md:151 +#: ../../../docs/installing.md:134 msgid "or help make this playbook better by contributing (code, documentation, or [coffee/beer](https://liberapay.com/s.pantaleev/donate))" msgstr "" -#: ../../../docs/installing.md:153 -msgid "⚠️ Keep the playbook and services up-to-date" +#: ../../../docs/installing.md:136 +msgid "Maintaining your setup in the future" msgstr "" -#: ../../../docs/installing.md:155 +#: ../../../docs/installing.md:138 msgid "While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**." msgstr "" -#: ../../../docs/installing.md:157 +#: ../../../docs/installing.md:140 msgid "The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities." msgstr "" -#: ../../../docs/installing.md:159 +#: ../../../docs/installing.md:142 msgid "Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date." msgstr "" -#: ../../../docs/installing.md:161 -msgid "Also, do not forget to update your system regularly. While this playbook may install basic services, such as Docker, it will not interfere further with system maintenance. Keeping the system itself up-to-date is out of scope for this playbook." -msgstr "" - -#: ../../../docs/installing.md:163 -msgid "For more information about upgrading or maintaining services with the playbook, take a look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)" +#: ../../../docs/installing.md:144 +msgid "For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)" msgstr "" -#: ../../../docs/installing.md:165 +#: ../../../docs/installing.md:146 msgid "Feel free to **re-run the setup command any time** you think something is wrong with the server configuration. Ansible will take your configuration and update your server to match." msgstr "" -#: ../../../docs/installing.md:171 +#: ../../../docs/installing.md:152 msgid "**Note**: see [this page on the playbook tags](playbook-tags.md) for more information about those tags." msgstr "" -#: ../../../docs/installing.md:173 +#: ../../../docs/installing.md:154 msgid "Make full use of `just` shortcut commands" msgstr "" -#: ../../../docs/installing.md:175 +#: ../../../docs/installing.md:156 msgid "After you get familiar with reconfiguring and re-running the playbook to maintain the server, upgrade its services, etc., you probably would like to make use of `just` shortcut commands for faster input." msgstr "" -#: ../../../docs/installing.md:177 +#: ../../../docs/installing.md:158 msgid "For example, `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/installing.md:179 +#: ../../../docs/installing.md:160 msgid "You can learn about the shortcut commands on this page: [Running `just` commands](just.md)" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/just.po b/i18n/locales/bg/LC_MESSAGES/docs/just.po index 1a90ab6f1..aa56f7f74 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/just.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/just.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,29 +19,29 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/just.md:8 +#: ../../../docs/just.md:1 msgid "Running `just` commands" msgstr "" -#: ../../../docs/just.md:10 +#: ../../../docs/just.md:3 msgid "We have previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers [`ansible-galaxy`](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html)). Our [`Makefile`](../Makefile) is still around, and you can still run these commands." msgstr "" -#: ../../../docs/just.md:12 +#: ../../../docs/just.md:5 msgid "In addition, we have added support for running commands via [`just`](https://github.com/casey/just) — a more modern command-runner alternative to `make`. It can be used to invoke `ansible-playbook` commands with less typing." msgstr "" -#: ../../../docs/just.md:14 +#: ../../../docs/just.md:7 msgid "The `just` utility executes shortcut commands (called as \"recipes\"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile). Most of the just recipes have no corresponding `Makefile` targets." msgstr "" -#: ../../../docs/just.md:16 -msgid "For some recipes such as `just update`, our `justfile` recommends installing `agru` (a faster alternative to `ansible-galaxy`) to speed up the process." +#: ../../../docs/just.md:9 +msgid "For some recipes such as `just update`, our `justfile` recommends installing [`agru`](https://github.com/etkecc/agru) (a faster alternative to `ansible-galaxy`) to speed up the process." msgstr "" -#: ../../../docs/just.md:18 +#: ../../../docs/just.md:11 msgid "Here are some examples of shortcuts:" msgstr "" @@ -69,7 +69,7 @@ msgstr "" msgid "Run `git pull` (to update the playbook) and install the Ansible roles" msgstr "" -#: ../../../docs/just.md ../../../docs/just.md:40 +#: ../../../docs/just.md ../../../docs/just.md:33 msgid "`just install-all`" msgstr "" @@ -133,50 +133,30 @@ msgstr "" msgid "Registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)" msgstr "" -#: ../../../docs/just.md:33 +#: ../../../docs/just.md:26 msgid "While [our documentation on prerequisites](prerequisites.md) lists `just` as one of the requirements for installation, using `just` is optional. If you find it difficult to install it, do not find it useful, or want to prefer raw `ansible-playbook` commands for some reason, feel free to run all commands manually. For example, you can run `ansible-galaxy` directly to install the Ansible roles: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`." msgstr "" -#: ../../../docs/just.md:35 +#: ../../../docs/just.md:28 msgid "Difference between playbook tags and shortcuts" msgstr "" -#: ../../../docs/just.md:37 +#: ../../../docs/just.md:30 msgid "It is worth noting that `just` \"recipes\" are different from [playbook tags](playbook-tags.md). The recipes are shortcuts of commands defined in `justfile` and can be executed by the `just` program only, while the playbook tags are available for the raw `ansible-playbook` commands as well. Please be careful not to confuse them." msgstr "" -#: ../../../docs/just.md:39 +#: ../../../docs/just.md:32 msgid "For example, these two commands are different:" msgstr "" -#: ../../../docs/just.md:41 +#: ../../../docs/just.md:34 msgid "`ansible-playbook -i inventory/hosts setup.yml --tags=install-all`" msgstr "" -#: ../../../docs/just.md:43 +#: ../../../docs/just.md:36 msgid "The just recipe runs `ensure-matrix-users-created` and `start` tags after `install-all`, while the latter runs only `install-all` tag. The correct shortcut of the latter is `just run-tags install-all`." msgstr "" -#: ../../../docs/just.md:45 -msgid "Such kind of difference sometimes matters. For example, when you install a Matrix server into which you will import old data (see [here](installing.md#installing-a-server-into-which-youll-import-old-data)), you are not supposed to run `just install-all` or `just setup-all`, because these commands start services immediately after installing components, which may prevent you from importing the data." -msgstr "" - -#: ../../../docs/just.md:47 -msgid "Conditional service restart" -msgstr "" - -#: ../../../docs/just.md:49 -msgid "When running `install-all` or `install-service` (whether via `just` or raw `ansible-playbook`), only services whose configuration or container image actually changed during the playbook run will be restarted. Unchanged services are left running (or get started if they were stopped). This reduces unnecessary downtime." -msgstr "" - -#: ../../../docs/just.md:51 -msgid "When running with `setup-*` tags (e.g. `setup-all`, `setup-synapse`), all services are unconditionally restarted regardless of whether changes were detected. This is appropriate for setup's thorough \"full setup\" semantics." -msgstr "" - -#: ../../../docs/just.md:53 -msgid "`start-all` and `start-group` always restart all targeted services, since no installation tasks run during these commands." -msgstr "" - -#: ../../../docs/just.md:55 -msgid "This behavior is automatically determined based on the playbook tags in use. It can be overridden with the `devture_systemd_service_manager_conditional_restart_enabled` variable. For example, to force unconditional restarts during installation: `just install-all --extra-vars='devture_systemd_service_manager_conditional_restart_enabled=false'`" +#: ../../../docs/just.md:38 +msgid "Such kind of difference sometimes matters. For example, when you install a Matrix server into which you will import old data (see [here](installing.md#installing-a-server-into-which-youll-import-old-data)), you are not supposed to run `just install-all` or `just setup-all`, because these commands start services immediately after installing components which may prevent your from importing old data." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-and-troubleshooting.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-and-troubleshooting.po index 6aa431ba0..b001bbf63 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-and-troubleshooting.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-and-troubleshooting.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,160 +19,68 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/maintenance-and-troubleshooting.md:12 +#: ../../../docs/maintenance-and-troubleshooting.md:1 msgid "Maintenance and Troubleshooting" msgstr "" -#: ../../../docs/maintenance-and-troubleshooting.md:14 -msgid "Maintenance" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:16 -msgid "How to back up the data on your server" +#: ../../../docs/maintenance-and-troubleshooting.md:3 +msgid "How to see the current status of your services" msgstr "" -#: ../../../docs/maintenance-and-troubleshooting.md:18 -msgid "We haven't documented this properly yet, but the general advice is to:" +#: ../../../docs/maintenance-and-troubleshooting.md:5 +msgid "You can check the status of your services by using `systemctl status`. Example:" msgstr "" -#: ../../../docs/maintenance-and-troubleshooting.md:20 -msgid "back up Postgres by making a database dump. See [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql)" +#: ../../../docs/maintenance-and-troubleshooting.md:15 +msgid "Docker containers that the playbook configures are supervised by [systemd](https://wiki.archlinux.org/title/Systemd) and their logs are configured to go to [systemd-journald](https://wiki.archlinux.org/title/Systemd/Journal)." msgstr "" -#: ../../../docs/maintenance-and-troubleshooting.md:22 -msgid "back up all `/matrix` files, except for `/matrix/postgres/data` (you already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` (this directory may exist and contain your old data if you've [performed a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql))." +#: ../../../docs/maintenance-and-troubleshooting.md:17 +msgid "To prevent double-logging, Docker logging is disabled by explicitly passing `--log-driver=none` to all containers. Due to this, you **cannot** view logs using `docker logs`." msgstr "" -#: ../../../docs/maintenance-and-troubleshooting.md:24 -msgid "You can later restore these by:" +#: ../../../docs/maintenance-and-troubleshooting.md:19 +msgid "To view systemd-journald logs using [journalctl](https://man.archlinux.org/man/journalctl.1), run a command like this:" msgstr "" -#: ../../../docs/maintenance-and-troubleshooting.md:26 -msgid "Restoring the `/matrix` directory and files on the new server manually" +#: ../../../docs/maintenance-and-troubleshooting.md:25 +msgid "Increase logging verbosity" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:27 -msgid "Following the instruction described on [Installing a server into which you'll import old data](installing.md#installing-a-server-into-which-youll-import-old-data)" +msgid "Because the [Synapse](https://github.com/element-hq/synapse) Matrix server is originally very chatty when it comes to logging, we intentionally reduce its [logging level](https://docs.python.org/3/library/logging.html#logging-levels) from `INFO` to `WARNING`." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:29 -msgid "If your server's IP address has changed, you may need to [set up DNS](configuring-dns.md) again." +msgid "If you'd like to debug an issue or [report a Synapse bug](https://github.com/element-hq/synapse/issues/new/choose) to the developers, it'd be better if you temporarily increasing the logging level to `INFO`." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:31 -msgid "Remove unused Docker data" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:33 -msgid "You can free some disk space from Docker by removing its unused data. See [docker system prune](https://docs.docker.com/engine/reference/commandline/system_prune/) for more information." +msgid "Example configuration (`inventory/host_vars/matrix.example.com/vars.yml`):" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:39 -msgid "The shortcut command with `just` program is also available: `just run-tags run-docker-prune`" +msgid "Re-run the playbook after making these configuration changes." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:41 -msgid "Postgres" +msgid "Remove unused Docker data" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:43 -msgid "See the dedicated [PostgreSQL maintenance](maintenance-postgres.md) documentation page." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:45 -msgid "Synapse" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:47 -msgid "See the dedicated [Synapse maintenance](maintenance-synapse.md) documentation page." +msgid "You can free some disk space from Docker, see [docker system prune](https://docs.docker.com/engine/reference/commandline/system_prune/) for more information." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:49 -msgid "Troubleshooting" +msgid "The shortcut command with `just` program is also available: `just run-tags run-docker-prune`" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:51 -msgid "How to see the current status of your services" +msgid "Postgres" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:53 -msgid "You can check the status of your services by using `systemctl status`. Example:" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:63 -msgid "How to see the logs" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:65 -msgid "Docker containers that the playbook configures are supervised by [systemd](https://wiki.archlinux.org/title/Systemd) and their logs are configured to go to [systemd-journald](https://wiki.archlinux.org/title/Systemd/Journal)." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:67 -msgid "For example, you can find the logs of `matrix-synapse` in `systemd-journald` by logging in to the server with SSH and running the command as below:" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:73 -msgid "Available service names can be seen by doing `ls /etc/systemd/system/matrix*.service` on the server. Some services also log to files in `/matrix/*/data/..`, but we're slowly moving away from that." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:75 -msgid "We just simply delegate logging to journald and it takes care of persistence and expiring old data." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:77 -msgid "Enable systemd/journald logs persistence" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:79 -msgid "On some distros, the journald logs are just in-memory and not persisted to disk." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:81 -msgid "Consult (and feel free to adjust) your distro's journald logging configuration in `/etc/systemd/journald.conf`." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:83 -msgid "To enable persistence and put some limits on how large the journal log files can become, adjust your configuration like this:" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:94 -msgid "How to check if services work" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:96 -msgid "The playbook can perform a check to ensure that you've configured things correctly and that services are running." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:98 -msgid "To perform the check, run:" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:104 -msgid "The shortcut command with `just` program is also available: `just run-tags self-check`" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:106 -msgid "If it's all green, everything is probably running correctly." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:108 -msgid "Besides this self-check, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:110 -msgid "How to debug or force SSL certificate renewal" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:112 -msgid "SSL certificates are managed automatically by the [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:114 -msgid "If you're having trouble with SSL certificate renewal, check the Traefik logs (`journalctl -fu matrix-traefik`)." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:116 -msgid "If you're [using your own webserver](configuring-playbook-own-webserver.md) instead of the integrated one (Traefik), you should investigate in another way." +msgid "See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) documentation page." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-migrating.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-migrating.po index 64973cc1e..a82fdaf44 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-migrating.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-migrating.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,120 +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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/maintenance-migrating.md:10 +#: ../../../docs/maintenance-migrating.md:1 msgid "Migrating to new server" msgstr "" -#: ../../../docs/maintenance-migrating.md:12 +#: ../../../docs/maintenance-migrating.md:3 msgid "This documentation explains how to migrate your Matrix services (server, client, bridges, etc.) and data **from an old server to a new server**." msgstr "" -#: ../../../docs/maintenance-migrating.md:14 +#: ../../../docs/maintenance-migrating.md:5 msgid "**Notes**:" msgstr "" -#: ../../../docs/maintenance-migrating.md:15 +#: ../../../docs/maintenance-migrating.md:6 msgid "This migration guide is applicable if you migrate from one server to another server having the same CPU architecture (e.g. both servers being `amd64`)." msgstr "" -#: ../../../docs/maintenance-migrating.md:17 +#: ../../../docs/maintenance-migrating.md:8 msgid "If you're trying to migrate between different architectures (e.g. `amd64` --> `arm64`), simply copying the complete `/matrix` directory is **not** possible as it would move the raw PostgreSQL data (`/matrix/postgres/data`) between different architectures. In this specific case, you can use the guide below as a reference, but you would also need to avoid syncing `/matrix/postgres/data` to the new host, and also dump the database on your current server and import it properly on the new server. See our [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql) docs for help with PostgreSQL backup/restore." msgstr "" -#: ../../../docs/maintenance-migrating.md:18 +#: ../../../docs/maintenance-migrating.md:9 msgid "If you have any questions about migration or encountered an issue during migration, do not hesitate to ask for help on [our Matrix room](https://matrix.to/#/%23matrix-docker-ansible-deploy:devture.com). You probably might want to prepare a temporary/sub account on another Matrix server in case it becomes impossible to use your server due to migration failure by any chance." msgstr "" -#: ../../../docs/maintenance-migrating.md:20 +#: ../../../docs/maintenance-migrating.md:11 msgid "You can't change the domain (specified in the `matrix_domain` variable) after the initial deployment." msgstr "" -#: ../../../docs/maintenance-migrating.md:22 +#: ../../../docs/maintenance-migrating.md:13 msgid "Lower DNS TTL" msgstr "" -#: ../../../docs/maintenance-migrating.md:24 +#: ../../../docs/maintenance-migrating.md:15 msgid "Prepare by lowering DNS TTL for your domains (`matrix.example.com`, etc.), so that DNS record changes would happen faster, leading to less downtime." msgstr "" -#: ../../../docs/maintenance-migrating.md:26 +#: ../../../docs/maintenance-migrating.md:17 msgid "Stop services on the old server completely" msgstr "" -#: ../../../docs/maintenance-migrating.md:28 +#: ../../../docs/maintenance-migrating.md:19 msgid "Before migrating, you need to stop all services on the old server and make sure they won't be starting again." msgstr "" -#: ../../../docs/maintenance-migrating.md:30 +#: ../../../docs/maintenance-migrating.md:21 msgid "To do so, it is recommended to run the `systemctl` command on the server. Running the playbook's `stop` tag also stops the services, but just once; they will start again if you reboot the server." msgstr "" -#: ../../../docs/maintenance-migrating.md:32 +#: ../../../docs/maintenance-migrating.md:23 msgid "Log in to the old server and run the command as `root` (or a user that can run it with `sudo`):" msgstr "" -#: ../../../docs/maintenance-migrating.md:38 +#: ../../../docs/maintenance-migrating.md:29 msgid "Copy data directory to the new server" msgstr "" -#: ../../../docs/maintenance-migrating.md:40 +#: ../../../docs/maintenance-migrating.md:31 msgid "After you've confirmed that all services were stopped, copy the `/matrix` directory from the old server to the new server. When copying, make sure to preserve ownership and permissions (use `cp -p` or `rsync -ar`)!" msgstr "" -#: ../../../docs/maintenance-migrating.md:42 +#: ../../../docs/maintenance-migrating.md:33 msgid "Adjust DNS records" msgstr "" -#: ../../../docs/maintenance-migrating.md:44 +#: ../../../docs/maintenance-migrating.md:35 msgid "Make sure your DNS records are adjusted to point to the new server's IP address." msgstr "" -#: ../../../docs/maintenance-migrating.md:46 +#: ../../../docs/maintenance-migrating.md:37 msgid "Update `inventory/hosts` file" msgstr "" -#: ../../../docs/maintenance-migrating.md:48 +#: ../../../docs/maintenance-migrating.md:39 msgid "Having adjusted DNS records, replace the old server's external IP address on the `inventory/hosts` file with that of the new server." msgstr "" -#: ../../../docs/maintenance-migrating.md:50 +#: ../../../docs/maintenance-migrating.md:41 msgid "Create `matrix` user and group on the new server" msgstr "" -#: ../../../docs/maintenance-migrating.md:52 +#: ../../../docs/maintenance-migrating.md:43 msgid "Then, run the command below on your local computer to create the `matrix` user and group on the new server:" msgstr "" -#: ../../../docs/maintenance-migrating.md:58 +#: ../../../docs/maintenance-migrating.md:49 msgid "The shortcut command with `just` program is also available: `just run-tags setup-system-user`" msgstr "" -#: ../../../docs/maintenance-migrating.md:60 +#: ../../../docs/maintenance-migrating.md:51 msgid "**Note**: because the `matrix` user and group are created dynamically on each server, the user/group ID may differ between the old and new server. We suggest that you adjust ownership of `/matrix` files. To adjust the ownership, log in to the new server and run the command:" msgstr "" -#: ../../../docs/maintenance-migrating.md:66 +#: ../../../docs/maintenance-migrating.md:57 msgid "Install and start all services on the new server" msgstr "" -#: ../../../docs/maintenance-migrating.md:68 +#: ../../../docs/maintenance-migrating.md:59 msgid "Finally, run the command below on your local computer to finish the installation and start all services:" msgstr "" -#: ../../../docs/maintenance-migrating.md:74 +#: ../../../docs/maintenance-migrating.md:65 msgid "The shortcut command with `just` program is also available: `just run-tags install-all,start`" msgstr "" -#: ../../../docs/maintenance-migrating.md:76 +#: ../../../docs/maintenance-migrating.md:67 msgid "Check if services work" msgstr "" -#: ../../../docs/maintenance-migrating.md:78 -msgid "After starting the services, you probably might want to ensure that you've migrated things correctly and that services are running. For instructions, see: [check if services work](maintenance-and-troubleshooting.md#how-to-check-if-services-work)" +#: ../../../docs/maintenance-migrating.md:69 +msgid "After starting the services, you probably might want to ensure that you've migrated things correctly and that services are running. For instructions, see: [check if services work](maintenance-checking-services.md)" msgstr "" -#: ../../../docs/maintenance-migrating.md:80 +#: ../../../docs/maintenance-migrating.md:71 msgid "Having make sure that both services and federation work as expected, you can safely shutdown the old server." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-postgres.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-postgres.po index c9059c560..620ced334 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-postgres.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-postgres.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,204 +19,204 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/maintenance-postgres.md:13 +#: ../../../docs/maintenance-postgres.md:1 msgid "PostgreSQL maintenance" msgstr "" -#: ../../../docs/maintenance-postgres.md:15 +#: ../../../docs/maintenance-postgres.md:3 msgid "This document shows you how to perform various maintenance tasks related to the Postgres database server used by Matrix." msgstr "" -#: ../../../docs/maintenance-postgres.md:17 +#: ../../../docs/maintenance-postgres.md:5 msgid "Table of contents:" msgstr "" -#: ../../../docs/maintenance-postgres.md:18 +#: ../../../docs/maintenance-postgres.md:7 msgid "[Getting a database terminal](#getting-a-database-terminal), for when you wish to execute SQL queries" msgstr "" -#: ../../../docs/maintenance-postgres.md:19 +#: ../../../docs/maintenance-postgres.md:9 msgid "[Vacuuming PostgreSQL](#vacuuming-postgresql), for when you wish to run a Postgres [VACUUM](https://www.postgresql.org/docs/current/sql-vacuum.html) (optimizing disk space)" msgstr "" -#: ../../../docs/maintenance-postgres.md:20 +#: ../../../docs/maintenance-postgres.md:11 msgid "[Backing up PostgreSQL](#backing-up-postgresql), for when you wish to make a backup" msgstr "" -#: ../../../docs/maintenance-postgres.md:21 +#: ../../../docs/maintenance-postgres.md:13 msgid "[Upgrading PostgreSQL](#upgrading-postgresql), for upgrading to new major versions of PostgreSQL. Such **manual upgrades are sometimes required**." msgstr "" -#: ../../../docs/maintenance-postgres.md:22 +#: ../../../docs/maintenance-postgres.md:15 msgid "[Tuning PostgreSQL](#tuning-postgresql) to make it run faster" msgstr "" -#: ../../../docs/maintenance-postgres.md:24 +#: ../../../docs/maintenance-postgres.md:17 msgid "Getting a database terminal" msgstr "" -#: ../../../docs/maintenance-postgres.md:26 -msgid "You can use the `/matrix/postgres/bin/cli` tool to get interactive terminal access ([psql](https://www.postgresql.org/docs/current/app-psql.html)) to the PostgreSQL server." +#: ../../../docs/maintenance-postgres.md:19 +msgid "You can use the `/matrix/postgres/bin/cli` tool to get interactive terminal access ([psql](https://www.postgresql.org/docs/11/app-psql.html)) to the PostgreSQL server." msgstr "" -#: ../../../docs/maintenance-postgres.md:28 +#: ../../../docs/maintenance-postgres.md:21 msgid "If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above tool will not be available." msgstr "" -#: ../../../docs/maintenance-postgres.md:30 +#: ../../../docs/maintenance-postgres.md:23 msgid "By default, this tool puts you in the `matrix` database, which contains nothing." msgstr "" -#: ../../../docs/maintenance-postgres.md:32 +#: ../../../docs/maintenance-postgres.md:25 msgid "To see the available databases, run `\\list` (or just `\\l`)." msgstr "" -#: ../../../docs/maintenance-postgres.md:34 +#: ../../../docs/maintenance-postgres.md:27 msgid "To change to another database (for example `synapse`), run `\\connect synapse` (or just `\\c synapse`)." msgstr "" -#: ../../../docs/maintenance-postgres.md:36 +#: ../../../docs/maintenance-postgres.md:29 msgid "You can then proceed to write queries. Example: `SELECT COUNT(*) FROM users;`" msgstr "" -#: ../../../docs/maintenance-postgres.md:38 -msgid "[!WARNING] **Modifying the database directly (especially as services are running) is dangerous and may lead to irreversible database corruption.** When in doubt, consider [making a backup](#backing-up-postgresql)." +#: ../../../docs/maintenance-postgres.md:31 +msgid "**Be careful**. Modifying the database directly (especially as services are running) is dangerous and may lead to irreversible database corruption. When in doubt, consider [making a backup](#backing-up-postgresql)." msgstr "" -#: ../../../docs/maintenance-postgres.md:41 +#: ../../../docs/maintenance-postgres.md:33 msgid "Vacuuming PostgreSQL" msgstr "" -#: ../../../docs/maintenance-postgres.md:43 +#: ../../../docs/maintenance-postgres.md:35 msgid "Deleting lots data from Postgres does not make it release disk space, until you perform a [`VACUUM` operation](https://www.postgresql.org/docs/current/sql-vacuum.html)." msgstr "" -#: ../../../docs/maintenance-postgres.md:45 +#: ../../../docs/maintenance-postgres.md:37 msgid "You can run different `VACUUM` operations via the playbook, with the default preset being `vacuum-complete`:" msgstr "" -#: ../../../docs/maintenance-postgres.md:47 +#: ../../../docs/maintenance-postgres.md:39 msgid "(default) `vacuum-complete`: stops all services temporarily and runs `VACUUM FULL VERBOSE ANALYZE`." msgstr "" -#: ../../../docs/maintenance-postgres.md:48 +#: ../../../docs/maintenance-postgres.md:40 msgid "`vacuum-full`: stops all services temporarily and runs `VACUUM FULL VERBOSE`" msgstr "" -#: ../../../docs/maintenance-postgres.md:49 +#: ../../../docs/maintenance-postgres.md:41 msgid "`vacuum`: runs `VACUUM VERBOSE` without stopping any services" msgstr "" -#: ../../../docs/maintenance-postgres.md:50 +#: ../../../docs/maintenance-postgres.md:42 msgid "`vacuum-analyze` runs `VACUUM VERBOSE ANALYZE` without stopping any services" msgstr "" -#: ../../../docs/maintenance-postgres.md:51 +#: ../../../docs/maintenance-postgres.md:43 msgid "`analyze` runs `ANALYZE VERBOSE` without stopping any services (this is just [ANALYZE](https://www.postgresql.org/docs/current/sql-analyze.html) without doing a vacuum, so it's faster)" msgstr "" -#: ../../../docs/maintenance-postgres.md:53 +#: ../../../docs/maintenance-postgres.md:45 msgid "**Note**: for the `vacuum-complete` and `vacuum-full` presets, you'll need plenty of available disk space in your Postgres data directory (usually `/matrix/postgres/data`). These presets also stop all services (e.g. Synapse, etc.) while the vacuum operation is running." msgstr "" -#: ../../../docs/maintenance-postgres.md:55 +#: ../../../docs/maintenance-postgres.md:47 msgid "Example playbook invocations:" msgstr "" -#: ../../../docs/maintenance-postgres.md:57 +#: ../../../docs/maintenance-postgres.md:49 msgid "`just run-tags run-postgres-vacuum`: runs the default `vacuum-complete` preset and restarts all services" msgstr "" -#: ../../../docs/maintenance-postgres.md:58 +#: ../../../docs/maintenance-postgres.md:50 msgid "`just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze`: runs the `analyze` preset with all services remaining operational at all times" msgstr "" -#: ../../../docs/maintenance-postgres.md:60 +#: ../../../docs/maintenance-postgres.md:52 msgid "Backing up PostgreSQL" msgstr "" -#: ../../../docs/maintenance-postgres.md:62 -msgid "To automatically make Postgres database backups on a fixed schedule, consider enabling the [Postgres Backup](configuring-playbook-postgres-backup.md) service." +#: ../../../docs/maintenance-postgres.md:54 +msgid "To automatically make Postgres database backups on a fixed schedule, see [Setting up postgres backup](configuring-playbook-postgres-backup.md)." msgstr "" -#: ../../../docs/maintenance-postgres.md:64 -msgid "To make a one-off back up of the current PostgreSQL database, make sure it's running and then execute a command like this on the server:" +#: ../../../docs/maintenance-postgres.md:56 +msgid "To make a one off back up of the current PostgreSQL database, make sure it's running and then execute a command like this on the server:" msgstr "" -#: ../../../docs/maintenance-postgres.md:75 +#: ../../../docs/maintenance-postgres.md:67 msgid "If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above command will not work, because neither the credentials file (`/matrix/postgres/env-postgres-psql`), nor the `matrix-postgres` container is available." msgstr "" -#: ../../../docs/maintenance-postgres.md:77 +#: ../../../docs/maintenance-postgres.md:69 msgid "Restoring a backup made this way can be done by [importing it](importing-postgres.md)." msgstr "" -#: ../../../docs/maintenance-postgres.md:79 +#: ../../../docs/maintenance-postgres.md:71 msgid "Upgrading PostgreSQL" msgstr "" -#: ../../../docs/maintenance-postgres.md:81 +#: ../../../docs/maintenance-postgres.md:73 msgid "Unless you are using an [external Postgres server](configuring-playbook-external-postgres.md), this playbook initially installs Postgres for you." msgstr "" -#: ../../../docs/maintenance-postgres.md:83 +#: ../../../docs/maintenance-postgres.md:75 msgid "Once installed, the playbook attempts to preserve the Postgres version it starts with. This is because newer Postgres versions cannot start with data generated by older Postgres versions." msgstr "" -#: ../../../docs/maintenance-postgres.md:85 +#: ../../../docs/maintenance-postgres.md:77 msgid "Upgrades must be performed manually." msgstr "" -#: ../../../docs/maintenance-postgres.md:87 +#: ../../../docs/maintenance-postgres.md:79 msgid "The playbook can upgrade your existing Postgres setup with the following command:" msgstr "" -#: ../../../docs/maintenance-postgres.md:93 +#: ../../../docs/maintenance-postgres.md:85 msgid "**The old Postgres data directory is backed up** automatically, by renaming it to `/matrix/postgres/data-auto-upgrade-backup`. To rename to a different path, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_auto_upgrade_backup_data_path=/another/disk/matrix-postgres-before-upgrade\"`" msgstr "" -#: ../../../docs/maintenance-postgres.md:95 +#: ../../../docs/maintenance-postgres.md:87 msgid "The auto-upgrade-backup directory stays around forever, until you **manually decide to delete it**." msgstr "" -#: ../../../docs/maintenance-postgres.md:97 +#: ../../../docs/maintenance-postgres.md:89 msgid "As part of the upgrade, the database is dumped to `/tmp`, an upgraded and empty Postgres server is started, and then the dump is restored into the new server. To use a different directory for the dump, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_dump_dir=/directory/to/dump/here\"`" msgstr "" -#: ../../../docs/maintenance-postgres.md:99 +#: ../../../docs/maintenance-postgres.md:91 msgid "To save disk space in `/tmp`, the dump file is gzipped on the fly at the expense of CPU usage. If you have plenty of space in `/tmp` and would rather avoid gzipping, you can explicitly pass a dump filename which doesn't end in `.gz`. Example: `--extra-vars=\"postgres_dump_name=matrix-postgres-dump.sql\"`" msgstr "" -#: ../../../docs/maintenance-postgres.md:101 -msgid "**All databases, roles, etc. on the Postgres server are migrated**. However, other components that depend on specific Postgres versions (like the [Postgres Backup](configuring-playbook-postgres-backup.md) service) may need to be updated after the upgrade by using `just install-all`" +#: ../../../docs/maintenance-postgres.md:93 +msgid "**All databases, roles, etc. on the Postgres server are migrated**." msgstr "" -#: ../../../docs/maintenance-postgres.md:103 +#: ../../../docs/maintenance-postgres.md:95 msgid "Tuning PostgreSQL" msgstr "" -#: ../../../docs/maintenance-postgres.md:105 +#: ../../../docs/maintenance-postgres.md:97 msgid "PostgreSQL can be [tuned](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) to make it run faster. This is done by passing extra arguments to the Postgres process." msgstr "" -#: ../../../docs/maintenance-postgres.md:107 -msgid "The [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) **already does some tuning by default**, which matches the [tuning logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) done by websites like https://pgtune.leopard.in.ua/. You can manually influence some of the tuning variables. These parameters (variables) are injected via the `postgres_postgres_process_extra_arguments_default` variable." +#: ../../../docs/maintenance-postgres.md:99 +msgid "The [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) **already does some tuning by default**, which matches the [tuning logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) done by websites like https://pgtune.leopard.in.ua/. You can manually influence some of the tuning variables. These parameters (variables) are injected via the `postgres_postgres_process_extra_arguments_auto` variable." msgstr "" -#: ../../../docs/maintenance-postgres.md:109 +#: ../../../docs/maintenance-postgres.md:101 msgid "Most users should be fine with the automatically-done tuning. However, you may wish to:" msgstr "" -#: ../../../docs/maintenance-postgres.md:111 -msgid "**adjust the automatically-determined tuning parameters manually**: change the values for the tuning variables defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) (see `postgres_max_connections`, `postgres_data_storage` etc). These variables are ultimately passed to Postgres via a `postgres_postgres_process_extra_arguments_default` variable" +#: ../../../docs/maintenance-postgres.md:103 +msgid "**adjust the automatically-determined tuning parameters manually**: change the values for the tuning variables defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) (see `postgres_max_connections`, `postgres_data_storage` etc). These variables are ultimately passed to Postgres via a `postgres_postgres_process_extra_arguments_auto` variable" msgstr "" -#: ../../../docs/maintenance-postgres.md:113 -msgid "**turn automatically-performed tuning off**: override it like this: `postgres_postgres_process_extra_arguments_default: []`" +#: ../../../docs/maintenance-postgres.md:105 +msgid "**turn automatically-performed tuning off**: override it like this: `postgres_postgres_process_extra_arguments_auto: []`" msgstr "" -#: ../../../docs/maintenance-postgres.md:115 -msgid "**add additional tuning parameters**: define your additional Postgres configuration parameters in `postgres_postgres_process_extra_arguments_custom`. See `postgres_postgres_process_extra_arguments_default` defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) for inspiration" +#: ../../../docs/maintenance-postgres.md:107 +msgid "**add additional tuning parameters**: define your additional Postgres configuration parameters in `postgres_postgres_process_extra_arguments_custom`. See `postgres_postgres_process_extra_arguments_auto` defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) for inspiration" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-synapse.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-synapse.po index ac2ff018d..da0db46d9 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-synapse.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-synapse.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,192 +19,184 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/maintenance-synapse.md:12 +#: ../../../docs/maintenance-synapse.md:1 msgid "Synapse maintenance" msgstr "" -#: ../../../docs/maintenance-synapse.md:14 +#: ../../../docs/maintenance-synapse.md:3 msgid "This document shows you how to perform various maintenance tasks related to the Synapse chat server." msgstr "" -#: ../../../docs/maintenance-synapse.md:16 +#: ../../../docs/maintenance-synapse.md:5 msgid "Table of contents:" msgstr "" -#: ../../../docs/maintenance-synapse.md:17 +#: ../../../docs/maintenance-synapse.md:7 msgid "[Purging old data with the Purge History API](#purging-old-data-with-the-purge-history-api), for when you wish to delete in-use (but old) data from the Synapse database" msgstr "" -#: ../../../docs/maintenance-synapse.md:18 +#: ../../../docs/maintenance-synapse.md:9 msgid "[Compressing state with rust-synapse-compress-state](#compressing-state-with-rust-synapse-compress-state)" msgstr "" -#: ../../../docs/maintenance-synapse.md:19 +#: ../../../docs/maintenance-synapse.md:11 msgid "[Browse and manipulate the database](#browse-and-manipulate-the-database), for when you really need to take matters into your own hands" msgstr "" -#: ../../../docs/maintenance-synapse.md:20 +#: ../../../docs/maintenance-synapse.md:13 msgid "[Make Synapse faster](#make-synapse-faster)" msgstr "" -#: ../../../docs/maintenance-synapse.md:22 -msgid "💡 See this page for details about configuring Synapse: [Configuring Synapse](configuring-playbook-synapse.md)" -msgstr "" - -#: ../../../docs/maintenance-synapse.md:24 +#: ../../../docs/maintenance-synapse.md:15 msgid "Purging old data with the Purge History API" msgstr "" -#: ../../../docs/maintenance-synapse.md:26 +#: ../../../docs/maintenance-synapse.md:17 msgid "You can use the **[Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md)** to delete old messages on a per-room basis. **This is destructive** (especially for non-federated rooms), because it means **people will no longer have access to history past a certain point**." msgstr "" -#: ../../../docs/maintenance-synapse.md:28 +#: ../../../docs/maintenance-synapse.md:19 msgid "To make use of this Synapse Admin API, **you'll need an admin access token** first. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" -#: ../../../docs/maintenance-synapse.md:30 +#: ../../../docs/maintenance-synapse.md:21 msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" -#: ../../../docs/maintenance-synapse.md:33 +#: ../../../docs/maintenance-synapse.md:24 msgid "Synapse's Admin API is not exposed to the internet by default, following [official Synapse reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints). To expose it you will need to add `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` to your `vars.yml` file." msgstr "" -#: ../../../docs/maintenance-synapse.md:35 +#: ../../../docs/maintenance-synapse.md:26 msgid "Follow the [Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md) documentation page for the actual purging instructions." msgstr "" -#: ../../../docs/maintenance-synapse.md:37 +#: ../../../docs/maintenance-synapse.md:28 msgid "After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." msgstr "" -#: ../../../docs/maintenance-synapse.md:39 +#: ../../../docs/maintenance-synapse.md:30 msgid "Compressing state with rust-synapse-compress-state" msgstr "" -#: ../../../docs/maintenance-synapse.md:41 +#: ../../../docs/maintenance-synapse.md:32 msgid "[rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) can be used to optimize some `_state` tables used by Synapse. If your server participates in large rooms this is the most effective way to reduce the size of your database." msgstr "" -#: ../../../docs/maintenance-synapse.md:43 +#: ../../../docs/maintenance-synapse.md:34 msgid "**Note**: besides running the `rust-synapse-compress-state` tool manually, you can also enable its `synapse-auto-compressor` tool by [Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md). The automatic tool will run on a schedule every day and you won't have to compress state manually ever again." msgstr "" -#: ../../../docs/maintenance-synapse.md:45 +#: ../../../docs/maintenance-synapse.md:36 msgid "`rust-synapse-compress-state` should be safe to use (even when Synapse is running), but it's always a good idea to [make Postgres backups](./maintenance-postgres.md#backing-up-postgresql) first." msgstr "" -#: ../../../docs/maintenance-synapse.md:47 +#: ../../../docs/maintenance-synapse.md:38 msgid "To ask the playbook to run rust-synapse-compress-state, execute:" msgstr "" -#: ../../../docs/maintenance-synapse.md:53 +#: ../../../docs/maintenance-synapse.md:44 msgid "The shortcut command with `just` program is also available: `just run-tags rust-synapse-compress-state`" msgstr "" -#: ../../../docs/maintenance-synapse.md:55 +#: ../../../docs/maintenance-synapse.md:46 msgid "By default, all rooms with more than `100000` state group rows will be compressed. If you need to adjust this, pass: `--extra-vars='matrix_synapse_rust_synapse_compress_state_min_state_groups_required=SOME_NUMBER_HERE'` to the command above." msgstr "" -#: ../../../docs/maintenance-synapse.md:57 +#: ../../../docs/maintenance-synapse.md:48 msgid "After state compression, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." msgstr "" -#: ../../../docs/maintenance-synapse.md:59 +#: ../../../docs/maintenance-synapse.md:50 msgid "Browse and manipulate the database" msgstr "" -#: ../../../docs/maintenance-synapse.md:61 +#: ../../../docs/maintenance-synapse.md:52 msgid "When the [Synapse Admin API](https://github.com/element-hq/synapse/tree/master/docs/admin_api) and the other tools do not provide a more convenient way, having a look at synapse's postgresql database can satisfy a lot of admins' needs." msgstr "" -#: ../../../docs/maintenance-synapse.md:63 +#: ../../../docs/maintenance-synapse.md:54 msgid "Editing the database manually is not recommended or supported by the Synapse developers. If you are going to do so you should [make a database backup](./maintenance-postgres.md#backing-up-postgresql)." msgstr "" -#: ../../../docs/maintenance-synapse.md:65 +#: ../../../docs/maintenance-synapse.md:56 msgid "First, set up an SSH tunnel to your Matrix server (skip if it is your local machine):" msgstr "" -#: ../../../docs/maintenance-synapse.md:72 +#: ../../../docs/maintenance-synapse.md:63 msgid "Then start up an ephemeral [adminer](https://www.adminer.org/) container on the Matrix server, connecting it to the `matrix` network and linking the postgresql container:" msgstr "" -#: ../../../docs/maintenance-synapse.md:78 +#: ../../../docs/maintenance-synapse.md:69 msgid "You should then be able to browse the adminer database administration GUI at http://localhost:1799/ after entering your DB credentials (found in the `host_vars` or on the server in `{{matrix_synapse_config_dir_path}}/homeserver.yaml` under `database.args`)" msgstr "" -#: ../../../docs/maintenance-synapse.md:80 +#: ../../../docs/maintenance-synapse.md:71 msgid "⚠️️ Be **very careful** with this, there is **no undo** for impromptu DB operations." msgstr "" -#: ../../../docs/maintenance-synapse.md:82 +#: ../../../docs/maintenance-synapse.md:73 msgid "Make Synapse faster" msgstr "" -#: ../../../docs/maintenance-synapse.md:84 +#: ../../../docs/maintenance-synapse.md:75 msgid "Synapse's presence feature which tracks which users are online and which are offline can use a lot of processing power. You can disable presence by adding `matrix_synapse_presence_enabled: false` to your `vars.yml` file." msgstr "" -#: ../../../docs/maintenance-synapse.md:86 -msgid "On smaller servers, consider limiting joins to very complex rooms with [the room complexity guard](configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts)." -msgstr "" - -#: ../../../docs/maintenance-synapse.md:88 +#: ../../../docs/maintenance-synapse.md:77 msgid "If you have enough compute resources (CPU & RAM), you can make Synapse better use of them by [enabling load-balancing with workers](configuring-playbook-synapse.md#load-balancing-with-workers)." msgstr "" -#: ../../../docs/maintenance-synapse.md:90 +#: ../../../docs/maintenance-synapse.md:79 msgid "[Tuning your PostgreSQL database](maintenance-postgres.md#tuning-postgresql) could also improve Synapse performance. The playbook tunes the integrated Postgres database automatically, but based on your needs you may wish to adjust tuning variables manually. If you're using an [external Postgres database](configuring-playbook-external-postgres.md), you will also need to tune Postgres manually." msgstr "" -#: ../../../docs/maintenance-synapse.md:92 +#: ../../../docs/maintenance-synapse.md:81 msgid "Tuning caches and cache autotuning" msgstr "" -#: ../../../docs/maintenance-synapse.md:94 +#: ../../../docs/maintenance-synapse.md:83 msgid "Tuning Synapse's cache factor is useful for performance increases but also as part of controlling Synapse's memory use. Use the variable `matrix_synapse_caches_global_factor` to set the cache factor as part of this process." msgstr "" -#: ../../../docs/maintenance-synapse.md:96 +#: ../../../docs/maintenance-synapse.md:85 msgid "**The playbook defaults the global cache factor to a large value** (e.g. `10`). A smaller value (e.g. `0.5`) will decrease the amount used for caches, but will [not necessarily decrease RAM usage as a whole](https://github.com/matrix-org/synapse/issues/3939)." msgstr "" -#: ../../../docs/maintenance-synapse.md:98 +#: ../../../docs/maintenance-synapse.md:87 msgid "Tuning the cache factor is useful only to a limited degree (as its crude to do in isolation) and therefore users who are tuning their cache factor should likely look into tuning autotune variables as well (see below)." msgstr "" -#: ../../../docs/maintenance-synapse.md:100 +#: ../../../docs/maintenance-synapse.md:89 msgid "Cache autotuning is **enabled by default** and controlled via the following variables:" msgstr "" -#: ../../../docs/maintenance-synapse.md:102 +#: ../../../docs/maintenance-synapse.md:91 msgid "`matrix_synapse_cache_autotuning_max_cache_memory_usage` — defaults to 1/8 of total RAM with a cap of 2GB; values are specified in bytes" msgstr "" -#: ../../../docs/maintenance-synapse.md:103 +#: ../../../docs/maintenance-synapse.md:92 msgid "`matrix_synapse_cache_autotuning_target_cache_memory_usage` — defaults to 1/16 of total RAM with a cap of 1GB; values are specified in bytes" msgstr "" -#: ../../../docs/maintenance-synapse.md:104 +#: ../../../docs/maintenance-synapse.md:93 msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` — defaults to `30s`" msgstr "" -#: ../../../docs/maintenance-synapse.md:106 +#: ../../../docs/maintenance-synapse.md:95 msgid "You can **learn more about cache-autotuning and the global cache factor settings** in the [Synapse's documentation on caches and associated values](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values)." msgstr "" -#: ../../../docs/maintenance-synapse.md:108 +#: ../../../docs/maintenance-synapse.md:97 msgid "To **disable cache auto-tuning**, unset all values:" msgstr "" -#: ../../../docs/maintenance-synapse.md:116 +#: ../../../docs/maintenance-synapse.md:105 msgid "Users who wish to lower Synapse's RAM footprint should look into lowering the global cache factor and tweaking the autotune variables (or disabling auto-tuning). If your cache factor is too low for a given auto tune setting your caches will not reach autotune thresholds and autotune won't be able to do its job. Therefore, when auto-tuning is enabled (which it is by default), it's recommended to have your cache factor be large." msgstr "" -#: ../../../docs/maintenance-synapse.md:118 +#: ../../../docs/maintenance-synapse.md:107 msgid "See also [How do I optimize this setup for a low-power server?](faq.md#how-do-i-optimize-this-setup-for-a-low-power-server)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/playbook-tags.po b/i18n/locales/bg/LC_MESSAGES/docs/playbook-tags.po index 90d2a1eb4..d99618b29 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/playbook-tags.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/playbook-tags.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,68 +19,60 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/playbook-tags.md:8 +#: ../../../docs/playbook-tags.md:1 msgid "Playbook tags" msgstr "" -#: ../../../docs/playbook-tags.md:10 +#: ../../../docs/playbook-tags.md:3 msgid "The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks." msgstr "" -#: ../../../docs/playbook-tags.md:12 -msgid "The general command syntax is:" +#: ../../../docs/playbook-tags.md:5 +msgid "The general command syntax is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`" msgstr "" -#: ../../../docs/playbook-tags.md:13 -msgid "(**recommended**) when using `just`: `just run-tags COMMA_SEPARATED_TAGS_GO_HERE`" -msgstr "" - -#: ../../../docs/playbook-tags.md:14 -msgid "when not using `just`: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`" -msgstr "" - -#: ../../../docs/playbook-tags.md:16 +#: ../../../docs/playbook-tags.md:7 msgid "Here are some playbook tags that you should be familiar with:" msgstr "" -#: ../../../docs/playbook-tags.md:18 +#: ../../../docs/playbook-tags.md:9 msgid "`setup-all` — runs all setup tasks (installation and uninstallation) for all components, but does not start/restart services" msgstr "" -#: ../../../docs/playbook-tags.md:20 +#: ../../../docs/playbook-tags.md:11 msgid "`install-all` — like `setup-all`, but skips uninstallation tasks. Useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove components, you'd need to run `setup-all` though, or these components will still remain installed" msgstr "" -#: ../../../docs/playbook-tags.md:22 +#: ../../../docs/playbook-tags.md:13 msgid "`setup-SERVICE` (e.g. `setup-postmoogle`) — runs the setup tasks only for a given role, but does not start/restart services. You can discover these additional tags in each role (`roles/**/tasks/main.yml`). Running per-component setup tasks is **not recommended**, as components sometimes depend on each other and running just the setup tasks for a given component may not be enough. For example, setting up the [mautrix-telegram bridge](configuring-playbook-bridge-mautrix-telegram.md), in addition to the `setup-mautrix-telegram` tag, requires database changes (the `setup-postgres` tag) as well as reverse-proxy changes (the `setup-nginx-proxy` tag)." msgstr "" -#: ../../../docs/playbook-tags.md:24 +#: ../../../docs/playbook-tags.md:15 msgid "`install-SERVICE` (e.g. `install-postmoogle`) — like `setup-SERVICE`, but skips uninstallation tasks. See `install-all` above for additional information." msgstr "" -#: ../../../docs/playbook-tags.md:26 +#: ../../../docs/playbook-tags.md:17 msgid "`start` — starts all systemd services and makes them start automatically in the future" msgstr "" -#: ../../../docs/playbook-tags.md:28 +#: ../../../docs/playbook-tags.md:19 msgid "`stop` — stops all systemd services" msgstr "" -#: ../../../docs/playbook-tags.md:30 -msgid "`ensure-matrix-users-created` or its alias `ensure-users-created` — a special tag which ensures that all special users needed by the playbook (for bots, etc.) are created. See the variable `matrix_user_creator_users_auto` on [`group_vars/matrix_servers`](../group_vars/matrix_servers) for actual values of users which running this tag can create by default." +#: ../../../docs/playbook-tags.md:21 +msgid "`ensure-matrix-users-created` — a special tag which ensures that all special users needed by the playbook (for bots, etc.) are created" msgstr "" -#: ../../../docs/playbook-tags.md:32 +#: ../../../docs/playbook-tags.md:23 msgid "**Notes**:" msgstr "" -#: ../../../docs/playbook-tags.md:33 +#: ../../../docs/playbook-tags.md:24 msgid "`setup-*` tags and `install-*` tags **do not start services** automatically, because you may wish to do things before starting services, such as importing a database dump, restoring data from another server, etc." msgstr "" -#: ../../../docs/playbook-tags.md:34 +#: ../../../docs/playbook-tags.md:25 msgid "Please be careful not to confuse the playbook tags with the `just` shortcut commands (\"recipes\"). For details about `just` commands, see: [Running `just` commands](just.md)" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/prerequisites.po b/i18n/locales/bg/LC_MESSAGES/docs/prerequisites.po index 78ef1dade..08e6a0ce8 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/prerequisites.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/prerequisites.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,124 +19,148 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/prerequisites.md:12 +#: ../../../docs/prerequisites.md:1 msgid "Prerequisites" msgstr "" -#: ../../../docs/prerequisites.md:14 -msgid "Prerequisites > [Configuring DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)" +#: ../../../docs/prerequisites.md:3 +msgid "Prerequisites > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)" msgstr "" -#: ../../../docs/prerequisites.md:16 +#: ../../../docs/prerequisites.md:5 msgid "To install Matrix services using this Ansible playbook, you need to prepare several requirements both on your local computer (where you will run the playbook to configure the server) and the server (where the playbook will install the Matrix services for you). **These requirements need to be set up manually** before proceeding to the next step." msgstr "" -#: ../../../docs/prerequisites.md:18 +#: ../../../docs/prerequisites.md:7 msgid "We will be using `example.com` as the domain in the following instruction. Please remember to replace it with your own domain before running any commands." msgstr "" -#: ../../../docs/prerequisites.md:20 +#: ../../../docs/prerequisites.md:9 msgid "**Note**: if you do not have an existing Matrix server and want to start quickly with \"opinionated defaults\", we suggest you to follow ⚡ **[Quick start](quick-start.md)** installation guide." msgstr "" -#: ../../../docs/prerequisites.md:22 +#: ../../../docs/prerequisites.md:11 msgid "Your local computer" msgstr "" -#: ../../../docs/prerequisites.md:24 +#: ../../../docs/prerequisites.md:13 msgid "[Ansible](http://ansible.com/) program. It's used to run this playbook and configures your server for you. Take a look at [our guide about Ansible](ansible.md) for more information, as well as [version requirements](ansible.md#supported-ansible-versions) and alternative ways to run Ansible." msgstr "" -#: ../../../docs/prerequisites.md:26 +#: ../../../docs/prerequisites.md:15 +msgid "[passlib](https://passlib.readthedocs.io/en/stable/index.html) Python library. See [this official documentation](https://passlib.readthedocs.io/en/stable/install.html#installation-instructions) for an instruction to install it. On most distros, you need to install some `python-passlib` or `py3-passlib` package, etc." +msgstr "" + +#: ../../../docs/prerequisites.md:17 msgid "[`git`](https://git-scm.com/) as the recommended way to download the playbook. `git` may also be required on the server if you will be [self-building](self-building.md) components." msgstr "" -#: ../../../docs/prerequisites.md:28 -msgid "[`just`](https://github.com/casey/just) for running `just roles`, `just update`, etc. (see [`justfile`](../justfile)), although you can also run these commands manually. Take a look at this documentation for more information: [Running `just` commands](just.md)." +#: ../../../docs/prerequisites.md:19 +msgid "[`just`](https://github.com/casey/just) for running `just roles`, `just update`, etc. (see [`justfile`](../justfile)), although you can also run these commands manually. Take at look at this documentation for more information: [Running `just` commands](just.md)." msgstr "" -#: ../../../docs/prerequisites.md:30 +#: ../../../docs/prerequisites.md:21 msgid "Strong password (random strings) generator. The playbook often requires you to create a strong password and use it for settings on `vars.yml`, components, etc. As any tools should be fine, this playbook has adopted [`pwgen`](https://linux.die.net/man/1/pwgen) (running `pwgen -s 64 1`). [Password Tech](https://pwgen-win.sourceforge.io/), formerly known as \"PWGen for Windows\", is available as free and open source password generator for Windows. Generally, using a random generator available on the internet is not recommended." msgstr "" -#: ../../../docs/prerequisites.md:32 +#: ../../../docs/prerequisites.md:23 msgid "Server" msgstr "" -#: ../../../docs/prerequisites.md:34 +#: ../../../docs/prerequisites.md:25 msgid "(Recommended) An **x86** server ([What kind of server specs do I need?](faq.md#what-kind-of-server-specs-do-i-need)) running one of these operating systems that make use of [systemd](https://systemd.io/):" msgstr "" -#: ../../../docs/prerequisites.md:35 +#: ../../../docs/prerequisites.md:26 msgid "**Archlinux**" msgstr "" -#: ../../../docs/prerequisites.md:36 +#: ../../../docs/prerequisites.md:27 msgid "**CentOS**, **Rocky Linux**, **AlmaLinux**, or possibly other RHEL alternatives (although your mileage may vary)" msgstr "" -#: ../../../docs/prerequisites.md:37 +#: ../../../docs/prerequisites.md:28 msgid "**Debian** (10/Buster or newer)" msgstr "" -#: ../../../docs/prerequisites.md:38 +#: ../../../docs/prerequisites.md:29 msgid "**Ubuntu** (18.04 or newer, although [20.04 may be problematic](ansible.md#supported-ansible-versions) if you run the Ansible playbook on it)" msgstr "" -#: ../../../docs/prerequisites.md:40 +#: ../../../docs/prerequisites.md:31 msgid "Generally, newer is better. We only strive to support released stable versions of distributions, not betas or pre-releases. The playbook can take over your whole server or co-exist with other services that you have there." msgstr "" -#: ../../../docs/prerequisites.md:42 +#: ../../../docs/prerequisites.md:33 msgid "This playbook somewhat supports running on non-`amd64` architectures like ARM. See [Alternative Architectures](alternative-architectures.md)." msgstr "" -#: ../../../docs/prerequisites.md:44 +#: ../../../docs/prerequisites.md:35 msgid "If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container." msgstr "" -#: ../../../docs/prerequisites.md:46 +#: ../../../docs/prerequisites.md:37 msgid "`root` access to your server (or a user capable of elevating to `root` via `sudo`)." msgstr "" -#: ../../../docs/prerequisites.md:48 +#: ../../../docs/prerequisites.md:39 msgid "[Python](https://www.python.org/). Most distributions install Python by default, but some don't (e.g. Ubuntu 18.04) and require manual installation (something like `apt-get install python3`). On some distros, Ansible may incorrectly [detect the Python version](https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html) (2 vs 3) and you may need to explicitly specify the interpreter path in `inventory/hosts` during installation (e.g. `ansible_python_interpreter=/usr/bin/python3`)" msgstr "" -#: ../../../docs/prerequisites.md:50 -msgid "[sudo](https://www.sudo.ws/), even when you've configured Ansible to log in as `root`, because this Ansible playbook sometimes uses the Ansible [become](https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_privilege_escalation.html) module to perform tasks as another user (e.g. `matrix`) and the `become` module's default implementation uses `sudo`. Some distributions, like a minimal Debian net install, do not include the `sudo` package by default." +#: ../../../docs/prerequisites.md:41 +msgid "[sudo](https://www.sudo.ws/), even when you've configured Ansible to log in as `root`. Some distributions, like a minimal Debian net install, do not include the `sudo` package by default." msgstr "" -#: ../../../docs/prerequisites.md:52 +#: ../../../docs/prerequisites.md:43 msgid "An HTTPS-capable web server at the base domain name (`example.com`) which is capable of serving static files. Unless you decide to [Serve the base domain from the Matrix server](configuring-playbook-base-domain-serving.md) or alternatively, to use DNS SRV records for [Server Delegation](howto-server-delegation.md)." msgstr "" -#: ../../../docs/prerequisites.md:54 +#: ../../../docs/prerequisites.md:45 msgid "Properly configured DNS records for `example.com` (details in [Configuring DNS](configuring-dns.md))." msgstr "" -#: ../../../docs/prerequisites.md:56 +#: ../../../docs/prerequisites.md:47 msgid "Some TCP/UDP ports open. This playbook (actually [Docker itself](https://docs.docker.com/network/iptables/)) configures the server's internal firewall for you. In most cases, you don't need to do anything special. But **if your server is running behind another firewall**, you'd need to open these ports:" msgstr "" -#: ../../../docs/prerequisites.md:58 +#: ../../../docs/prerequisites.md:49 msgid "`80/tcp`: HTTP webserver" msgstr "" -#: ../../../docs/prerequisites.md:59 +#: ../../../docs/prerequisites.md:50 msgid "`443/tcp` and `443/udp`: HTTPS webserver" msgstr "" -#: ../../../docs/prerequisites.md:60 +#: ../../../docs/prerequisites.md:51 +msgid "`3478/tcp`: TURN over TCP (used by coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:52 +msgid "`3478/udp`: TURN over UDP (used by coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:53 +msgid "`5349/tcp`: TURN over TCP (used by coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:54 +msgid "`5349/udp`: TURN over UDP (used by coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:55 msgid "`8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. Some components like [Matrix User Verification Service](configuring-playbook-user-verification-service.md#open-matrix-federation-port) require this port to be opened **even with federation disabled**." msgstr "" -#: ../../../docs/prerequisites.md:61 +#: ../../../docs/prerequisites.md:56 +msgid "the range `49152-49172/udp`: TURN over UDP" +msgstr "" + +#: ../../../docs/prerequisites.md:57 msgid "potentially some other ports, depending on the additional (non-default) services that you enable in the **configuring the playbook** step (later on). Consult each service's documentation page in `docs/` for that." msgstr "" -#: ../../../docs/prerequisites.md:65 +#: ../../../docs/prerequisites.md:61 msgid "[▶️](configuring-dns.md) When ready to proceed, continue with [Configuring DNS](configuring-dns.md)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/quick-start.po b/i18n/locales/bg/LC_MESSAGES/docs/quick-start.po index a5c73bb48..fc8f45f9c 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/quick-start.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/quick-start.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: 2024-12-20 15:23+0200\n" "Last-Translator: \n" "Language: bg\n" @@ -19,82 +19,81 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/quick-start.md:7 +#: ../../../docs/quick-start.md:1 msgid "Quick start" msgstr "Бърза инсталация" -#: ../../../docs/quick-start.md:15 +#: ../../../docs/quick-start.md:9 msgid "This page explains how to use this Ansible playbook to install Matrix services on your server with a minimal set of core services." msgstr "Тази страница показва как да използвате Ansible плейбука за да инсталирате минимален брой от важните Matrix услуги на ваш собствен сървър." -#: ../../../docs/quick-start.md:17 +#: ../../../docs/quick-start.md:11 msgid "We will be using `example.com` as the \"base domain\" in the following instruction." msgstr "Ще използваме `example.com` като \"базов домейн\" в инструкциите по-долу." -#: ../../../docs/quick-start.md:19 +#: ../../../docs/quick-start.md:13 msgid "By following the instruction on this page, you will set up:" msgstr "Следвайки инструкциите на тази страница, ще настройте:" -#: ../../../docs/quick-start.md:21 +#: ../../../docs/quick-start.md:15 msgid "**your own Matrix server** on a `matrix.example.com` server, which is configured to present itself as `example.com`" msgstr "**ваш собствен Matrix сървър** на `matrix.example.com` сървъра, който е настроен да се представя за `example.com`" -#: ../../../docs/quick-start.md:22 +#: ../../../docs/quick-start.md:16 msgid "**your user account** like `@alice:example.com` on the server" msgstr "**ваш потребителски профил** като `@alice:example.com` на сървъра" -#: ../../../docs/quick-start.md:23 +#: ../../../docs/quick-start.md:17 msgid "a **self-hosted Matrix client**, [Element Web](configuring-playbook-client-element-web.md) with the default subdomain at `element.example.com`" msgstr "**самостоятелно-хостван Matrix клиент**, [Element Web](configuring-playbook-client-element-web.md) на поддомейн по подразбиране `element.example.com`" -#: ../../../docs/quick-start.md:24 +#: ../../../docs/quick-start.md:18 msgid "Matrix delegation, so that your `matrix.example.com` server (presenting itself as `example.com`) can join the Matrix Federation and communicate with any other server in the Matrix network" msgstr "Matrix делегиране, така че `matrix.example.com` сървърът ви (представящ се за `example.com`) да може да се включи в Matrix Федерацията и да комуникира с други сървъри в Matrix мрежата" -#: ../../../docs/quick-start.md:26 +#: ../../../docs/quick-start.md:20 msgid "Please remember to replace `example.com` with your own domain before running any commands." msgstr "Моля, помнете да замените `example.com` със собствения си домейн преди да изпълните командите по-долу." -#: ../../../docs/quick-start.md:28 +#: ../../../docs/quick-start.md:22 msgid "Prerequisites" msgstr "Предварителни условия" -#: ../../../docs/quick-start.md:30 +#: ../../../docs/quick-start.md:24 msgid "This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Prerequisites](prerequisites.md)" msgstr "Този раздел е оптимизиран за този наръчник за бърза инсталация на базата на следната страница от пълната документация: [Предварителни условия](prerequisites.md)" -#: ../../../docs/quick-start.md:32 +#: ../../../docs/quick-start.md:26 msgid "At first, **check prerequisites** and prepare for installation by setting up programs [on your own computer](prerequisites.md#your-local-computer) and [your server](prerequisites.md#server). You also need `root` access on your server (a user that could elevate to `root` via `sudo` also works)." msgstr "" -#: ../../../docs/quick-start.md:34 +#: ../../../docs/quick-start.md:28 msgid "When preparing your server, make sure to check [the server specs you need](faq.md#what-kind-of-server-specs-do-i-need). We recommend starting with a server having at least 2GB of memory." msgstr "" -#: ../../../docs/quick-start.md:40 +#: ../../../docs/quick-start.md:34 msgid "If you encounter an error during installation, please make sure that you have installed and configured programs correctly." msgstr "" -#: ../../../docs/quick-start.md:42 +#: ../../../docs/quick-start.md:36 msgid "One of the main reasons of basic errors is using an incompatible version of required software such as Ansible. Take a look at [our guide about Ansible](ansible.md) for more information. In short: installing the latest available version is recommended." msgstr "" -#: ../../../docs/quick-start.md:44 +#: ../../../docs/quick-start.md:38 msgid "Configure your DNS settings" msgstr "" -#: ../../../docs/quick-start.md:46 -#, fuzzy -msgid "This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Configuring DNS settings](configuring-dns.md)" +#: ../../../docs/quick-start.md:40 +msgid "This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Configuring your DNS settings](configuring-dns.md)" msgstr "Този раздел е оптимизиран за този наръчник за бърза инсталация на базата на следната страница от пълната документация: [Конфигуриране на DNS настройките](configuring-dns.md)" -#: ../../../docs/quick-start.md:48 +#: ../../../docs/quick-start.md:42 msgid "After installing and configuring prerequisites, you will need to **configure DNS records**." msgstr "" -#: ../../../docs/quick-start.md:50 +#: ../../../docs/quick-start.md:44 msgid "To configure Matrix services in the default settings, go to your DNS service provider, and adjust DNS records as below." msgstr "" @@ -135,17 +134,7 @@ msgid "-" msgstr "-" #: ../../../docs/quick-start.md -#, fuzzy -msgid "`matrix-server-IPv4`" -msgstr "`IP-на-matrix-сървъра`" - -#: ../../../docs/quick-start.md -msgid "AAAA" -msgstr "" - -#: ../../../docs/quick-start.md -#, fuzzy -msgid "`matrix-server-IPv6`" +msgid "`matrix-server-IP`" msgstr "`IP-на-matrix-сървъра`" #: ../../../docs/quick-start.md @@ -160,291 +149,286 @@ msgstr "`element`" msgid "`matrix.example.com`" msgstr "`matrix.example.com`" -#: ../../../docs/quick-start.md:58 -#, fuzzy -msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IPv4/IPv6 address." +#: ../../../docs/quick-start.md:51 +msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)." msgstr "Както показва таблицата, необходимо е да създадете 2 поддомейна (`matrix.example.com` и `element.example.com`) и да ги насочите към IP адреса на сървъра (чрез DNS `A` запис или `CNAME` запис)." -#: ../../../docs/quick-start.md:60 -msgid "If you don't have IPv6 connectivity yet, you can skip the `AAAA` record. For more details about IPv6, see the [Configuring IPv6](./configuring-ipv6.md) documentation page." -msgstr "" - -#: ../../../docs/quick-start.md:62 +#: ../../../docs/quick-start.md:53 msgid "It might take some time for the DNS records to propagate after creation." msgstr "Може да отнеме известно време след създаване на DNS записите докато се отразят." -#: ../../../docs/quick-start.md:64 +#: ../../../docs/quick-start.md:55 msgid "**💡 Note**: if you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\"" msgstr "" -#: ../../../docs/quick-start.md:66 +#: ../../../docs/quick-start.md:57 msgid "Get the playbook" msgstr "" -#: ../../../docs/quick-start.md:68 +#: ../../../docs/quick-start.md:59 msgid "This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Getting the playbook](getting-the-playbook.md)" msgstr "Този раздел е оптимизиран за този наръчник за бърза инсталация на базата на следната страница от пълната документация: [Изтегляне на плейбука](getting-the-playbook.md)" -#: ../../../docs/quick-start.md:70 +#: ../../../docs/quick-start.md:61 msgid "Next, let's **get the playbook's source code**." msgstr "" -#: ../../../docs/quick-start.md:72 +#: ../../../docs/quick-start.md:63 msgid "We recommend to do so with [git](https://git-scm.com/) as it enables you to keep it up to date with the latest source code. While it is possible to download the playbook as a ZIP archive, it is not recommended." msgstr "" -#: ../../../docs/quick-start.md:74 +#: ../../../docs/quick-start.md:65 msgid "To get the playbook with git, install git on your computer, go to a directory, and run the command:" msgstr "" -#: ../../../docs/quick-start.md:80 +#: ../../../docs/quick-start.md:71 msgid "It will fetch the playbook to a new `matrix-docker-ansible-deploy` directory underneath the directory you are currently in." msgstr "" -#: ../../../docs/quick-start.md:82 +#: ../../../docs/quick-start.md:73 msgid "Configure the playbook" msgstr "" -#: ../../../docs/quick-start.md:84 +#: ../../../docs/quick-start.md:75 msgid "This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Configuring the playbook](configuring-playbook.md)" msgstr "Този раздел е оптимизиран за този наръчник за бърза инсталация на базата на следната страница от пълната документация: [Конфигуриране на плейбука](configuring-playbook.md)" -#: ../../../docs/quick-start.md:86 +#: ../../../docs/quick-start.md:77 msgid "Now that the playbook was fetched, it is time to **configure** it per your needs." msgstr "" -#: ../../../docs/quick-start.md:88 +#: ../../../docs/quick-start.md:79 msgid "To install Matrix services with this playbook, you would at least need 2 configuration files." msgstr "" -#: ../../../docs/quick-start.md:90 +#: ../../../docs/quick-start.md:81 msgid "For your convenience, we have prepared example files of them ([`vars.yml`](../examples/vars.yml) and [`hosts`](../examples/hosts))." msgstr "" -#: ../../../docs/quick-start.md:92 +#: ../../../docs/quick-start.md:83 msgid "To start quickly based on these example files, go into the `matrix-docker-ansible-deploy` directory and follow the instructions below:" msgstr "" -#: ../../../docs/quick-start.md:94 +#: ../../../docs/quick-start.md:85 msgid "Create a directory to hold your configuration: `mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\"" msgstr "" -#: ../../../docs/quick-start.md:95 +#: ../../../docs/quick-start.md:86 msgid "Copy the sample configuration file: `cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`" msgstr "" -#: ../../../docs/quick-start.md:96 +#: ../../../docs/quick-start.md:87 msgid "Copy the sample inventory hosts file: `cp examples/hosts inventory/hosts`" msgstr "" -#: ../../../docs/quick-start.md:97 +#: ../../../docs/quick-start.md:88 msgid "Edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`)" msgstr "" -#: ../../../docs/quick-start.md:98 +#: ../../../docs/quick-start.md:89 msgid "Edit the inventory hosts file (`inventory/hosts`)" msgstr "" -#: ../../../docs/quick-start.md:100 +#: ../../../docs/quick-start.md:91 msgid "Before editing these 2 files, make sure to read explanations on them to understand what needs to be configured." msgstr "" -#: ../../../docs/quick-start.md:102 +#: ../../../docs/quick-start.md:93 msgid "**💡 Notes:**" msgstr "" -#: ../../../docs/quick-start.md:103 +#: ../../../docs/quick-start.md:94 msgid "If you are not in control of anything on the base domain, you would need to set additional configuration on `vars.yml`. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ." msgstr "" -#: ../../../docs/quick-start.md:104 +#: ../../../docs/quick-start.md:95 msgid "Certain configuration decisions (like the base domain configured in `matrix_domain` and homeserver implementation configured in `matrix_homeserver_implementation`) are final. If you make the wrong choice and wish to change it, you'll have to run the Uninstalling step and start over." msgstr "" -#: ../../../docs/quick-start.md:105 +#: ../../../docs/quick-start.md:96 msgid "Instead of configuring a lot of things all at once, we recommend starting with the basic (default) settings in order to get yourself familiar with how the playbook works. After making sure that everything works as expected, you can add (and remove) advanced settings / features and run the playbook as many times as you wish." msgstr "" -#: ../../../docs/quick-start.md:107 +#: ../../../docs/quick-start.md:98 msgid "Install" msgstr "" -#: ../../../docs/quick-start.md:109 +#: ../../../docs/quick-start.md:100 msgid "This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Installing](installing.md)" msgstr "Този раздел е оптимизиран за този наръчник за бърза инсталация на базата на следната страница от пълната документация: [Инсталиране](installing.md)" -#: ../../../docs/quick-start.md:111 +#: ../../../docs/quick-start.md:102 msgid "After editing `vars.yml` and `hosts` files, let's start the **installation** procedure." msgstr "" -#: ../../../docs/quick-start.md:113 +#: ../../../docs/quick-start.md:104 msgid "Update Ansible roles" msgstr "" -#: ../../../docs/quick-start.md:115 +#: ../../../docs/quick-start.md:106 msgid "Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside." msgstr "" -#: ../../../docs/quick-start.md:117 +#: ../../../docs/quick-start.md:108 msgid "To update your playbook directory and all upstream Ansible roles, run:" msgstr "" -#: ../../../docs/quick-start.md:119 +#: ../../../docs/quick-start.md:110 msgid "either: `just update`" msgstr "" -#: ../../../docs/quick-start.md:120 +#: ../../../docs/quick-start.md:111 msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)" msgstr "" -#: ../../../docs/quick-start.md:122 +#: ../../../docs/quick-start.md:113 msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`" msgstr "" -#: ../../../docs/quick-start.md:124 +#: ../../../docs/quick-start.md:115 msgid "Run installation command" msgstr "" -#: ../../../docs/quick-start.md:126 +#: ../../../docs/quick-start.md:117 msgid "Then, run the command below to start installation:" msgstr "" -#: ../../../docs/quick-start.md:132 +#: ../../../docs/quick-start.md:123 msgid "If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the command." msgstr "" -#: ../../../docs/quick-start.md:134 +#: ../../../docs/quick-start.md:125 msgid "If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to the command." msgstr "" -#: ../../../docs/quick-start.md:136 +#: ../../../docs/quick-start.md:127 msgid "Wait until the command completes. If it's all green, everything should be running properly." msgstr "" -#: ../../../docs/quick-start.md:138 +#: ../../../docs/quick-start.md:129 msgid "Create your user account" msgstr "" -#: ../../../docs/quick-start.md:140 +#: ../../../docs/quick-start.md:131 msgid "This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Registering users](registering-users.md)" msgstr "" -#: ../../../docs/quick-start.md:142 +#: ../../../docs/quick-start.md:133 msgid "As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server." msgstr "" -#: ../../../docs/quick-start.md:144 +#: ../../../docs/quick-start.md:135 msgid "To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer." msgstr "" -#: ../../../docs/quick-start.md:146 +#: ../../../docs/quick-start.md:137 msgid "**💡 Notes**:" msgstr "" -#: ../../../docs/quick-start.md:147 +#: ../../../docs/quick-start.md:138 msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`" msgstr "" -#: ../../../docs/quick-start.md:148 +#: ../../../docs/quick-start.md:139 msgid "For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)" msgstr "" -#: ../../../docs/quick-start.md:160 +#: ../../../docs/quick-start.md:151 msgid "Finalize server installation" msgstr "" -#: ../../../docs/quick-start.md:162 +#: ../../../docs/quick-start.md:153 msgid "This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Server Delegation](howto-server-delegation.md)" msgstr "" -#: ../../../docs/quick-start.md:164 +#: ../../../docs/quick-start.md:155 msgid "Now that you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network." msgstr "" -#: ../../../docs/quick-start.md:166 +#: ../../../docs/quick-start.md:157 msgid "**This is required for federation to work!** Without a proper configuration, your server will effectively not be part of the Matrix network." msgstr "" -#: ../../../docs/quick-start.md:168 +#: ../../../docs/quick-start.md:159 msgid "To configure the delegation, you have these two options. Choose one of them according to your situation." msgstr "" -#: ../../../docs/quick-start.md:170 +#: ../../../docs/quick-start.md:161 msgid "If you can afford to point the base domain at the Matrix server, follow the instruction below which guides you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server." msgstr "" -#: ../../../docs/quick-start.md:171 +#: ../../../docs/quick-start.md:162 msgid "Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot \"serve the base domain\" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server)." msgstr "" -#: ../../../docs/quick-start.md:173 +#: ../../../docs/quick-start.md:164 msgid "To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/quick-start.md:179 +#: ../../../docs/quick-start.md:170 msgid "After configuring the playbook, run the command below and wait until it finishes:" msgstr "" -#: ../../../docs/quick-start.md:185 +#: ../../../docs/quick-start.md:176 msgid "💡 Running the `install-matrix-static-files` playbook tag (as done here) is an optimized version of running [the full setup command](#run-installation-command)." msgstr "" -#: ../../../docs/quick-start.md:187 +#: ../../../docs/quick-start.md:178 msgid "After the command finishes, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain." msgstr "" -#: ../../../docs/quick-start.md:189 +#: ../../../docs/quick-start.md:180 msgid "Re-run the full setup command any time" msgstr "" -#: ../../../docs/quick-start.md:191 +#: ../../../docs/quick-start.md:182 msgid "If you think something is wrong with the server configuration, feel free to re-run the setup command any time:" msgstr "" -#: ../../../docs/quick-start.md:197 +#: ../../../docs/quick-start.md:188 msgid "Log in to your user account" msgstr "" -#: ../../../docs/quick-start.md:199 +#: ../../../docs/quick-start.md:190 msgid "Finally, let's make sure that you can log in to the created account with the specified password." msgstr "" -#: ../../../docs/quick-start.md:201 +#: ../../../docs/quick-start.md:192 msgid "You should be able to log in to it with your own [Element Web](configuring-playbook-client-element-web.md) client which you have set up at `element.example.com` by running the playbook. Open the URL (`https://element.example.com`) in a web browser and enter your credentials to log in." msgstr "" -#: ../../../docs/quick-start.md:203 -msgid "**If you successfully logged in to your account, the installation and configuration have completed successfully**🎉" +#: ../../../docs/quick-start.md:194 +msgid "**If you successfully logged in to your account, installing and configuring is complete**🎉" msgstr "" -#: ../../../docs/quick-start.md:205 +#: ../../../docs/quick-start.md:196 msgid "Come say Hi👋 in our support room — [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting." msgstr "" -#: ../../../docs/quick-start.md:207 +#: ../../../docs/quick-start.md:198 msgid "Things to do next" msgstr "" -#: ../../../docs/quick-start.md:209 +#: ../../../docs/quick-start.md:200 msgid "Once you get familiar with the playbook, you might probably want to set up additional services such as a bridge on your server." msgstr "" -#: ../../../docs/quick-start.md:211 +#: ../../../docs/quick-start.md:202 msgid "As this page intends to be a quick start guide which explains how to start the core Matrix services, it does not cover a topic like how to set them up. Take a look at the list of [things to do next](installing.md#things-to-do-next) to learn more." msgstr "" -#: ../../../docs/quick-start.md:213 +#: ../../../docs/quick-start.md:204 msgid "⚠️Keep the playbook and services up-to-date" msgstr "" -#: ../../../docs/quick-start.md:215 +#: ../../../docs/quick-start.md:206 msgid "While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**." msgstr "" -#: ../../../docs/quick-start.md:217 +#: ../../../docs/quick-start.md:208 msgid "Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date." msgstr "" -#: ../../../docs/quick-start.md:219 -msgid "For more information about upgrading or maintaining services with the playbook, take a look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)" +#: ../../../docs/quick-start.md:210 +msgid "For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/uninstalling.po b/i18n/locales/bg/LC_MESSAGES/docs/uninstalling.po index de76e41f3..b16bebd9f 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/uninstalling.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/uninstalling.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,65 +19,64 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/uninstalling.md:9 +#: ../../../docs/uninstalling.md:1 msgid "Uninstalling" msgstr "" -#: ../../../docs/uninstalling.md:11 -msgid "[!WARNING]" +#: ../../../docs/uninstalling.md:3 +msgid "⚠️ **Warnings**:" msgstr "" -#: ../../../docs/uninstalling.md:12 +#: ../../../docs/uninstalling.md:4 msgid "If your server federates with others, make sure to **leave any federated rooms before nuking your Matrix server's data**. Otherwise, the next time you set up a Matrix server for this domain (regardless of the installation method you use), you'll encounter trouble federating." msgstr "" -#: ../../../docs/uninstalling.md:13 +#: ../../../docs/uninstalling.md:5 msgid "If you have some trouble with your installation, you can just [re-run the playbook](installing.md) and it will try to set things up again. **Uninstalling and then installing anew rarely solves anything**." msgstr "" -#: ../../../docs/uninstalling.md:15 +#: ../../../docs/uninstalling.md:9 msgid "Uninstalling using a script" msgstr "" -#: ../../../docs/uninstalling.md:17 +#: ../../../docs/uninstalling.md:11 msgid "Installing places a `/matrix/bin/remove-all` script on the server." msgstr "" -#: ../../../docs/uninstalling.md:19 +#: ../../../docs/uninstalling.md:13 msgid "You can run it to to have it uninstall things for you automatically (see below). **Use with caution!**" msgstr "" -#: ../../../docs/uninstalling.md:21 +#: ../../../docs/uninstalling.md:15 msgid "Uninstalling manually" msgstr "" -#: ../../../docs/uninstalling.md:23 +#: ../../../docs/uninstalling.md:17 msgid "If you prefer to uninstall manually, run these commands (most are meant to be executed on the Matrix server itself):" msgstr "" -#: ../../../docs/uninstalling.md:25 +#: ../../../docs/uninstalling.md:19 msgid "ensure all Matrix services are stopped: `ansible-playbook -i inventory/hosts setup.yml --tags=stop` (if you can't get Ansible working to run this command, you can run `systemctl stop 'matrix*'` manually on the server)" msgstr "" -#: ../../../docs/uninstalling.md:27 -#, python-brace-format +#: ../../../docs/uninstalling.md:21 msgid "delete the Matrix-related systemd `.service` and `.timer` files (`rm -f /etc/systemd/system/matrix*.{service,timer}`) and reload systemd (`systemctl daemon-reload`)" msgstr "" -#: ../../../docs/uninstalling.md:29 +#: ../../../docs/uninstalling.md:23 msgid "delete some cached Docker images (`docker system prune -a`) or just delete them all (`docker rmi $(docker images -aq)`)" msgstr "" -#: ../../../docs/uninstalling.md:31 +#: ../../../docs/uninstalling.md:25 msgid "delete the Docker networks: `docker network rm matrix matrix-coturn` (might have been deleted already if you ran the `docker system prune` command)" msgstr "" -#: ../../../docs/uninstalling.md:33 +#: ../../../docs/uninstalling.md:27 msgid "uninstall Docker itself, if necessary" msgstr "" -#: ../../../docs/uninstalling.md:35 +#: ../../../docs/uninstalling.md:29 msgid "delete the `/matrix` directory (`rm -rf /matrix`)" msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/updating-users-passwords.po b/i18n/locales/bg/LC_MESSAGES/docs/updating-users-passwords.po index 7ee3aa35e..0d3caf7c2 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/updating-users-passwords.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/updating-users-passwords.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -19,76 +19,76 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/updating-users-passwords.md:13 +#: ../../../docs/updating-users-passwords.md:1 msgid "Updating users passwords" msgstr "" -#: ../../../docs/updating-users-passwords.md:15 +#: ../../../docs/updating-users-passwords.md:3 msgid "Option 1 (if you are using the integrated Postgres database):" msgstr "" -#: ../../../docs/updating-users-passwords.md:17 +#: ../../../docs/updating-users-passwords.md:5 msgid "**Notes**:" msgstr "" -#: ../../../docs/updating-users-passwords.md:18 +#: ../../../docs/updating-users-passwords.md:6 msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`" msgstr "" -#: ../../../docs/updating-users-passwords.md:19 +#: ../../../docs/updating-users-passwords.md:7 msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)" msgstr "" -#: ../../../docs/updating-users-passwords.md:21 +#: ../../../docs/updating-users-passwords.md:9 msgid "You can reset a user's password via the Ansible playbook:" msgstr "" -#: ../../../docs/updating-users-passwords.md:27 +#: ../../../docs/updating-users-passwords.md:15 msgid "**You can then log in with that user** via Element Web that this playbook has created for you at a URL like this: `https://element.example.com/`." msgstr "" -#: ../../../docs/updating-users-passwords.md:29 +#: ../../../docs/updating-users-passwords.md:17 msgid "Option 2 (if you are using an external Postgres server):" msgstr "" -#: ../../../docs/updating-users-passwords.md:31 +#: ../../../docs/updating-users-passwords.md:19 msgid "You can manually generate the password hash by using the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#finalize-the-installation):" msgstr "" -#: ../../../docs/updating-users-passwords.md:37 -msgid "and then connecting to the Postgres server and executing:" +#: ../../../docs/updating-users-passwords.md:25 +msgid "and then connecting to the postgres server and executing:" msgstr "" -#: ../../../docs/updating-users-passwords.md:43 +#: ../../../docs/updating-users-passwords.md:31 msgid "where `` is the hash returned by the docker command above." msgstr "" -#: ../../../docs/updating-users-passwords.md:45 +#: ../../../docs/updating-users-passwords.md:33 msgid "Option 3:" msgstr "" -#: ../../../docs/updating-users-passwords.md:47 +#: ../../../docs/updating-users-passwords.md:35 msgid "Use the Synapse User Admin API as described here: https://github.com/element-hq/synapse/blob/master/docs/admin_api/user_admin_api.rst#reset-password" msgstr "" -#: ../../../docs/updating-users-passwords.md:49 +#: ../../../docs/updating-users-passwords.md:37 msgid "This requires an [access token](obtaining-access-tokens.md) from a server admin account. *This method will also log the user out of all of their clients while the other options do not.*" msgstr "" -#: ../../../docs/updating-users-passwords.md:51 +#: ../../../docs/updating-users-passwords.md:39 msgid "If you didn't make your account a server admin when you created it, you can learn how to switch it now by reading about it in [Adding/Removing Administrator privileges to an existing user in Synapse](registering-users.md#addingremoving-administrator-privileges-to-an-existing-user-in-synapse)." msgstr "" -#: ../../../docs/updating-users-passwords.md:53 +#: ../../../docs/updating-users-passwords.md:41 msgid "Example:" msgstr "" -#: ../../../docs/updating-users-passwords.md:55 +#: ../../../docs/updating-users-passwords.md:43 msgid "To set @alice:example.com's password to `correct_horse_battery_staple` you could use this curl command:" msgstr "" -#: ../../../docs/updating-users-passwords.md:61 +#: ../../../docs/updating-users-passwords.md:49 msgid "Make sure to replace `ACCESS_TOKEN_HERE` with the access token of the server admin account." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/i18n/README.po b/i18n/locales/bg/LC_MESSAGES/i18n/README.po index 61d4c8ec2..c5e6d158e 100644 --- a/i18n/locales/bg/LC_MESSAGES/i18n/README.po +++ b/i18n/locales/bg/LC_MESSAGES/i18n/README.po @@ -8,14 +8,14 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2026-02-13 10:32+0000\n" +"POT-Creation-Date: 2024-12-20 15:27+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \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" +"Generated-By: Babel 2.16.0\n" #: ../../README.md:8 msgid "Internationalization" @@ -54,7 +54,7 @@ msgid "[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we p msgstr "" #: ../../README.md:23 -msgid "[.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionally ignore translated results (`translations/` directories) for languages that are still in progress. We only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold." +msgid "[.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionaly ignore translated results (`translations/` directories) for languages taht are still in progress. We only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold." msgstr "" #: ../../README.md:24 diff --git a/i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po b/i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po index 430bc452a..be33e6670 100644 --- a/i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po +++ b/i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,276 +18,276 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../YEAR-IN-REVIEW.md:8 +#: ../../../YEAR-IN-REVIEW.md:1 msgid "2023" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:10 +#: ../../../YEAR-IN-REVIEW.md:3 msgid "2023 was a year filled with many changes for matrix-docker-ansible-deploy. In this post, we're looking backward at some of the major changes that happened this year, as well as taking a glimpse of what's ahead in 2024." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:12 +#: ../../../YEAR-IN-REVIEW.md:5 msgid "2023 is probably [the year of AI](https://journal.everypixel.com/2023-the-year-of-ai), with millions of people jumping aboard [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/chatgpt) train. matrix-docker-ansible-deploy is no stranger to this and 2023 began with a PR from [bertybuttface](https://github.com/bertybuttface) who added support for [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#chatgpt-support)). While OpenAI's chat GPT website was frequently overloaded in the past, their API was up which made using this bot both convenient and more reliable." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:14 -msgid "AI aside, with the playbook's focus being containers, we're **doubling down on being \"container native\"** and becoming more interoperable for people hosting other containers on the Matrix server. In [2022](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/YEAR-IN-REVIEW.md#2022), we've announced a few sibling Ansible playbooks, their use of [Traefik](https://doc.traefik.io/traefik/) and the possibility of matrix-docker-ansible-deploy also switching to this reverse-proxy. This prediction materialized quickly. The **largest change** in the playbook in 2023 happened way back in February - matrix-docker-ansible-deploy [starting the switch from nginx to Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support) and then quickly [making Treafik the default reverse-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#traefik-is-the-default-reverse-proxy-now). As noted in the changelog entries, we envisioned a quick and complete elimination of `matrix-nginx-proxy`, but at the end of 2023, it hasn't happened yet. The playbook is already using Traefik as the front-most reverse-proxy, but nginx (via `matrix-nginx-proxy`) is still around - it has taken a step back and is only used internally for new setups. Work got to a stall due to:" +#: ../../../YEAR-IN-REVIEW.md:7 +msgid "AI aside, with the playbook's focus being containers, we're **doubling down on being \"container native\"** and becoming more interoperable for people hosting other containers on the Matrix server. In [2022](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/YEAR-IN-REVIEW.md#2022), we've announced a few sibling Ansible playbooks, their use of [Traefik](https://doc.traefik.io/traefik/) and the possiblity of matrix-docker-ansible-deploy also switching to this reverse-proxy. This prediction materialized quickly. The **largest change** in the playbook in 2023 happened way back in February - matrix-docker-ansible-deploy [starting the switch from nginx to Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support) and then quickly [making Treafik the default reverse-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#traefik-is-the-default-reverse-proxy-now). As noted in the changelog entries, we envisioned a quick and complete elimination of `matrix-nginx-proxy`, but at the end of 2023, it hasn't happened yet. The playbook is already using Traefik as the front-most reverse-proxy, but nginx (via `matrix-nginx-proxy`) is still around - it has taken a step back and is only used internally for new setups. Work got to a stall due to:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:16 +#: ../../../YEAR-IN-REVIEW.md:9 msgid "complexity: untangling the overly large and messy `matrix-nginx-proxy` component is difficult" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:17 +#: ../../../YEAR-IN-REVIEW.md:10 msgid "the current setup became \"good enough\" because nginx has become an internal implementation detail for those who have migrated to Traefik. Traefik is already the default public reverse-proxy and gives better possibilities to people wishing to run other web-exposed containers on their Matrix server via [Docker Compose](https://docs.docker.com/compose/), other Ansible playbooks like [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) (more about this one, below) or any other way." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:19 +#: ../../../YEAR-IN-REVIEW.md:12 msgid "`matrix-nginx-proxy` is no longer in the way of us being interoperable, but its ugly internal details are still there. It is one more proxy in the long chain of reverse-proxies we have and we'd like to cut it out. This would both make things simpler and also boost performance." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:21 +#: ../../../YEAR-IN-REVIEW.md:14 msgid "The delay in eliminating `matrix-nginx-proxy` has probably been welcome by many existing users who decided to postpone the Traefik migration a bit longer. In 2024, work on eliminating `matrix-nginx-proxy` will continue with rapid pace. People who are still using `matrix-nginx-proxy` as their front-most reverse-proxy will need to rework their setup. About a year of putting it off has been long enough." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:23 +#: ../../../YEAR-IN-REVIEW.md:16 msgid "This large Traefik reverse-proxy change was also accompanied by another internal change which began in 2022, but continued in 2023 - **moving non-Matrix-related roles from being internal to the playbook to living their own life outside of it**. Various roles were made more decoupled and moved outside of the playbook, so that other projects (like the [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook or other Ansible playbooks) could benefit from them. This led to the **death of a few sibling playbooks** ([gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy), [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), [peertube-docker-ansible-deploy](https://github.com/spantaleev/peertube-docker-ansible-deploy), [vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy)), but brought life to something better, which supports all these services and more." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:25 +#: ../../../YEAR-IN-REVIEW.md:18 msgid "[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) is a new Ansible playbook that a few of us (matrix-docker-ansible-deploy contributors) have launched in 2023. It has quickly grown to supports [60+ services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md) and aims to do the same for [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) service hosting, as matrix-docker-ansible-deploy has done for Matrix - providing a clean and secure way to run a bunch of services in containers on a regular server (that is to say, without Kubernetes, etc.). Thanks to Traefik and Ansible role reuse, it's easy to host both mash-playbook services and matrix-docker-ansible-deploy services on the same server - see mash-playbook's [interoperability](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md) documentation page. If you've been looking for a holiday project or your New Year's Resolutions list contains \"self-hosting more services\", then you're welcome to give this new playbook a try and join its Matrix room ([#mash-playbook:devture.com](https://matrix.to/#/#mash-playbook:devture.com))." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:27 +#: ../../../YEAR-IN-REVIEW.md:20 msgid "Because many of the roles are now external to this playbook (defined in the [requirements.yml](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/da27655ef34999fa924bc0a5e641dbd9ba06f133/requirements.yml) file), running `make roles` (or better yet `just roles` via the [just tool](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#support-for-running-commands-via-just)) becomes a necessity each time one pulls playbook updates (`git pull`). Pulling external roles happens via the [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) command-line tool, but if available, the playbook would also use the much faster [agru](https://github.com/etkecc/agru) tool (developed by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) this year)." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:29 +#: ../../../YEAR-IN-REVIEW.md:22 msgid "With the internal (but important) details out of the way, we can now talk more about **new features that landed in matrix-docker-ansible-deploy in 2023**." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:31 +#: ../../../YEAR-IN-REVIEW.md:24 msgid "The following **new** **bridges** were added to the playbook in 2023:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:33 +#: ../../../YEAR-IN-REVIEW.md:26 msgid "(2023-01-11) [mautrix-slack](https://mau.dev/mautrix/slack), thanks to a PR by [Cody Neiman](https://github.com/xangelix) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#mautrix-slack-support))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:34 +#: ../../../YEAR-IN-REVIEW.md:27 msgid "(2023-07-21) [mautrix-gmessages](https://github.com/mautrix/gmessages), thanks to a PR by [Shreyas Ajjarapu](https://github.com/shreyasajj) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#mautrix-gmessages-support))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:35 +#: ../../../YEAR-IN-REVIEW.md:28 msgid "(2023-08-23) [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for Apple iMessage bridging (when combined with the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android phone), thanks to a PR by [Johan Swetzén](https://github.com/jswetzen)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:37 +#: ../../../YEAR-IN-REVIEW.md:30 msgid "This brings the total number of **[bridges that the playbook supports](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/docs/configuring-playbook.md#bridging-other-networks) up to 30**. There are alternative bridge implementations for various networks and protocols, so the number of \"unique bridged networks\" is surely much smaller." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:39 +#: ../../../YEAR-IN-REVIEW.md:32 msgid "A few other **major components and changes** landed in 2023:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:41 +#: ../../../YEAR-IN-REVIEW.md:34 msgid "(2023-02-10) The [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (successor to [Mjolnir](https://github.com/matrix-org/mjolnir)), thanks to a PR by [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#draupnir-moderation-tool-bot-support))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:42 +#: ../../../YEAR-IN-REVIEW.md:35 msgid "(2023-02-10) [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) to add Matrix Authentication Support to our Jitsi setup, thanks to a PR by [Jakob S.](https://github.com/jakicoll) from [zakk gGmbH](https://github.com/zakk-it) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-authentication-support-for-jitsi))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:43 +#: ../../../YEAR-IN-REVIEW.md:36 msgid "(2023-02-25) The [rageshake](https://github.com/matrix-org/rageshake) bug report server, thanks to a PR by [Benjamin Kampmann](https://github.com/gnunicorn) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#rageshake-support))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:44 +#: ../../../YEAR-IN-REVIEW.md:37 msgid "(2023-03-07) [Sliding Sync proxy](https://github.com/matrix-org/sliding-sync) (currently a necessary component for [Element X](https://element.io/labs/element-x) to work), thanks to: [Benjamin Kampmann](https://github.com/gnunicorn) and [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#sliding-sync-proxy-element-x-support))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:45 +#: ../../../YEAR-IN-REVIEW.md:38 msgid "(2023-03-12) synapse-auto-compressor to periodically and automatically run [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#synapse-auto-compressor-support))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:46 +#: ../../../YEAR-IN-REVIEW.md:39 msgid "(2023-07-17) [matrix-media-repo](https://github.com/turt2live/matrix-media-repo),  thanks to a PR by [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-media-repo-support))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:47 +#: ../../../YEAR-IN-REVIEW.md:40 msgid "(2023-08-31) [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client app (fork of [Element Web)](https://github.com/element-hq/element-web), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#schildichat-support))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:48 +#: ../../../YEAR-IN-REVIEW.md:41 msgid "(2023-10-18) Postgres parameters auto-tuning, thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#postgres-parameters-are-automatically-tuned-now))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:49 +#: ../../../YEAR-IN-REVIEW.md:42 msgid "(2023-10-23) Enabling federation of the room directory for Synapse (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#enabling-allow_public_rooms_over_federation-by-default-for-synapse))" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:51 +#: ../../../YEAR-IN-REVIEW.md:44 msgid "The most recent change in the list above (Enabling federation of the room directory for Synapse) has been somewhat **controversial** as it goes against upstream defaults for Synapse. Nevertheless, we believe it **promotes the well-being of the Matrix Federation by improving room discovery**." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:53 +#: ../../../YEAR-IN-REVIEW.md:46 msgid "**Matrix Federation Stats** (containing the percentage of servers publishing their room directory publicly) are posted to [TWIM](https://matrix.org/category/this-week-in-matrix/) each week by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/). The number of servers which [currently published their room directory publicly](https://matrix.org/blog/2023/12/2/this-week-in-matrix-2023-12-22/#matrix-federation-stats) stands at `26.6%`, which is:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:55 +#: ../../../YEAR-IN-REVIEW.md:48 msgid "**2.4% more** than when it was when [first published to TWIM](https://matrix.org/blog/2023/11/03/this-week-in-matrix-2023-11-03/#matrix-federation-stats) (1 month earlier, in November)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:56 +#: ../../../YEAR-IN-REVIEW.md:49 msgid "likely about **15+% more** than from before we flipped the switch (in October)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:58 +#: ../../../YEAR-IN-REVIEW.md:51 msgid "Hopefully, Synapse defaults would also change the same way and we'd see the number of servers publicly listing their room directory grow faster." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:60 +#: ../../../YEAR-IN-REVIEW.md:53 msgid "With this configuration change in place, projects like [MatrixRooms.info](https://matrixrooms.info/) (made by [etke.cc](https://etke.cc/)) and potentially others in the future, can discover, index the metadata (room address, title, topic, number of users, etc.) and make public rooms browsable & searchable across the whole Matrix Federation. It'd be great if users joining Matrix could more easily find interesting communities that match their interests!" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:62 +#: ../../../YEAR-IN-REVIEW.md:55 msgid "On the **media side of things**, besides Jitsi getting better Matrix integration (via the aforementioned Matrix User Verification Service), we've also had some [coturn security tightening](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues) as well as [performance optimizations](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#coturn-can-now-use-host-networking) for configurations exposing lots of network ports." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:64 +#: ../../../YEAR-IN-REVIEW.md:57 msgid "[Element Call](https://github.com/element-hq/element-call) seems to have become a nice and polished product lately (as proclaimed in [The Matrix Holiday Update 2023](https://matrix.org/blog/2023/12/25/the-matrix-holiday-update-2023/)), so 2024 is likely the year we'll see support for it in the playbook. Element Call depends on the [LiveKit](https://livekit.io/) streaming server (which is also useful to developers even by itself), so the first step is likely to see LiveKit support in mash-playbook via a reusable Ansible role. Such a LiveKit Ansible role could later easily land in matrix-docker-ansible-deploy and an Element Call static website could be hooked to it." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:66 +#: ../../../YEAR-IN-REVIEW.md:59 msgid "Besides these highlights, there were many other relatively large changes announced in our [CHANGELOG](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md) and hundreds of other more minor (but still important) playbook changes that didn't get a mention." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:68 +#: ../../../YEAR-IN-REVIEW.md:61 msgid "We have **hundreds of contributors to thank for their hard work** on making Matrix self-hosting better for all of us! It should be noted that **support comes in many shapes**, not only in raw code commits and financial help (via [donations](https://liberapay.com/s.pantaleev) or using the [etke.cc managed Matrix hosting service](https://etke.cc/) which is based on matrix-docker-ansible-deploy). It also comes in the shape of code reviews, helping others with [issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues), reporting new issues, participating in our support room on Matrix ([#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)), etc. To everyone who has been there to make matrix-docker-ansible-deploy better in 2023, thank you! 🙇‍♂️" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:71 +#: ../../../YEAR-IN-REVIEW.md:64 msgid "2022" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:73 +#: ../../../YEAR-IN-REVIEW.md:66 msgid "For [matrix-docker-ansible-deploy](https://github.com/spantaleev/matrix-docker-ansible-deploy/), 2022 started with **breaking the** [**Synapse**](https://github.com/element-hq/synapse) **monopoly** by [adding support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#dendrite-support) for the [Dendrite](https://github.com/matrix-org/dendrite) Matrix homeserver in early January. This required various internal changes so that the [Ansible](https://www.ansible.com/) playbook would not be Synapse-centric anymore. This groundwork paved the way for continuing in this direction and we [added support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#conduit-support) for [Conduit](https://conduit.rs/) in August." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:75 +#: ../../../YEAR-IN-REVIEW.md:68 msgid "When it comes to the `matrix-docker-ansible-deploy` Ansible playbook, 2022 was the year of the non-Synapse homeserver implementation. In practice, none of these homeserver implementations seem ready for prime-time yet and there is no migration path when coming from Synapse. Having done our job of adding support for these alternative homeserver implementations, we can say that we're not getting in the way of future progress. It's time for the Dendrite developers to push harder (development-wise) and for the Synapse developers to take a well-deserved long (infinite) break, and we may get to see more people migrating away from Synapse in the next year(s)." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:77 +#: ../../../YEAR-IN-REVIEW.md:70 msgid "Support for the following new **bridges** was added:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:79 +#: ../../../YEAR-IN-REVIEW.md:72 msgid "[Postmoogle](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#postmoogle-email-bridge-support) for bi-directional email bridging, which supersedes my old and simplistic [Email2Matrix](https://github.com/devture/email2matrix) one-way bridge-bot" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:80 +#: ../../../YEAR-IN-REVIEW.md:73 msgid "[mautrix-discord](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#mautrix-discord-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:81 +#: ../../../YEAR-IN-REVIEW.md:74 msgid "[go-skype-bridge](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#go-skype-bridge-bridging-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:82 +#: ../../../YEAR-IN-REVIEW.md:75 msgid "[matrix-appservice-kakaotalk](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-appservice-kakaotalk-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:84 +#: ../../../YEAR-IN-REVIEW.md:77 msgid "Support for the following new **bots** was added:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:86 +#: ../../../YEAR-IN-REVIEW.md:79 msgid "[buscarron bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#buscarron-bot-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:87 +#: ../../../YEAR-IN-REVIEW.md:80 msgid "[Honoroit bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#honoroit-bot-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:88 +#: ../../../YEAR-IN-REVIEW.md:81 msgid "[matrix-registration-bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-registration-bot-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:89 +#: ../../../YEAR-IN-REVIEW.md:82 msgid "[matrix-hookshot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-hookshot-bridging-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:90 +#: ../../../YEAR-IN-REVIEW.md:83 msgid "[maubot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#maubot-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:92 +#: ../../../YEAR-IN-REVIEW.md:85 msgid "Support for the following new **components and services** was added:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:94 +#: ../../../YEAR-IN-REVIEW.md:87 msgid "[BorgBackup](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#borg-backup-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:95 +#: ../../../YEAR-IN-REVIEW.md:88 msgid "[Cactus Comments](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cactus-comments-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:96 +#: ../../../YEAR-IN-REVIEW.md:89 msgid "[Cinny](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cinny-support) client support" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:97 +#: ../../../YEAR-IN-REVIEW.md:90 msgid "[ntfy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#ntfy-push-notifications-support) notifications" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:98 +#: ../../../YEAR-IN-REVIEW.md:91 msgid "[matrix-ldap-registration-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-ldap-registration-proxy-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:99 +#: ../../../YEAR-IN-REVIEW.md:92 msgid "[matrix\\_encryption\\_disabler support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix_encryption_disabler-support)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:100 +#: ../../../YEAR-IN-REVIEW.md:93 msgid "[synapse-s3-storage-provider](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-s3-storage-provider-support) to stop the Synapse media store from being a scalability problem. This brought along [another feature](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-container-image-customization-support) - an easier way to customize the Synapse container image without having to fork and self-build all of it from scratch" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:102 +#: ../../../YEAR-IN-REVIEW.md:95 msgid "Besides these major user-visible changes, a lot of work also happened **under the hood**:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:104 +#: ../../../YEAR-IN-REVIEW.md:97 msgid "we made [major improvements to Synapse workers](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#potential-backward-compatibility-break-major-improvements-to-synapse-workers) - adding support for stream writers and for running multiple workers of various kinds (federation senders, pushers, background task processing workers, etc.)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:105 +#: ../../../YEAR-IN-REVIEW.md:98 msgid "we [improved the compatibility of (Synapse + workers) with the rest of the playbook](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#backward-compatibility-break-changing-how-reverse-proxying-to-synapse-works---now-via-a-matrix-synapse-reverse-proxy-companion-service) by introducing a new `matrix-synapse-reverse-proxy-companion-service` service" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:106 +#: ../../../YEAR-IN-REVIEW.md:99 msgid "we started [splitting various Ansible roles out of the Matrix playbook and into independent roles](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#the-playbook-now-uses-external-roles-for-some-things) (e.g. `matrix-postgres` -> [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres)), which could be included in other Ansible playbooks. In fact, these roles already power a few **interesting other sibling playbooks**:" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:107 +#: ../../../YEAR-IN-REVIEW.md:100 msgid "[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy), for deploying a [Gitea](https://gitea.io/) (self-hosted [Git](https://git-scm.com/) service) server" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:108 +#: ../../../YEAR-IN-REVIEW.md:101 msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), for deploying a [Nextcloud](https://nextcloud.com/) groupware server" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:109 +#: ../../../YEAR-IN-REVIEW.md:102 msgid "[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy), for deploying a [Vaultwarden](https://github.com/dani-garcia/vaultwarden) password manager server (unofficial [Bitwarden](https://bitwarden.com/) compatible server)" msgstr "" -#: ../../../YEAR-IN-REVIEW.md:111 +#: ../../../YEAR-IN-REVIEW.md:104 msgid "These sibling playbooks co-exist nicely with one another due to using [Traefik](https://traefik.io/) for reverse-proxying, instead of trying to overtake the whole server by running their own [nginx](https://nginx.org/) reverse-proxy. Hopefully soon, the Matrix playbook will follow suit and be powered by Traefik by default." msgstr "" -#: ../../../YEAR-IN-REVIEW.md:113 +#: ../../../YEAR-IN-REVIEW.md:106 msgid "Last, but not least, to optimize our [etke.cc managed Matrix hosting service](https://etke.cc/)'s performance (but also individual Ansible playbook runs for people self-hosting by themselves using the playbook), we've [improved playbook runtime 2-5x](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) by employing various Ansible tricks." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/ansible.po b/i18n/locales/jp/LC_MESSAGES/docs/ansible.po index b71d8c3e2..a322cda24 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/ansible.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/ansible.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,176 +18,164 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/ansible.md:11 -msgid "Using Ansible for the playbook" +#: ../../../docs/ansible.md:2 +msgid "Running this playbook" msgstr "" -#: ../../../docs/ansible.md:13 +#: ../../../docs/ansible.md:4 msgid "This playbook is meant to be run using [Ansible](https://www.ansible.com/)." msgstr "" -#: ../../../docs/ansible.md:15 +#: ../../../docs/ansible.md:6 msgid "Ansible typically runs on your local computer and carries out tasks on a remote server. If your local computer cannot run Ansible, you can also run Ansible on some server somewhere (including the server you wish to install to)." msgstr "" -#: ../../../docs/ansible.md:17 +#: ../../../docs/ansible.md:8 msgid "Supported Ansible versions" msgstr "" -#: ../../../docs/ansible.md:19 +#: ../../../docs/ansible.md:10 msgid "To manually check which version of Ansible you're on, run: `ansible --version`." msgstr "" -#: ../../../docs/ansible.md:21 +#: ../../../docs/ansible.md:12 msgid "For the **best experience**, we recommend getting the **latest version of Ansible available**." msgstr "" -#: ../../../docs/ansible.md:23 -msgid "We're not sure what's the minimum version of Ansible that can run this playbook successfully. The lowest version that we suspect (on 2025-09-03) to be working fine is: `ansible-core` (`2.15.1`)." +#: ../../../docs/ansible.md:14 +msgid "We're not sure what's the minimum version of Ansible that can run this playbook successfully. The lowest version that we've confirmed (on 2022-11-26) to be working fine is: `ansible-core` (`2.11.7`) combined with `ansible` (`4.10.0`)." msgstr "" -#: ../../../docs/ansible.md:25 +#: ../../../docs/ansible.md:16 msgid "If your distro ships with an Ansible version older than this, you may run into issues. Consider [Upgrading Ansible](#upgrading-ansible) or [using Ansible via Docker](#using-ansible-via-docker)." msgstr "" -#: ../../../docs/ansible.md:27 -msgid "[!WARNING] One reason for the version requirement being as such is that the playbook by default installs Docker for you using [this Docker role](https://github.com/geerlingguy/ansible-role-docker) which [has a hard requirement on Ansible v2.15.1](https://github.com/geerlingguy/ansible-role-docker/commit/7f44a1d9ad8132819ea9852918bca5dab8757cd0). If you install Docker yourself another way, you can tell the playbook to skip running this role (by adding `matrix_playbook_docker_installation_enabled: false` to your `vars.yml` configuration). It may then be possible to get the playbook running on an older version of Ansible. Still, this is a complication and your mileage may vary. We recommend [upgrading Ansible](#upgrading-ansible) instead of going into uncharted territory." -msgstr "" - -#: ../../../docs/ansible.md:30 +#: ../../../docs/ansible.md:18 msgid "Upgrading Ansible" msgstr "" -#: ../../../docs/ansible.md:32 +#: ../../../docs/ansible.md:20 msgid "Depending on your distribution, you may be able to upgrade Ansible in a few different ways:" msgstr "" -#: ../../../docs/ansible.md:34 +#: ../../../docs/ansible.md:22 msgid "by using an additional repository (PPA, etc.), which provides newer Ansible versions. See instructions for [CentOS](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-rhel-centos-or-fedora), [Debian](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-debian), or [Ubuntu](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-ubuntu) on the Ansible website." msgstr "" -#: ../../../docs/ansible.md:36 +#: ../../../docs/ansible.md:24 msgid "by removing the Ansible package (`yum remove ansible` or `apt-get remove ansible`) and installing via [pip](https://pip.pypa.io/en/stable/installation/) (`pip install ansible`)." msgstr "" -#: ../../../docs/ansible.md:38 +#: ../../../docs/ansible.md:26 msgid "If using the `pip` method, do note that the `ansible-playbook` binary may not be on the `$PATH` (https://linuxconfig.org/linux-path-environment-variable), but in some more special location like `/usr/local/bin/ansible-playbook`. You may need to invoke it using the full path." msgstr "" -#: ../../../docs/ansible.md:40 +#: ../../../docs/ansible.md:28 msgid "**Note**: Both of the above methods are a bad way to run system software such as Ansible. If you find yourself needing to resort to such hacks, please consider reporting a bug to your distribution and/or switching to a sane distribution, which provides up-to-date software." msgstr "" -#: ../../../docs/ansible.md:42 +#: ../../../docs/ansible.md:30 msgid "Using Ansible via Docker" msgstr "" -#: ../../../docs/ansible.md:44 -msgid "Alternatively, you can run Ansible inside a Docker container (powered by the [ghcr.io/devture/ansible](https://github.com/devture/docker-ansible/pkgs/container/ansible) Docker image)." -msgstr "" - -#: ../../../docs/ansible.md:46 -msgid "This ensures that:" -msgstr "" - -#: ../../../docs/ansible.md:48 -msgid "you're using a very recent Ansible version, which is less likely to be incompatible with the playbook" +#: ../../../docs/ansible.md:32 +msgid "Alternatively, you can run Ansible inside a Docker container (powered by the [devture/ansible](https://hub.docker.com/r/devture/ansible/) Docker image)." msgstr "" -#: ../../../docs/ansible.md:49 -msgid "you also get access to the [agru](https://github.com/etkecc/agru) tool for quicker Ansible role installation (when running `just roles`) compared to `ansible-galaxy`" +#: ../../../docs/ansible.md:34 +msgid "This ensures that you're using a very recent Ansible version, which is less likely to be incompatible with the playbook." msgstr "" -#: ../../../docs/ansible.md:51 +#: ../../../docs/ansible.md:36 msgid "You can either [run Ansible in a container on the Matrix server itself](#running-ansible-in-a-container-on-the-matrix-server-itself) or [run Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)." msgstr "" -#: ../../../docs/ansible.md:53 +#: ../../../docs/ansible.md:38 msgid "Running Ansible in a container on the Matrix server itself" msgstr "" -#: ../../../docs/ansible.md:55 +#: ../../../docs/ansible.md:40 msgid "To run Ansible in a (Docker) container on the Matrix server itself, you need to have a working Docker installation. Docker is normally installed by the playbook, so this may be a bit of a chicken and egg problem. To solve it:" msgstr "" -#: ../../../docs/ansible.md:57 +#: ../../../docs/ansible.md:42 msgid "you **either** need to install Docker manually first. Follow [the upstream instructions](https://docs.docker.com/engine/install/) for your distribution and consider setting `matrix_playbook_docker_installation_enabled: false` in your `vars.yml` file, to prevent the playbook from installing Docker" msgstr "" -#: ../../../docs/ansible.md:58 +#: ../../../docs/ansible.md:43 msgid "**or** you need to run the playbook in another way (e.g. [Running Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)) at least the first time around" msgstr "" -#: ../../../docs/ansible.md:60 +#: ../../../docs/ansible.md:45 msgid "Once you have a working Docker installation on the server, **clone the playbook** somewhere on the server and configure it as per usual (`inventory/hosts`, `inventory/host_vars/…`, etc.), as described in [configuring the playbook](configuring-playbook.md)." msgstr "" -#: ../../../docs/ansible.md:62 +#: ../../../docs/ansible.md:47 msgid "You would then need to add `ansible_connection=community.docker.nsenter` to the host line in `inventory/hosts`. This tells Ansible to connect to the \"remote\" machine by switching Linux namespaces with [nsenter](https://man7.org/linux/man-pages/man1/nsenter.1.html), instead of using SSH." msgstr "" -#: ../../../docs/ansible.md:64 -msgid "Alternatively, you can leave your `inventory/hosts` as is and specify the connection type in **each** `ansible-playbook` call you do later, like this: `just install-all --connection=community.docker.nsenter` (or `ansible-playbook --connection=community.docker.nsenter …`)." +#: ../../../docs/ansible.md:49 +msgid "Alternatively, you can leave your `inventory/hosts` as is and specify the connection type in **each** `ansible-playbook` call you do later, like this: `ansible-playbook --connection=community.docker.nsenter …`" msgstr "" -#: ../../../docs/ansible.md:66 ../../../docs/ansible.md:88 +#: ../../../docs/ansible.md:51 ../../../docs/ansible.md:71 msgid "Run this from the playbook's directory:" msgstr "" -#: ../../../docs/ansible.md:80 ../../../docs/ansible.md:103 +#: ../../../docs/ansible.md:63 ../../../docs/ansible.md:84 msgid "Once you execute the above command, you'll be dropped into a `/work` directory inside a Docker container. The `/work` directory contains the playbook's code." msgstr "" -#: ../../../docs/ansible.md:82 ../../../docs/ansible.md:105 +#: ../../../docs/ansible.md:65 ../../../docs/ansible.md:86 msgid "First, consider running `git config --global --add safe.directory /work` to [resolve directory ownership issues](#resolve-directory-ownership-issues)." msgstr "" -#: ../../../docs/ansible.md:84 -msgid "Finally, you can execute `just` or `ansible-playbook …` (e.g. `ansible-playbook --connection=community.docker.nsenter …`) commands as per normal now." +#: ../../../docs/ansible.md:67 +msgid "Finally, you can execute `ansible-playbook …` (or `ansible-playbook --connection=community.docker.nsenter …`) commands as per normal now." msgstr "" -#: ../../../docs/ansible.md:86 +#: ../../../docs/ansible.md:69 msgid "Running Ansible in a container on another computer (not the Matrix server)" msgstr "" -#: ../../../docs/ansible.md:101 -msgid "The above command tries to mount an SSH key (`$HOME/.ssh/id_ed25519`) into the container (at `/root/.ssh/id_ed25519`). If your SSH key is at a different path (not in `$HOME/.ssh/id_ed25519`), adjust that part." +#: ../../../docs/ansible.md:82 +msgid "The above command tries to mount an SSH key (`$HOME/.ssh/id_rsa`) into the container (at `/root/.ssh/id_rsa`). If your SSH key is at a different path (not in `$HOME/.ssh/id_rsa`), adjust that part." msgstr "" -#: ../../../docs/ansible.md:107 -msgid "Finally, you execute `just` or `ansible-playbook …` commands as per normal now." +#: ../../../docs/ansible.md:88 +msgid "Finally, you execute `ansible-playbook …` commands as per normal now." msgstr "" -#: ../../../docs/ansible.md:109 +#: ../../../docs/ansible.md:90 msgid "If you don't use SSH keys for authentication" msgstr "" -#: ../../../docs/ansible.md:111 -msgid "If you don't use SSH keys for authentication, simply remove that whole line (`--mount type=bind,src$HOME/.ssh/id_ed25519,dst=/root/.ssh/id_ed25519,ro`)." +#: ../../../docs/ansible.md:92 +msgid "If you don't use SSH keys for authentication, simply remove that whole line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`)." msgstr "" -#: ../../../docs/ansible.md:113 +#: ../../../docs/ansible.md:94 msgid "To authenticate at your server using a password, you need to add a package. So, when you are in the shell of the ansible docker container (the previously used `docker run -it …` command), run:" msgstr "" -#: ../../../docs/ansible.md:119 -msgid "Then, to be asked for the password whenever running an `ansible-playbook` command add `--ask-pass` to the arguments of the command." +#: ../../../docs/ansible.md:100 +msgid "Then, to be asked for the password whenever running an `ansible-playbook` command add `--ask-pass` to the arguments of the command." msgstr "" -#: ../../../docs/ansible.md:121 +#: ../../../docs/ansible.md:102 msgid "Resolve directory ownership issues" msgstr "" -#: ../../../docs/ansible.md:123 -msgid "Because you're `root` in the container running Ansible and this likely differs from the owner (your regular user account) of the playbook directory outside of the container, certain playbook features which use `git` locally may report warnings such as:" +#: ../../../docs/ansible.md:104 +msgid "Because you're `root` in the container running Ansible and this likely differs fom the owner (your regular user account) of the playbook directory outside of the container, certain playbook features which use `git` locally may report warnings such as:" msgstr "" -#: ../../../docs/ansible.md:125 +#: ../../../docs/ansible.md:106 msgid "fatal: unsafe repository ('/work' is owned by someone else) To add an exception for this directory, call: git config --global --add safe.directory /work" msgstr "" -#: ../../../docs/ansible.md:129 +#: ../../../docs/ansible.md:110 msgid "These errors can be resolved by making `git` trust the playbook directory by running `git config --global --add safe.directory /work`" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-dns.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-dns.po index 2c327006c..7ab3e1cb9 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-dns.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-dns.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,25 +18,25 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-dns.md:18 -msgid "Configuring DNS settings" +#: ../../../docs/configuring-dns.md:1 +msgid "Configuring your DNS settings" msgstr "" -#: ../../../docs/configuring-dns.md:20 -msgid "[Prerequisites](prerequisites.md) > Configuring DNS settings > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)" +#: ../../../docs/configuring-dns.md:3 +msgid "[Prerequisites](prerequisites.md) > Configuring your DNS settings > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)" msgstr "" -#: ../../../docs/configuring-dns.md:22 +#: ../../../docs/configuring-dns.md:5 msgid "To set up Matrix on your domain, you'd need to do some DNS configuration." msgstr "" -#: ../../../docs/configuring-dns.md:24 +#: ../../../docs/configuring-dns.md:7 msgid "DNS settings for services enabled by default" msgstr "" -#: ../../../docs/configuring-dns.md:26 +#: ../../../docs/configuring-dns.md:9 msgid "To serve the base domain (`example.com`) and [Element Web](configuring-playbook-client-element-web.md) with the default subdomain, adjust DNS records as below." msgstr "" @@ -77,15 +77,7 @@ msgid "-" msgstr "" #: ../../../docs/configuring-dns.md -msgid "`matrix-server-IPv4`" -msgstr "" - -#: ../../../docs/configuring-dns.md -msgid "AAAA" -msgstr "" - -#: ../../../docs/configuring-dns.md -msgid "`matrix-server-IPv6`" +msgid "`matrix-server-IP`" msgstr "" #: ../../../docs/configuring-dns.md @@ -100,62 +92,58 @@ msgstr "" msgid "`matrix.example.com`" msgstr "" -#: ../../../docs/configuring-dns.md:34 -msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IPv4/IPv6 address." +#: ../../../docs/configuring-dns.md:16 +msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)." msgstr "" -#: ../../../docs/configuring-dns.md:36 -msgid "If you don't have IPv6 connectivity yet, you can skip the `AAAA` record. For more details about IPv6, see the [Configuring IPv6](./configuring-ipv6.md) documentation page." -msgstr "" - -#: ../../../docs/configuring-dns.md:38 +#: ../../../docs/configuring-dns.md:18 msgid "The `element.example.com` subdomain is necessary, because this playbook installs the [Element Web](https://github.com/element-hq/element-web) client for you by default. If you'd rather instruct the playbook not to install Element Web (`matrix_client_element_enabled: false` when [Configuring the playbook](configuring-playbook.md) later), feel free to skip the `element.example.com` DNS record." msgstr "" -#: ../../../docs/configuring-dns.md:40 +#: ../../../docs/configuring-dns.md:20 msgid "Be mindful as to how long it will take for the DNS records to propagate." msgstr "" -#: ../../../docs/configuring-dns.md:42 +#: ../../../docs/configuring-dns.md:22 msgid "**Note**: if you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\". Otherwise, fetching certificates will fail." msgstr "" -#: ../../../docs/configuring-dns.md:44 +#: ../../../docs/configuring-dns.md:24 msgid "DNS setting for server delegation (optional)" msgstr "" -#: ../../../docs/configuring-dns.md:46 +#: ../../../docs/configuring-dns.md:26 msgid "In the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com`." msgstr "" -#: ../../../docs/configuring-dns.md:48 +#: ../../../docs/configuring-dns.md:28 msgid "To use such an ID, you don't need to install anything on the actual `example.com` server. Instead, you need to instruct the Matrix network that Matrix services for `example.com` are redirected over to `matrix.example.com`. This redirection is also known as \"delegation\"." msgstr "" -#: ../../../docs/configuring-dns.md:50 +#: ../../../docs/configuring-dns.md:30 msgid "As we discuss in [Server Delegation](howto-server-delegation.md), server delegation can be configured in either of these ways:" msgstr "" -#: ../../../docs/configuring-dns.md:52 +#: ../../../docs/configuring-dns.md:32 msgid "Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)" msgstr "" -#: ../../../docs/configuring-dns.md:53 +#: ../../../docs/configuring-dns.md:33 msgid "Setting up a `_matrix._tcp` DNS SRV record" msgstr "" -#: ../../../docs/configuring-dns.md:55 +#: ../../../docs/configuring-dns.md:35 msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file, instead of using a DNS SRV record." msgstr "" -#: ../../../docs/configuring-dns.md:57 +#: ../../../docs/configuring-dns.md:37 msgid "If you choose the recommended method (file-based delegation), you do not need to configure the DNS record to enable server delegation. You will need to add a necessary configuration later, when you [finalize the installation](installing.md#finalize-the-installation) after installing and starting Matrix services." msgstr "" -#: ../../../docs/configuring-dns.md:59 +#: ../../../docs/configuring-dns.md:39 msgid "On the other hand, if you choose this method (setting up a DNS SRV record), you need to configure the additional DNS record as well as adjust SSL certificate handling. Take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)" msgstr "" -#: ../../../docs/configuring-dns.md:63 +#: ../../../docs/configuring-dns.md:43 msgid "[▶️](getting-the-playbook.md) When you're done with the DNS configuration and ready to proceed, continue with [Getting the playbook](getting-the-playbook.md)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-ipv6.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-ipv6.po deleted file mode 100644 index 7fc5e0c89..000000000 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-ipv6.po +++ /dev/null @@ -1,366 +0,0 @@ -# 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 , 2026. -# -#, fuzzy -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" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: jp\n" -"Language-Team: jp \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-ipv6.md:6 -msgid "Configuring IPv6" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:8 -msgid "Since 2025-03-08, the [default example configuration](../examples/vars.yml) for the playbook recommends enabling [IPv6](https://en.wikipedia.org/wiki/IPv6) support for Docker's container networks." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:10 -msgid "**If you have IPv6 support on your server/network** (see [How do I check if my server has IPv6 connectivity?](#how-do-i-check-if-my-server-has-ipv6-connectivity)), then [enabling IPv6 support for the playbook](#enabling-ipv6-support-for-the-playbook) would give you:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:12 -msgid "📥 incoming IPv6 connectivity to the server via the server's IPv6 address/addresses (containers won't have their own individual publicly accessible IPs)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:13 -msgid "📤 outgoing IPv6 connectivity from the server via the server's IPv6 address/addresses (containers won't exit via their own individual IPv6 address)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:14 -msgid "🔄 IPv6 connectivity for cross-container communication" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:16 -msgid "**If you still don't have IPv6 support on your server/network**, then enabling IPv6 support for the playbook will only enable IPv6 connectivity for cross-container communication and shouldn't affect your server's incoming/outgoing communication. You may also be interested in reading if [there's a performance penalty to enabling IPv6 if the server/network doesn't support IPv6 connectivity?](#is-there-a-performance-penalty-to-enabling-ipv6-if-the-server-network-doesn-t-support-ipv6-connectivity)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:18 -msgid "As such, **we recommend that you follow the default example configuration and leave IPv6 support for Docker enabled in all cases**." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:20 -msgid "Enabling IPv6 consists of 2 steps:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:22 -msgid "[Enabling IPv6 support for the playbook](#enabling-ipv6-support-for-the-playbook)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:23 -msgid "[Configuring DNS records for IPv6](#configuring-dns-records-for-ipv6)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:25 -msgid "💡 If you've followed a recent version of our documentation, you would have already done these steps, so there's nothing else to do." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:27 -msgid "Enabling IPv6 support for the playbook" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:29 -msgid "You can enable IPv6 support for all components' Docker container networks by using the following `vars.yml` configuration:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:50 -msgid "Doing this:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:52 -msgid "all container networks will be IPv6-enabled" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:54 -msgid "NAT66 will be used, so that:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:55 -msgid "containers will get [Unique Local Addresses (ULA)](https://en.wikipedia.org/wiki/Unique_local_address)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:56 -msgid "the outgoing IPv6 address for containers will be the same as the one on the server" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:57 -msgid "traffic destined for the IPv6 address of the server will be forwarded to the containers that handle (and publish) that specific port" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:59 -msgid "[!WARNING] Without enabling this and assuming you have IPv6 `AAAA` DNS records pointing to the server (see [Configuring DNS records for IPv6](#configuring-dns-records-for-ipv6)), IPv6 traffic will still be handled, but NAT64 will be used instead of NAT66. As such, containers will only have an IPv4 address and all IPv6 traffic that reaches them will seem to originate from a local IP. Containers also won't be able to make outgoing (even cross-container) IPv6 requests." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:63 -msgid "To confirm connectivity, see the following other resources:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:65 -msgid "[How do I check if my server has IPv6 connectivity?](#how-do-i-check-if-my-server-has-ipv6-connectivity)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:66 -msgid "[How do I check outgoing IPv6 connectivity for containers?](#how-do-i-check-outgoing-ipv6-connectivity-for-containers)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:67 -msgid "[How do I check incoming IPv6 connectivity for containers?](#how-do-i-check-incoming-ipv6-connectivity-for-containers)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:68 -msgid "[How do I confirm if my container networks are IPv6-enabled?](#how-do-i-confirm-if-my-container-networks-are-ipv6-enabled)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:69 -msgid "Ensure that the [Federation Tester](https://federationtester.matrix.org/) reports that your server is reachable over IPv6." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:71 -msgid "Configuring DNS records for IPv6" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:73 -msgid "[Enabling IPv6 support for the playbook](#enabling-ipv6-support-for-the-playbook) tells you how to prepare for IPv6 on the container (Docker) side." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:75 -msgid "For full public IPv6 connectivity (and not just IPv6 connectivity for containers inside the container networks) you also need to **ensure that your domain names** (e.g. `matrix.example.com` and others) have IPv6 (`AAAA`) DNS records pointing to the server's IPv6 address." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:77 -msgid "Also see the [Configuring DNS settings](configuring-dns.md) documentation page for more details." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:79 -msgid "A note about old Docker" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:81 -msgid "With our [default example configuration](../examples/vars.yml), the playbook manages Docker for you and installs a modern-enough version." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:83 -msgid "Docker versions newer than 27.0.1 enable IPv6 integration at the Docker daemon level out of the box. This still requires that networks are created with IPv6 support as described in the [Enabling IPv6 support for the playbook](#enabling-ipv6-support-for-the-playbook) section above." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:85 -msgid "**If you're on an old Docker version** (Docker 27.0.0 or older) for some reason, it's likely that your Docker installation is not enabled for IPv6 at all. In such a case:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:87 -msgid "if Docker is managed by the playbook, you can tell it to force-enable IPv6 via `devture_systemd_docker_base_ipv6_daemon_options_changing_enabled: true`" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:89 -#, python-brace-format -msgid "if Docker is managed by you manually, you can add `{\"experimental\": true, \"ip6tables\": true}` to the Docker daemon options and restart the Docker service (`docker.service`)." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:91 -msgid "Frequently Asked Questions" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:93 -msgid "How do I check if my server has IPv6 connectivity?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:95 -msgid "With curl" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:97 -msgid "You can run `curl https://icanhazip.com` and see if it returns an [IPv6 address](https://en.wikipedia.org/wiki/IPv6_address) (an address with `:` characters in it, like `2001:db8:1234:5678::1`). If it does, then your server has IPv6 connectivity and prefers it over using IPv4. This is common." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:99 -msgid "If you see an IPv4 address instead (e.g. `1.2.3.4`), it may be that your server prefers IPv4 over IPv6 or that your network does not support IPv6. You can try forcing `curl` to use IPv6 by running `curl -6 https://icanhazip.com` and see if it returns an IPv6 address." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:101 -msgid "With other network utilities" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:103 -msgid "You can run `ip -6 addr` to see if you have any IPv6 addresses assigned to your server, besides the link-local (`fe80::*`) addresses that everyone has (unless they have force-disabled IPv6 support on their system)." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:105 -msgid "If you do have an IPv6 address, it's still worth [using curl](#with-curl) to confirm that your server can successfully make outgoing requests over IPv6." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:107 -msgid "What does the `devture_systemd_docker_base_ipv6_enabled` setting actually do?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:109 -msgid "The `devture_systemd_docker_base_ipv6_enabled` setting controls whether container networks will be created with IPv6 support." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:111 -msgid "Changing this setting subsequently requires manual work (deleting all container networks). See [I've changed the `devture_systemd_docker_base_ipv6_enabled` setting, but it doesn't seem to have any effect](#i-ve-changed-the-devture_systemd_docker_base_ipv6_enabled-setting-but-it-doesn-t-seem-to-have-any-effect)." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:114 -msgid "I've changed the `devture_systemd_docker_base_ipv6_enabled` setting, but it doesn't seem to have any effect." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:116 -msgid "If you're using an older Docker version (Docker 27.0.0 or older), see [A note about old Docker](#a-note-about-old-docker)." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:118 -msgid "If you've previously installed with one `devture_systemd_docker_base_ipv6_enabled` value and then changed it to another, you need to:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:120 -msgid "stop all services (`just stop-all`)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:121 -msgid "delete all container networks on the server: `docker network rm $(docker network ls -q)`" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:122 -msgid "re-run the playbook fully: `just install-all`" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:124 -msgid "How do I confirm if my container networks are IPv6-enabled?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:126 -msgid "You can list container networks by running `docker network ls` on the server." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:128 -msgid "For each container network (e.g. `matrix-homeserver`), you can check if it has IPv6 connectivity by running a command like this: `docker network inspect matrix-homeserver`." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:130 -msgid "Ensure that there's an IPv6 subnet/gateway in the `IPAM.Config` section. If yes, you may wish to proceed with [How do I check outgoing IPv6 connectivity for containers?](#how-do-i-check-outgoing-ipv6-connectivity-for-containers)" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:132 -msgid "If there's no IPv6 subnet/gateway in the `IPAM.Config` section, this container network was not created with IPv6 support. See [I've changed the `devture_systemd_docker_base_ipv6_enabled` setting, but it doesn't seem to have any effect](#i-ve-changed-the-devture_systemd_docker_base_ipv6_enabled-setting-but-it-doesn-t-seem-to-have-any-effect)." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:135 -msgid "How do I check outgoing IPv6 connectivity for containers?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:141 -msgid "💡 This one-off container is connected to the `matrix-homeserver` container network, not to the default Docker bridge network. The default Docker `bridge` network does not have IPv6 connectivity by default (yet) and is not influenced by the `devture_systemd_docker_base_ipv6_enabled` setting, so using that network (by omitting `--network=..` from the command above) will not show an IPv6 address" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:143 -msgid "✅ If this command returns an IPv6 address, you're all good." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:145 -msgid "❌ If this command doesn't return an IPv6 address, it may be that:" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:147 -msgid "your container network does not have IPv6 connectivity. See [How do I confirm if my container networks are IPv6-enabled?](#how-do-i-confirm-if-my-container-networks-are-ipv6-enabled) for more details." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:149 -msgid "your server does not have IPv6 connectivity. See [How do I check if my server has IPv6 connectivity?](#how-do-i-check-if-my-server-has-ipv6-connectivity) for more details. If you do have IPv6 connectivity, then the issue is with Docker's IPv6 configuration. Otherwise, you need to check your server's network configuration/firewall/routing and get back to configuring the playbook later on." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:151 -msgid "How do I check incoming IPv6 connectivity for containers?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:153 -msgid "Only containers that publish ports will be exposed (reachable) publicly on the server's own IPv6 address. Containers will not get their own individual public IPv6 address." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:155 -msgid "For this playbook, a commonly exposed container is the Traefik reverse-proxy container (unless [you're using your own webserver](./configuring-playbook-own-webserver.md))." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:157 -msgid "You can either do something like `curl -6 https://matrix.example.com` from an IPv6-enabled host (including the server itself) and see if it works." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:159 -msgid "An alternative is to use the [IPv6 Port Checker](https://port.tools/port-checker-ipv6/) with a hostname of `matrix.example.com` and a port of `443`." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:161 -msgid "💡 Trying to connect to `matrix.example.com` via IPv6 requires that you have already [configured the DNS records for IPv6](#configuring-dns-records-for-ipv6) as described above. If you wish to eliminate DNS as a potential issue, you can also try connecting to the server's own IPv6 address directly: `curl -6 -H 'Host: matrix.example.com' https://[2001:db8:1234:5678::1]` (we pass a `Host` header to tell Traefik which host we'd like it to serve)." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:163 -msgid "Why enable IPv6 if my network doesn't support it yet?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:165 -msgid "Because when your network does get support for IPv6 later on (even if that's 5 years away), you won't have to change anything besides [configuring the DNS records for IPv6](#configuring-dns-records-for-ipv6)." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:167 -msgid "Can I use a custom subnet for IPv6?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:169 -msgid "Not easily." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:171 -msgid "The playbook and the various roles only support passing an `enable_ipv6` flag (`true` or `false` value depending on the `devture_systemd_docker_base_ipv6_enabled` Ansible variable) when creating the Docker container networks." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:173 -msgid "There's no support for passing a custom subnet for IPv4 and IPv6. We let Docker auto-generate the subnets for us." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:175 -msgid "You can either create a Pull Request that adds support for this to the various playbook roles, or you can manually recreate the networks from the command-line (e.g. `docker network rm matrix-homeserver && docker network create --ipv6 --subnet=2001:db8:1234:5678::/64 matrix-homeserver`)." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:177 -msgid "Can I use Global Unicast Addresses (GUA) for IPv6?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:179 -msgid "No. You cannot have GUA addresses where each container is individually addressable over the public internet." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:181 -msgid "The playbook only supports NAT66, which should be good enough for most use cases." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:183 -msgid "Having containers get IPv6 addresses from your own GUA subnet requires complex configuration (ndp-proxy, etc.) and is not supported." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:185 -msgid "You may find [this Reddit post](https://www.reddit.com/r/ipv6/comments/1alpzmb/comment/kphpw11/) interesting." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:187 -msgid "Is there a performance penalty to enabling IPv6 if the server/network doesn't support IPv6 connectivity?" -msgstr "" - -#: ../../../docs/configuring-ipv6.md:189 -msgid "Probably a tiny one, as services may try to make (unsuccessful) outgoing requests over IPv6." -msgstr "" - -#: ../../../docs/configuring-ipv6.md:191 -msgid "In practice, it's probably negligible." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po index 69d0b0836..0bf38b253 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,176 +18,184 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:9 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:1 msgid "Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver (optional)" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:11 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:3 msgid "The playbook can install and configure the [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver) service for you. It's a [client](https://prometheus.io/docs/alerting/latest/clients/) for Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/), allowing you to deliver alerts to Matrix rooms." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:13 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:5 msgid "See the project's [documentation](https://github.com/metio/matrix-alertmanager-receiver/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:15 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:7 msgid "This service is meant to be used with an external [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) instance. It's **not** meant to be integrated with the [Prometheus & Grafana stack](./configuring-playbook-prometheus-grafana.md) installed by this playbook, because the Alertmanager component is not installed by it." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:17 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:9 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:19 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:11 msgid "Register the bot account" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:21 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:13 msgid "This service uses a bot (with a username specified in `matrix_alertmanager_receiver_config_matrix_user_id_localpart`) for delivering messages." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:23 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:15 msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:25 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:17 msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:27 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:19 msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:33 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:25 msgid "Obtain an access token" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:35 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:27 msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:37 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:29 msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:40 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:32 msgid "Join to rooms as the bot manually" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:42 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:34 msgid "ℹ️ **This bot does not accept room invitations automatically**. To deliver messages to rooms, the bot must be joined to all rooms manually." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:44 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:36 msgid "For each new room you would like the bot to deliver alerts to, invite the bot to the room." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:46 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:38 msgid "Then, log in as the bot using any Matrix client of your choosing, accept the room invitation from the bot's account, and log out." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:48 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:40 msgid "Adjusting DNS records (optional)" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:50 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:42 msgid "By default, this playbook installs matrix-alertmanager-receiver on the `matrix.` subdomain, at the `/matrix-alertmanager-receiver` path (https://matrix.example.com/matrix-alertmanager-receiver). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:52 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:44 msgid "If you wish to adjust it, see the section [below](#adjusting-the-matrix-alertmanager-receiver-url-optional) for details about DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:54 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:46 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:56 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:48 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:77 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:69 msgid "Adjusting the matrix-alertmanager-receiver URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:79 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:71 msgid "By tweaking the `matrix_alertmanager_receiver_hostname` and `matrix_alertmanager_receiver_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:81 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:73 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:89 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:81 msgid "If you've changed the default hostname, you may need to create a CNAME record for the matrix-alertmanager-receiver domain (`alertmanager.example.com`), which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:91 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:83 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:93 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:85 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:95 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:87 msgid "There are some additional things you may wish to configure about the component." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:97 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:89 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:99 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:91 msgid "`roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:100 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:92 msgid "`roles/custom/matrix-alertmanager-receiver/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_alertmanager_receiver_configuration_extension_yaml` variable" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:102 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:94 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:104 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:96 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:111 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:103 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:105 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:107 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:113 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:109 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:115 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:111 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:117 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:113 msgid "Configure your Prometheus Alertmanager with configuration like this:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:136 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:132 msgid "where `URL_HERE` looks like `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/some-room-name` or `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/!qporfwt:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:138 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:134 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:140 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:136 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-alertmanager-receiver`." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:142 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:138 msgid "Increase logging verbosity" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:144 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:140 msgid "The default logging level for this component is `info`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po index 914ed22c1..60a96e7fe 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,68 +18,76 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:8 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:1 msgid "Setting up Appservice Double Puppet (optional)" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:10 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:3 msgid "The playbook can install and configure the Appservice Double Puppet service for you. It is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver." msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:12 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:5 msgid "This is useful for performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via the appservice method. The service is an implementation of this approach." msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:14 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:7 msgid "Previously, bridges supported performing double-puppeting with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but this old and hacky solution has been superseded by this Appservice Double Puppet method." msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:16 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:9 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:18 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:11 msgid "To enable the Appservice Double Puppet service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:24 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:17 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:26 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:19 msgid "There are some additional things you may wish to configure about the service." msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:28 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:21 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:30 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:23 msgid "`roles/custom/matrix-appservice-double-puppet/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_appservice_double_puppet_registration_configuration_extension_yaml` variable" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:32 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:25 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:34 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:27 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:41 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:34 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:36 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:38 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:43 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:40 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:45 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:42 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-appservice-double-puppet.md:47 +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:44 msgid "Installing the service will automatically enable double puppeting for all bridges that support double puppeting via the appservice method." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po index 5fc0d9344..6aa8af195 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,169 +18,169 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:8 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:1 msgid "Setting up Draupnir for All/D4A (optional)" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:10 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:3 msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool for you in appservice mode." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:12 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:5 msgid "Appservice mode can be used together with the regular [Draupnir bot](configuring-playbook-bot-draupnir.md) or independently. Details about the differences between the 2 modes are described below." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:14 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:7 msgid "Draupnir Appservice mode compared to Draupnir bot mode" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:16 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:9 msgid "The administrative functions for managing the appservice are alpha quality and very limited. However, the experience of using an appservice-provisioned Draupnir is on par with the experience of using Draupnir from bot mode except in the case of avatar customisation as described later on in this document." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:18 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:11 msgid "Draupnir for all is the way to go if you need more than 1 Draupnir instance, but you don't need access to Synapse Admin features as they are not accessible through Draupnir for All (Even though the commands do show up in help)." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:20 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:13 msgid "Draupnir for all in the playbook is rate-limit-exempt automatically as its appservice configuration file does not specify any rate limits." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:22 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:15 msgid "Normal Draupnir does come with the benefit of access to Synapse Admin features. You are also able to more easily customise your normal Draupnir than D4A as D4A even on the branch with the Avatar command (To be Upstreamed to Mainline Draupnir) that command is clunky as it requires the use of things like Element Web devtools. In normal Draupnir this is a quick operation where you login to Draupnir with a normal client and set Avatar and Display name normally." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:24 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:17 msgid "Draupnir for all does not support external tooling like [MRU](https://mru.rory.gay) as it can't access Draupnir's user account." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:26 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:19 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:28 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:21 msgid "Create a main management room" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:30 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:23 msgid "The playbook does not create a management room for your Main Draupnir. You **need to create the room manually** before setting up the bot." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:32 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:25 msgid "Note that the room must be unencrypted." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:34 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:27 msgid "The management 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:36 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:29 msgid "This management room is used to control who has access to your D4A deployment. The room stores this data inside of the control room state so your bot must have sufficient powerlevel to send custom state events. This is default 50 or moderator as Element clients call this powerlevel." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:38 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:31 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:41 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:34 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:43 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:36 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ALIAS_HERE`." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:51 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:44 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:53 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:46 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:48 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:57 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:50 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:52 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:66 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:68 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:83 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:77 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:70 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:72 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:74 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:83 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:76 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:85 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:94 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:87 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:96 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:89 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:91 +msgid "If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com` you have succesfully installed Draupnir for All and can now start using it." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:100 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:93 msgid "The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot mode." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:102 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:95 msgid "Granting Users the ability to use D4A" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:104 -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." +#: ../../../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." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:106 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:99 msgid "The bot requires a powerlevel of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297))" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:108 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:101 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." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:110 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:103 msgid "How to provision a D4A once you are allowed to" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:112 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:105 msgid "To provision a D4A, you need to start a chat with `@draupnir-main:example.com`. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:114 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:107 msgid "Congratulations if you made it all the way here because you now have a fully working Draupnir for all deployment." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-backup-borg.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-backup-borg.po index 0b1b0dc2b..68b1beb1d 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-backup-borg.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-backup-borg.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,28 +18,176 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-backup-borg.md:11 +#: ../../../docs/configuring-playbook-backup-borg.md:1 msgid "Setting up BorgBackup (optional)" msgstr "" -#: ../../../docs/configuring-playbook-backup-borg.md:13 +#: ../../../docs/configuring-playbook-backup-borg.md:3 msgid "The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) (short: Borg) with [borgmatic](https://torsion.org/borgmatic/) for you." msgstr "" -#: ../../../docs/configuring-playbook-backup-borg.md:15 +#: ../../../docs/configuring-playbook-backup-borg.md:5 msgid "BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service." msgstr "" -#: ../../../docs/configuring-playbook-backup-borg.md:17 -msgid "The [Ansible role for BorgBackup](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring BorgBackup, you can check them via:" +#: ../../../docs/configuring-playbook-backup-borg.md:7 +msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-backup-borg.md:18 -msgid "🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/docs/configuring-backup-borg.md) online" +#: ../../../docs/configuring-playbook-backup-borg.md:9 +msgid "Set up a remote server for storing backups" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:11 +msgid "You will need a remote server where BorgBackup will store the backups. There are hosted, BorgBackup compatible solutions available, such as [BorgBase](https://www.borgbase.com)." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:13 +msgid "Check the Postgres version" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:15 +msgid "By default, if you're using the integrated Postgres database server (as opposed to [an external Postgres server](configuring-playbook-external-postgres.md)), backups with BorgBackup will also include dumps of your Postgres database." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:17 +msgid "Unless you disable the Postgres-backup support, make sure that the Postgres version of your homeserver's database is compatible with borgmatic. You can check the compatible versions [here](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:19 -msgid "📁 `roles/galaxy/backup_borg/docs/configuring-backup-borg.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" +msgid "An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md). If you decide to go with another solution, you can disable Postgres-backup support for BorgBackup using the `backup_borg_postgresql_enabled` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:21 +msgid "Create a new SSH key" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:23 +msgid "Run the command below on any machine to create a new SSH key:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:29 +msgid "You don't need to place the key in the `.ssh` folder." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:31 +msgid "Add the public key" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:33 +msgid "Next, add the **public** part of this SSH key (the `matrix-borg-backup.pub` file) to your BorgBackup provider/server." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:35 +msgid "If you are using a hosted solution, follow their instructions. If you have your own server, copy the key to it with the command like below:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:45 +msgid "The **private** key needs to be added to `backup_borg_ssh_key_private` on your `inventory/host_vars/matrix.example.com/vars.yml` file as below." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:47 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:49 +msgid "To enable BorgBackup, add the following configuration to your `vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:76 +msgid "**Note**: `REPO` will be initialized on backup start, for example: `matrix`. See [Remote repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html#repository-urls) for the syntax." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:78 +msgid "Set backup archive name (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:80 +msgid "You can specify the backup archive name format. To set it, add the following configuration to your `vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:86 +msgid "Configure retention policy (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:88 +msgid "It is also possible to configure a retention strategy. To configure it, add the following configuration to your `vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:98 +msgid "Edit the backup schedule (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:100 +msgid "By default the backup will run 4 a.m. every day based on the `backup_borg_schedule` variable. It is defined in the format of systemd timer calendar." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:102 +msgid "To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:108 +msgid "**Note**: the actual job may run with a delay. See `backup_borg_schedule_randomized_delay_sec` [here](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/f5d5b473d48c6504be10b3d946255ef5c186c2a6/defaults/main.yml#L50) for its default value." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:110 +msgid "Set include and/or exclude directories (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:112 +msgid "`backup_borg_location_source_directories` defines the list of directories to back up. It's set to `{{ matrix_base_data_path }}` by default, which is the base directory for every service's data, such as Synapse, Postgres and the bridges." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:114 +msgid "You might also want to exclude certain directories or file patterns from the backup using the `backup_borg_location_exclude_patterns` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:116 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:118 +msgid "There are some additional things you may wish to configure about the component." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:120 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:122 +msgid "[backup_borg role](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml) for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `backup_borg_configuration_extension_yaml` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:124 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:126 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:133 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:135 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:137 +msgid "Manually start a backup" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:139 +msgid "Sometimes it can be helpful to run the backup as you'd like, avoiding to wait until 4 a.m., like when you test your configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:141 +msgid "If you want to run it immediately, log in to the server with SSH and run `systemctl start matrix-backup-borg`." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:143 +msgid "This will not return until the backup is done, so it can possibly take a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po index b853dae63..80a782475 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,24 +18,112 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:1 +msgid "Setting up matrix-bot-chatgpt (optional, unmaintained)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:3 +msgid "**Note**: [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) is now an archived (**unmaintained**) project. Talking to ChatGPT (and many other LLM providers) can happen via the much more featureful [baibot](https://github.com/etkecc/baibot), which can be installed using [this playbook](configuring-playbook-bot-baibot.md). Consider using that bot instead of this one." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:5 +msgid "The playbook can install and configure [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:7 +msgid "Talk to [ChatGPT](https://openai.com/blog/chatgpt/) via your favourite Matrix client!" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:9 +msgid "Prerequisites" +msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:11 -msgid "Setting up matrix-chatgpt-bot (optional, removed)" +msgid "Obtain an OpenAI API key" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:13 -msgid "🪦 The playbook used to be able to install and configure [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot), but no longer includes this component." +msgid "To use the bot, you'd need to obtain an API key from [https://platform.openai.com/account/api-keys](https://platform.openai.com/account/api-keys)." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:15 -msgid "While not a 1:1 replacement, the bot'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)." +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:17 -msgid "Uninstalling matrix-chatgpt-bot manually" +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:19 -msgid "If you still have the matrix-chatgpt-bot component 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:" +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:21 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:27 +msgid "Obtain an access token and create encryption keys" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:29 +msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:31 +msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:34 +msgid "To make sure the bot can read encrypted messages, it will need an encryption key, just like any other new user. While obtaining the access token, follow the prompts to setup a backup key. More information can be found in the [Element documentation](https://element.io/help#encryption6)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:36 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:38 +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `API_KEY_HERE` with the API key retrieved [here](#obtain-an-openai-api-key) and `ACCESS_TOKEN_HERE` with the access token created [here](#obtain-an-access-token-and-create-encryption-keys), respectively." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:55 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:57 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:64 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:66 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:68 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:70 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:72 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:74 +msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.chatgpt:example.com` where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:76 +msgid "After the bot joins the room, you can send a message to it. When you do so, use the prefix if you configured it or mention the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:78 +msgid "You can also refer to the upstream [documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po index a4e6495d6..a0ac374fc 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,160 +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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bot-go-neb.md:11 +#: ../../../docs/configuring-playbook-bot-go-neb.md:1 msgid "Setting up Go-NEB (optional, unmaintained)" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:13 -msgid "**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an archived (**unmaintained**) project. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be [installed using this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bot instead of this one." +#: ../../../docs/configuring-playbook-bot-go-neb.md:3 +msgid "**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an archived (**unmaintained**) project. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bot instead of this one." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:15 +#: ../../../docs/configuring-playbook-bot-go-neb.md:5 msgid "The playbook can install and configure [Go-NEB](https://github.com/matrix-org/go-neb) for you." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:17 +#: ../../../docs/configuring-playbook-bot-go-neb.md:7 msgid "Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, the original Matrix bot written in Python." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:19 +#: ../../../docs/configuring-playbook-bot-go-neb.md:9 msgid "See the project's [documentation](https://github.com/matrix-org/go-neb/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:21 +#: ../../../docs/configuring-playbook-bot-go-neb.md:11 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:23 +#: ../../../docs/configuring-playbook-bot-go-neb.md:13 msgid "Register the bot account" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:25 +#: ../../../docs/configuring-playbook-bot-go-neb.md:15 msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:27 +#: ../../../docs/configuring-playbook-bot-go-neb.md:17 msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:29 +#: ../../../docs/configuring-playbook-bot-go-neb.md:19 msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:35 +#: ../../../docs/configuring-playbook-bot-go-neb.md:25 msgid "Obtain an access token" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:37 +#: ../../../docs/configuring-playbook-bot-go-neb.md:27 msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:39 +#: ../../../docs/configuring-playbook-bot-go-neb.md:29 msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:42 +#: ../../../docs/configuring-playbook-bot-go-neb.md:32 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:44 +#: ../../../docs/configuring-playbook-bot-go-neb.md:34 msgid "By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to create a CNAME record for `goneb`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:46 +#: ../../../docs/configuring-playbook-bot-go-neb.md:36 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:48 +#: ../../../docs/configuring-playbook-bot-go-neb.md:38 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:50 +#: ../../../docs/configuring-playbook-bot-go-neb.md:40 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_GONEB_HERE` and `ACCESS_TOKEN_FOR_ANOTHER_GONEB_HERE` with the ones created [above](#obtain-an-access-token)." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:214 +#: ../../../docs/configuring-playbook-bot-go-neb.md:204 msgid "Adjusting the Go-NEB URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:216 +#: ../../../docs/configuring-playbook-bot-go-neb.md:206 msgid "By tweaking the `matrix_bot_go_neb_hostname` and `matrix_bot_go_neb_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:218 +#: ../../../docs/configuring-playbook-bot-go-neb.md:208 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:229 +#: ../../../docs/configuring-playbook-bot-go-neb.md:219 msgid "After changing the domain, **you may need to adjust your DNS** records to point the Go-NEB domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:231 +#: ../../../docs/configuring-playbook-bot-go-neb.md:221 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:233 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-go-neb.md:235 -msgid "There are some additional things you may wish to configure about the bot." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-go-neb.md:237 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-go-neb.md:239 -msgid "`roles/custom/matrix-bot-go-neb/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +#: ../../../docs/configuring-playbook-bot-go-neb.md:223 +msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:240 -msgid "`roles/custom/matrix-bot-go-neb/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_go_neb_configuration_extension_yaml` variable" +#: ../../../docs/configuring-playbook-bot-go-neb.md:225 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:242 -msgid "Installing" +#: ../../../docs/configuring-playbook-bot-go-neb.md:232 +msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:244 -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:" +#: ../../../docs/configuring-playbook-bot-go-neb.md:234 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:251 +#: ../../../docs/configuring-playbook-bot-go-neb.md:236 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:253 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-bot-go-neb.md:238 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:255 +#: ../../../docs/configuring-playbook-bot-go-neb.md:240 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:257 +#: ../../../docs/configuring-playbook-bot-go-neb.md:242 msgid "To use the bot, invite it to any existing Matrix room (`/invite @bot.go-neb:example.com` where `example.com` is your base domain, not the `matrix.` domain). Make sure you are granted with the sufficient permission if you are not the room owner." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:259 +#: ../../../docs/configuring-playbook-bot-go-neb.md:244 msgid "Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy matrix`" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:261 +#: ../../../docs/configuring-playbook-bot-go-neb.md:246 msgid "If you enabled the github_cmd service, send `!github help` to the bot in the room to see the available commands." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:263 +#: ../../../docs/configuring-playbook-bot-go-neb.md:248 msgid "You can also refer to the upstream [Documentation](https://github.com/matrix-org/go-neb)." msgstr "" - -#: ../../../docs/configuring-playbook-bot-go-neb.md:265 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-go-neb.md:267 -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-go-neb`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po index 00e999a54..97b54bae7 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,181 +18,153 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:10 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:1 msgid "Setting up Appservice Discord bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:12 -msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge supported by the playbook." +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:3 +msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:13 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:4 msgid "For using as a Bot we are recommend the Appservice Discord bridge (the one being discussed here), because it supports plumbing." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:14 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:5 msgid "For personal use we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:16 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:7 msgid "The playbook can install and configure [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:18 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:9 msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-discord/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:20 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:11 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:22 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:13 msgid "Create a Discord Application [here](https://discordapp.com/developers/applications). Then retrieve Client ID, and create a bot from the Bot tab and retrieve the Bot token." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:24 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:15 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:26 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:17 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:40 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:42 -msgid "There are some additional things you may wish to configure about the bridge." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:44 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:46 -msgid "`roles/custom/matrix-bridge-appservice-discord/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:31 +msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:47 -msgid "`roles/custom/matrix-bridge-appservice-discord/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_appservice_discord_configuration_extension_yaml` variable" +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:33 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:49 -msgid "Installing" +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:40 +msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:51 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:42 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:58 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:44 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:60 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:46 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:63 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:48 msgid "Self-Service Bridging (Manual)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:65 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:50 msgid "Self-service bridging allows you to bridge specific and existing Matrix rooms to specific Discord rooms. To enable it, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:71 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:56 msgid "**Note**: If self-service bridging is not enabled, `!discord help` commands will return no results." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:73 -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:97 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:58 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:82 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:75 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:60 msgid "Once self-service is enabled, start a chat with `@_discord_bot:example.com` and say `!discord help bridge`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:77 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:62 msgid "Then, follow the instructions in the help output message." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:79 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:64 msgid "If the bot is not already in the Discord server, follow the provided invite link. This may require you to be a administrator of the Discord server." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:81 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:66 msgid "On the Discord side, send `!matrix help` to the bot to see the available commands for managing the bridge and Matrix users." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:83 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:68 msgid "**Note**: Encrypted Matrix rooms are not supported as of writing." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:85 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:70 msgid "Portal Bridging (Automatic)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:87 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:72 msgid "Through portal bridging, Matrix rooms will automatically be created by the bot and bridged to the relevant Discord room. This is done by simply joining a room with a specific name pattern (`#_discord__`)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:89 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:74 msgid "All Matrix rooms created this way are **listed publicly** by default, and you will not have admin permissions to change this. To get more control, [make yourself a room Administrator](#getting-administrator-access-in-a-portal-bridged-room). You can then unlist the room from the directory and change the join rules." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:91 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:76 msgid "To disable portal bridging, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:99 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:84 msgid "To get started with Portal Bridging:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:101 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:86 msgid "To invite the bot to Discord, retrieve the invite link from the `{{ matrix_appservice_discord_config_path }}/invite_link` file on the server (this defaults to `/matrix/appservice-discord/config/invite_link`). You need to peek at the file on the server via SSH, etc., because it's not available via HTTP(S)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:102 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:87 msgid "Room addresses follow this syntax: `#_discord__`. You can easily find the guild and channel IDs by logging into Discord in a browser and opening the desired channel. The URL will have this format: `discord.com/channels//`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:103 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:88 msgid "Once you have figured out the appropriate room address, you can join by doing `/join #_discord__` in your Matrix client." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:105 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:90 msgid "Getting Administrator access in a portal bridged room" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:107 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:92 msgid "By default, you won't have Administrator access in rooms created by the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:109 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:94 msgid "To adjust room access privileges or do various other things (change the room name subsequently, etc.), you'd wish to become an Administrator." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:111 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:96 msgid "There's the Discord bridge's guide for [setting privileges on bridge managed rooms](https://github.com/matrix-org/matrix-appservice-discord/blob/master/docs/howto.md#set-privileges-on-bridge-managed-rooms). To do the same with our container setup, run the following command on the server:" msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:118 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:120 -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-discord`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:122 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:124 -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 (adapt to your needs) and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po index d4a6e0734..21ade5894 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,88 +18,60 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:10 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:1 msgid "Setting up Appservice IRC bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:12 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:3 msgid "**Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [Heisenbridge](configuring-playbook-bridge-heisenbridge.md) bridge supported by the playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:14 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:5 msgid "The playbook can install and configure the [matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc) bridge for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:16 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:7 msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-irc/blob/master/HOWTO.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:18 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:9 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:20 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:11 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:72 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:74 -msgid "There are some additional things you may wish to configure about the bridge." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:76 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:78 -msgid "`roles/custom/matrix-bridge-appservice-irc/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:63 +msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:79 -msgid "`roles/custom/matrix-bridge-appservice-irc/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_irc_configuration_extension_yaml` variable" +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:65 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:81 -msgid "Installing" +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:72 +msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:83 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:74 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:90 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:76 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:92 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:78 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:94 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:80 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:96 +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:82 msgid "To use the bridge, you need to start a chat with `@irc_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:98 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:100 -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-irc`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:102 -msgid "Configuring for logging" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:104 -msgid "The default logging level for this component is `debug`, and the log is output to the console only. If you want to change the verbosity or enable logging to a file, add the following configuration to your `vars.yml` file (adapt to your needs) and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po index 59574d388..237f73e5e 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,112 +18,104 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:10 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:1 msgid "Setting up Appservice Kakaotalk bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:12 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:3 msgid "The playbook can install and configure [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) for you, for bridging to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG). This bridge is based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:14 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:5 msgid "See the project's [documentation](https://src.miscworks.net/fair/matrix-appservice-kakaotalk/src/branch/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:16 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:7 msgid "[!WARNING] There have been recent reports (~2022-09-16) that **using this bridge may get your account banned**." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:19 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:10 msgid "Prerequisite (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:21 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:12 msgid "Enable Shared Secret Auth" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:23 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:14 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:25 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:16 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-appservice-kakaotalk.md:27 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:18 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-appservice-kakaotalk.md:29 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:20 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:31 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:22 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:37 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:28 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:39 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:30 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:41 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:32 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:43 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:34 msgid "`roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:44 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:35 msgid "`roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_appservice_kakaotalk_configuration_extension_yaml` variable" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:46 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:37 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:48 +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:39 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.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-appservice-kakaotalk.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-appservice-kakaotalk.md:59 -msgid "Usage" +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:46 +msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:61 -msgid "To use the bridge, you need to start a chat with `@kakaotalkbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:48 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:63 -msgid "You then need to send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable bridging for your Kakaotalk account. The `--save` flag may be omitted, if you'd rather not save your password." +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:50 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:65 -msgid "Troubleshooting" +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:52 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:67 -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-kakaotalk`." +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:54 +msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:69 -msgid "Increase logging verbosity" +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:56 +msgid "To use the bridge, you need to start a chat with `@kakaotalkbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:71 -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-appservice-kakaotalk.md:58 +msgid "You then need to send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable bridging for your Kakaotalk account. The `--save` flag may be omitted, if you'd rather not save your password." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po index 606a8fa0b..cfe628372 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,24 +18,250 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:22 -msgid "Setting up Appservice Slack bridging (optional, removed)" +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:1 +msgid "Setting up Appservice Slack bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:3 +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:89 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:4 +msgid "Bridging to [Slack](https://slack.com) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:5 +msgid "Currently (as of November, 2024) **this component is not available for new installation unless you have already created a classic Slack application** (which the bridge makes use of in order to enable bridging between Slack and Matrix), because the creation of classic Slack applications has been discontinued since June 4 2024. The author of the bridge claims [here](https://github.com/matrix-org/matrix-appservice-slack/issues/789#issuecomment-2172947787) that he plans to support the modern Slack application and until then \"the best (and only) option for new installations is to use the webhook bridging\"." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:7 +msgid "The playbook can install and configure [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:9 +msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-slack/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:13 +msgid "Create a Classic Slack App" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:15 +msgid "First, you need to create a Classic Slack App [here](https://api.slack.com/apps?new_classic_app=1)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:17 +msgid "Name the app \"matrixbot\" (or anything else you'll remember). Select the team/workspace this app will belong to. Click on bot users and add a new bot user. We will use this account to bridge the the rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:19 +msgid "Then, click on Event Subscriptions and enable them and use the request url: `https://matrix.example.com/appservice-slack`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:21 +msgid "Add the following events as `Bot User Events` and save:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:23 +msgid "team_domain_change" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:24 -msgid "🪦 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." +msgid "message.channels" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:25 +msgid "message.groups (if you want to bridge private channels)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:26 -msgid "**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." +msgid "reaction_added" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:27 +msgid "reaction_removed" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:29 +msgid "Next, click on \"OAuth & Permissions\" and add the following scopes:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:31 +msgid "chat:write:bot" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:32 +msgid "users:read" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:33 +msgid "reactions:write" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:34 +msgid "files:write:user (if you want to bridge files)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:36 +msgid "**Note**: In order to make Slack files visible to Matrix users, this bridge will make Slack files visible to anyone with the url (including files in private channels). This is different than the current behavior in Slack, which only allows authenticated access to media posted in private channels. See MSC701 for details." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:38 +msgid "Click on \"Install App\" and \"Install App to Workspace\". Note the access tokens shown. You will need the Bot User OAuth Access Token and if you want to bridge files, the OAuth Access Token whenever you link a room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:40 +msgid "Create an administration control room on Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:42 +msgid "Create a new Matrix room to act as the administration control room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:44 +msgid "Note its internal room ID. This can be done in Element Web by sending a message, opening the options for that message and choosing \"view source\". The room ID will be displayed near the top." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:46 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:48 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:64 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:66 +msgid "There are some additional things you may wish to configure about the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:68 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:70 +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:71 +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:73 +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:80 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:82 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:91 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:93 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:95 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:97 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:99 +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:101 +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:103 +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:104 +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:105 +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//details/`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:106 +msgid "Issue a link command in the administration control room with these collected values as arguments:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:108 +msgid "with file bridging:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:114 +msgid "without file bridging:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:120 +msgid "These arguments can be shortened to single-letter forms:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:126 +msgid "Unlinking" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:128 +msgid "Channels can be unlinked again by sending this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:134 +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:136 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:138 +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:140 +msgid "Linking: \"Room is now pending-name\"" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:142 +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:144 +msgid "Messages work from Matrix to Slack, but not the other way around" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:146 +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:28 -msgid "Uninstalling the component manually" +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:148 +#, python-format +msgid "`WARN SlackEventHandler Ignoring message from unrecognised Slack channel ID : %s (%s) `" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:30 -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:" +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:150 +msgid "This may particularly hit you, if you tried to unsuccessfully link your room multiple times without unlinking it after each failed attempt." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po index eb9925f60..a0709fde0 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,24 +18,96 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:16 -msgid "Setting up Appservice Webhooks bridging (optional, removed)" +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:1 +msgid "Setting up Appservice Webhooks bridging (optional, deprecated)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:18 -msgid "🪦 The playbook used to be able to install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks), but no longer includes this component, as it has been deprecated since more than several years." +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:3 +msgid "**Note**: This bridge has been deprecated. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bridge instead of this one." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:20 -msgid "You may wish to use [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) instead." +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:5 +msgid "The playbook can install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:22 -msgid "Uninstalling the bridge manually" +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:7 +msgid "See the project's [documentation](https://github.com/turt2live/matrix-appservice-webhooks/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:24 -msgid "If you still have matrix-appservice-webhooks 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:" +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:11 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:27 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:29 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:36 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:38 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:40 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:42 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:44 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:46 +msgid "To use the bridge, you need to invite the bridge bot user to your room in either way." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:48 +msgid "Send `/invite @_webhook:example.com` (**Note**: Make sure you have administration permissions in your room)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:49 +msgid "Add the bridge bot to a private channel (personal channels imply you being an administrator)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:51 +msgid "You then need to send a message to the bridge bot to receive a private message including the webhook link:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:57 +msgid "The JSON body for posting messages will have to look like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:68 +msgid "You can test this via curl like so:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:81 +msgid "Setting Webhooks with Dimension integration manager" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:83 +msgid "If you're using the [Dimension integration manager](configuring-playbook-dimension.md), you can configure the Webhooks bridge with it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:85 +msgid "To configure it, open the Dimension integration manager, and go to \"Settings\" and \"Bridges\", then select edit action for \"Webhook Bridge\"." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:87 +msgid "On the UI, press \"Add self-hosted Bridge\" button and populate \"Provisioning URL\" and \"Shared Secret\" values from `/matrix/appservice-webhooks/config/config.yaml` file's homeserver URL value and provisioning secret value, respectively." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po index 283de0195..02223fc9e 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,112 +18,108 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:11 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:1 msgid "Setting up Beeper Linkedin bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:13 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:3 msgid "The playbook can install and configure [beeper-linkedin](https://github.com/beeper/linkedin) for you, for bridging to [LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on the mautrix-python framework and can be configured in a similar way to the mautrix bridges." msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:15 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:5 msgid "See the project's [documentation](https://github.com/beeper/linkedin/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:17 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:7 msgid "Prerequisite" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:19 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:9 msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:21 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:11 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [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-beeper-linkedin.md:23 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:13 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-beeper-linkedin.md:25 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:15 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-beeper-linkedin.md:27 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:29 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:19 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:35 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:25 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:37 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:27 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:39 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:29 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-beeper-linkedin.md:41 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:31 msgid "**Note**: when following the guide to configure the bridge, make sure to replace `_mautrix_SERVICENAME_` in the variable names with `_beeper_linkedin_`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:43 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:33 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:45 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:35 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:52 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:42 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:44 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:46 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:54 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:48 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:56 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:50 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:58 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:52 msgid "To use the bridge, you need to start a chat with `@linkedinbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:60 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:54 msgid "You then need to send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to enable bridging for your LinkedIn account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:62 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:56 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:64 -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-beeper-linkedin`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:66 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:68 -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 "" - -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:74 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:58 msgid "Bridge asking for 2FA even if you don't have 2FA enabled" msgstr "" -#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:76 +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:60 msgid "If you don't have 2FA enabled and are logging in from a strange IP for the first time, LinkedIn will send an email with a one-time code. You can use this code to authorize the bridge session. In my experience, once the IP is authorized, you will not be asked again." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po index 6bc3ee5fa..69b5722d1 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,20 +18,92 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:12 -msgid "Setting up Go Skype Bridge bridging (optional, removed)" +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:1 +msgid "Setting up Go Skype Bridge bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:14 -msgid "🪦 The playbook used to be able to install and configure [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge), but no longer includes this component, as Skype has been discontinued since May 2025." +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:3 +msgid "The playbook can install and configure [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) for you, for bridging to [Skype](https://www.skype.com/). This bridge was created based on [mautrix-whatsapp](https://github.com/mautrix/whatsapp) and can be configured in a similar way to it." msgstr "" -#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:16 -msgid "Uninstalling the bridge manually" +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:5 +msgid "See the project's [documentation](https://github.com/kelaresg/go-skype-bridge/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:18 -msgid "If you still have the Go Skype bridge 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:" +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:7 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:9 +msgid "Enable Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:11 +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:13 +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-go-skype-bridge.md:15 +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-go-skype-bridge.md:17 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:19 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:25 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:27 +msgid "There are some additional things you may wish to configure about the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:29 +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-go-skype-bridge.md:31 +msgid "**Note**: when following the guide to configure the bridge, make sure to replace `_mautrix_SERVICENAME_` in the variable names with `_go_skype_bridge_`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:33 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:35 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:42 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:44 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:46 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:48 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:50 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:52 +msgid "To use the bridge, you need to start a chat with `@skypebridgebot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po index ad121056a..7757f8e39 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,120 +18,104 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:9 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:1 msgid "Setting up Heisenbridge bouncer-style IRC bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:11 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:3 msgid "**Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md) bridge supported by the playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:13 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:5 msgid "The playbook can install and configure [Heisenbridge](https://github.com/hifi/heisenbridge) — the bouncer-style [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) bridge for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:15 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:7 msgid "See the project's [documentation](https://github.com/hifi/heisenbridge/blob/master/README.md) to learn what it does and why it might be useful to you. You can also take a look at [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:17 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:9 msgid "Adjusting DNS records (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:19 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:11 msgid "By default, this playbook installs Heisenbridge on the `matrix.` subdomain, at the `/heisenbridge` path (https://matrix.example.com/heisenbridge). It would handle media requests there (see the [release notes for Heisenbridge v1.15.0](https://github.com/hifi/heisenbridge/releases/tag/v1.15.0)). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:21 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:13 msgid "If you wish to adjust it, see the section [below](#adjusting-the-heisenbridge-url-optional) for details about DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:23 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:15 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:25 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:17 msgid "To enable Heisenbridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:38 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:30 msgid "Adjusting the Heisenbridge URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:40 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:32 msgid "By tweaking the `matrix_heisenbridge_hostname` and `matrix_heisenbridge_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:42 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:34 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:50 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:42 msgid "If you've changed the default hostname, you may need to create a CNAME record for the Heisenbridge domain (`heisenbridge.example.com`), which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:52 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:44 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:54 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:56 -msgid "There are some additional things you may wish to configure about the bridge." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:58 -msgid "Take a look at:" +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:46 +msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:60 -msgid "`roles/custom/matrix-bridge-heisenbridge/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:48 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:62 -msgid "Installing" +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:55 +msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:64 -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:" +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:57 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:71 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:59 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:73 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:61 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:75 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:63 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:77 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:65 msgid "To use the bridge, you need to start a chat with `@heisenbridge:example.com` (where `example.com` is your base domain, not the `matrix.` domain). If the bridge ignores you and a DM is not accepted then the owner setting may be wrong." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:79 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:67 msgid "Help is available for all commands with the `-h` switch." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:81 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:69 msgid "You can also learn the basics by watching [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:83 +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:71 msgid "If you encounter issues or feel lost you can join the project room at [#heisenbridge:vi.fi](https://matrix.to/#/#heisenbridge:vi.fi) for help." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:85 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:87 -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-heisenbridge`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po index 48ddce094..8b237cb4e 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,137 +18,141 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:11 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:1 msgid "Setting up matrix-hookshot (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:13 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:3 msgid "The playbook can install and configure [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:15 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:5 msgid "Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) from software project management services such as GitHub, GitLab, Jira, and Figma, as well as generic webhooks." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:17 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:7 msgid "See the project's [documentation](https://matrix-org.github.io/matrix-hookshot/latest/hookshot.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:19 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:9 +msgid "**Note**: the playbook also supports [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), which however was deprecated by its author." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:11 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:21 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:13 msgid "Download GitHub app private key (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:23 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:15 msgid "If you're setting up the GitHub bridge, you need to create your GitHub app, and generate a private key file of it." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:25 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:17 msgid "You need to download the private key file, if you will install the file manually or with the `aux` role. For details, see [the section below](#manage-github-private-key-with-aux-role)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:27 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:19 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:29 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:21 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `GITHUB_PRIVATE_KEY_HERE` with the one created [above](#download-github-app-private-key)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:43 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:35 msgid "For each of the services (GitHub, GitLab, Jira, Figma, and generic webhooks) fill in the respective variables `matrix_hookshot_service_*` listed in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) as required." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:45 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:37 msgid "Take special note of the `matrix_hookshot_*_enabled` variables. Services that need no further configuration are enabled by default (GitLab and generic webhooks), while you must first add the required configuration and enable the others (GitHub, Jira, and Figma)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:47 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:39 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:49 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:41 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:51 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:43 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:53 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:45 msgid "`roles/custom/matrix-bridge-hookshot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:54 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:46 msgid "`roles/custom/matrix-bridge-hookshot/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_hookshot_configuration_extension_yaml` and `matrix_hookshot_registration_extension_yaml` variables" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:56 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:48 msgid "Refer the [official instructions](https://matrix-org.github.io/matrix-hookshot/latest/setup.html) and the comments in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) to learn what the individual options do." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:58 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:50 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:60 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:52 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:67 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:59 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service hookshot` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:69 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:61 msgid "`just install-service hookshot` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:71 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:63 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:73 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:65 msgid "To use the bridge, you need to create a room and invite the Hookshot bot (`@hookshot:example.com`) to it." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:75 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:67 msgid "Make sure the bot is able to send state events (usually the Moderator power level in clients)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:77 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:69 msgid "Send `!hookshot help` to the bot to see the available commands." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:79 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:71 msgid "Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-hookshot/latest/usage.html) for more details about using the bridge's various features." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:81 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:73 msgid "💡 **Note**: the different listeners are bound to certain paths which might differ from those assumed by the hookshot documentation. See [URLs for bridges setup](#urls-for-bridges-setup) below." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:83 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:75 msgid "Reset crypto store" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:85 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:77 msgid "Should the crypto store be corrupted, you can reset it by executing this Ansible playbook with the tag `reset-hookshot-encryption` added:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:91 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:83 msgid "More setup documentation" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:93 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:85 msgid "URLs for bridges setup" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:95 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:87 msgid "Unless indicated otherwise, the following endpoints are reachable on your `matrix.` subdomain (if the feature is enabled)." msgstr "" @@ -248,6 +252,22 @@ msgstr "" msgid "Figma" msgstr "" +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "provisioning" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/v1/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_provisioning_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Dimension [provisioning](#provisioning-api)" +msgstr "" + #: ../../../docs/configuring-playbook-bridge-hookshot.md msgid "appservice" msgstr "" @@ -280,98 +300,114 @@ msgstr "" msgid "Widgets" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:107 +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "metrics" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/metrics/hookshot`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_metrics_enabled` and exposure enabled via `matrix_hookshot_metrics_proxying_enabled` or `matrix_metrics_exposure_enabled`. Read more in the [Metrics section](#metrics) below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Prometheus" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:101 msgid "Also see the various `matrix_hookshot_container_labels_*` variables in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), which expose URLs publicly." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:109 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:103 msgid "The different listeners are also reachable *internally* in the docker-network via the container's name (configured by `matrix_hookshot_container_url`) and on different ports (e.g. `matrix_hookshot_appservice_port`). Read [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) in detail for more info." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:111 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:105 msgid "Manage GitHub Private Key with aux role" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:113 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:107 msgid "The GitHub bridge requires you to install a private key file. This can be done in multiple ways:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:115 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:109 msgid "copy the *contents* of the downloaded file and set the variable `matrix_hookshot_github_private_key` to the contents (see example in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml))." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:116 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:110 msgid "somehow copy the file to the path `{{ matrix_hookshot_base_path }}/{{ matrix_hookshot_github_private_key_file }}` (default: `/matrix/hookshot/private-key.pem`) on the server manually." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:117 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:111 msgid "use the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) to copy the file from an arbitrary path on your ansible client to the correct path on the server." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:119 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:113 msgid "To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:130 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:124 msgid "For more information, see the documentation in the [default configuration of the aux role](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:132 -msgid "Enable metrics" +#: ../../../docs/configuring-playbook-bridge-hookshot.md:126 +msgid "Provisioning API" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:134 -msgid "The playbook can enable and configure the metrics of the service for you." +#: ../../../docs/configuring-playbook-bridge-hookshot.md:128 +msgid "The provisioning API will be enabled automatically if you set `matrix_dimension_enabled: true` and provided a `matrix_hookshot_provisioning_secret`, unless you override it either way. To use hookshot with dimension, you will need to enter as \"Provisioning URL\": `http://matrix-hookshot:9002`, which is made up of the variables `matrix_hookshot_container_url` and `matrix_hookshot_provisioning_port`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:136 -msgid "Metrics are **only enabled by default** if the builtin [Prometheus](configuring-playbook-prometheus-grafana.md) is enabled (by default, Prometheus isn't enabled). If so, metrics will automatically be collected by Prometheus and made available in Grafana. You will, however, need to set up your own Dashboard for displaying them." +#: ../../../docs/configuring-playbook-bridge-hookshot.md:130 +msgid "Metrics" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:138 -msgid "To enable the metrics, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-bridge-hookshot.md:132 +msgid "Metrics are **only enabled by default** if the builtin [Prometheus](configuring-playbook-prometheus-grafana.md) is enabled (by default, Prometheus isn't enabled). If so, metrics will automatically be collected by Prometheus and made available in Grafana. You will, however, need to set up your own Dashboard for displaying them." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:145 -msgid "**To collect metrics from an external Prometheus server**, besides enabling metrics as described above, you will also need to enable metrics exposure on `https://matrix.example.com/metrics/hookshot` by adding the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-bridge-hookshot.md:134 +msgid "To explicitly enable metrics, use `matrix_hookshot_metrics_enabled: true`. This only exposes metrics over the container network, however." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:151 -msgid "By default metrics are exposed publicly **without** password-protection. To password-protect the metrics with dedicated credentials, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-bridge-hookshot.md:136 +msgid "**To collect metrics from an external Prometheus server**, besides enabling metrics as described above, you will also need to enable metrics exposure on `https://matrix.example.com/metrics/hookshot` by:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:158 -msgid "To `matrix_hookshot_container_labels_metrics_middleware_basic_auth_users`, set the Basic Authentication credentials (raw `htpasswd` file content) used to protect the endpoint. See https://doc.traefik.io/traefik/middlewares/http/basicauth/#users for details about it." +#: ../../../docs/configuring-playbook-bridge-hookshot.md:138 +msgid "either enabling metrics exposure for Hookshot via `matrix_hookshot_metrics_proxying_enabled: true`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:160 -msgid "**Note**: alternatively, you can use `matrix_metrics_exposure_enabled` to expose all services on this `/metrics/*` feature, and you can use `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users` to password-protect the metrics of them. See [this section](configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) for more information." +#: ../../../docs/configuring-playbook-bridge-hookshot.md:139 +msgid "or enabling metrics exposure for all services via `matrix_metrics_exposure_enabled: true`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:162 -msgid "Enable Grafana (optional)" +#: ../../../docs/configuring-playbook-bridge-hookshot.md:141 +msgid "Whichever one you go with, by default metrics are exposed publicly **without** password-protection. See [the Prometheus and Grafana docs](configuring-playbook-prometheus-grafana.md) for details about password-protection for metrics." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:164 -msgid "Probably you wish to enable Grafana along with Prometheus for generating graphs of the metrics." +#: ../../../docs/configuring-playbook-bridge-hookshot.md:143 +msgid "Collision with matrix-appservice-webhooks" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:166 -msgid "To enable Grafana, see [this section](configuring-playbook-prometheus-grafana.md#adjusting-the-playbook-configuration-grafana) for instructions." +#: ../../../docs/configuring-playbook-bridge-hookshot.md:145 +msgid "If you are also running [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), it reserves its namespace by the default setting `matrix_appservice_webhooks_user_prefix: '_webhook_'`. You should take care if you modify its or hookshot's prefix that they do not collide with each other's namespace (default `matrix_hookshot_generic_userIdPrefix: '_webhooks_'`)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:168 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:147 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:170 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-hookshot`." +#: ../../../docs/configuring-playbook-bridge-hookshot.md:149 +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-bridge-hookshot`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:172 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:151 msgid "Increase logging verbosity" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:174 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:153 msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po index b72ebad42..cd3149443 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,80 +18,64 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:9 +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:1 msgid "Setting up Matrix SMS bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:11 +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:3 msgid "The playbook can install and configure [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:13 +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:5 msgid "See the project's [documentation](https://github.com/benkuly/matrix-sms-bridge/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:15 +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:7 msgid "Prerequisite" msgstr "" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:17 +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:9 msgid "The bridge uses [android-sms-gateway-server](https://github.com/RebekkaMa/android-sms-gateway-server). You need to configure it first." msgstr "" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:19 +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:11 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:21 +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:13 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:43 -msgid "Extending the configuration" +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:36 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:38 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:45 -msgid "There are some additional things you may wish to configure about the bridge." +msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:47 -msgid "Take a look at:" +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:49 -msgid "`roles/custom/matrix-bridge-sms/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_sms_bridge_configuration_extension_yaml` variable" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:51 -msgid "Installing" +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:53 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:60 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:62 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:64 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:66 +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:55 msgid "Read the [user guide](https://github.com/benkuly/matrix-sms-bridge/blob/master/README.md#user-guide) to see how this bridge works." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:68 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:70 -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-sms-bridge`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-bluesky.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-bluesky.po deleted file mode 100644 index 5821d74b2..000000000 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-bluesky.po +++ /dev/null @@ -1,125 +0,0 @@ -# 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 , 2026. -# -#, fuzzy -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" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: jp\n" -"Language-Team: jp \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-bridge-mautrix-bluesky.md:9 -msgid "Setting up Mautrix Bluesky bridging (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:11 -msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:13 -msgid "The playbook can install and configure [mautrix-bluesky](https://github.com/mautrix/bluesky) for you, which provides a bridge to [Bluesky](https://bsky.social/about)." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:15 -msgid "See the project's [documentation](https://github.com/mautrix/bluesky/blob/master/README.md) to learn what it does and why it might be useful to you." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:17 -msgid "Prerequisite (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:19 -msgid "Enable Appservice Double Puppet" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:21 -msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:23 -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-bluesky.md:25 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:27 -msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:33 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:35 -msgid "There are some additional things you may wish to configure about the bridge." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:38 -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-bluesky.md:40 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:42 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:49 -msgid "**Notes**:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:51 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:53 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:55 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:57 -msgid "To use the bridge, you need to start a chat with `@blueskybot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:59 -msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/bluesky/authentication.html)." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:61 -msgid "After logging in, the bridge will create portal rooms for recent chats. Portal rooms for other chats will be created as you receive messages." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:63 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:65 -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-bluesky`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:67 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bluesky.md:69 -msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-bridges.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-bridges.po index 6749f3171..19d1de68e 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-bridges.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-bridges.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,281 +18,286 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:10 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:1 msgid "Setting up a Generic Mautrix Bridge (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:12 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:3 msgid "The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, discord, signal, googlechat, etc.), as well as many other (non-mautrix) bridges. This is a common guide for configuring mautrix bridges." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:14 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:5 msgid "The author of the bridges maintains [the official docs](https://docs.mau.fi/bridges/index.html), whose source code is available at [mautrix/docs](https://github.com/mautrix/docs) repository on GitHub. You may as well to refer it while configuring them." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:16 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:7 msgid "You can see each bridge's features on the `ROADMAP.md` file in its corresponding mautrix repository." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:18 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:9 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:20 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:11 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:27 -msgid "**Note**: for bridging to Meta's Messenger or Instagram, you would need to add `meta` with an underscore symbol (`_`) or hyphen (`-`) based on the context as prefix to each `SERVICENAME`; add `_` to variables (as in `matrix_mautrix_meta_messenger_configuration_extension_yaml` for example) and `-` to paths of the configuration files (as in `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2`), respectively." +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:18 +msgid "**Note**: for bridging to Meta's Messenger or Instagram, you would need to add `meta` with an underscore symbol (`_`) or hyphen (`-`) based on the context as prefix to each `SERVICENAME`; add `_` to variables (as in `matrix_mautrix_meta_messenger_configuration_extension_yaml` for example) and `-` to paths of the configuration files (as in `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2`), respectively. **`matrix_mautrix_facebook_*` and `matrix_mautrix_instagram_*` variables belong to the deprecated components and do not control the new bridge** ([mautrix-meta](https://github.com/mautrix/meta)), which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:29 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:20 msgid "There are some additional things you may wish to configure about the bridge before you continue. Each bridge may have additional requirements besides `_enabled: true`. For example, the mautrix-telegram bridge (our documentation page about it is [here](configuring-playbook-bridge-mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and `matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each bridge's individual documentation page for details about enabling bridges." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:31 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:22 msgid "Configure bridge permissions (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:33 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:24 msgid "By default any user on your homeserver will be able to use the mautrix bridges. To limit who can use them you would need to configure their permissions settings." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:35 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:26 msgid "Different levels of permission can be granted to users. For example, to **configure a user as an administrator for all bridges**, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:41 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:32 msgid "If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:43 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:34 msgid "**Alternatively** (more verbose, but allows multiple admins to be configured), you can do the same on a per-bridge basis with:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:52 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:43 msgid "This will add the admin permission to the specific user, while keeping the default permissions." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:54 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:45 msgid "You could also redefine the default permissions settings completely, rather than adding extra permissions. You may wish to look at `roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` to find information on the permission settings and other options you would like to configure." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:56 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:47 msgid "Enable encryption (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:58 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:49 msgid "[Encryption (End-to-Bridge Encryption, E2BE) support](https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html) is off by default. If you would like to enable encryption, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:60 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:51 msgid "**for all bridges with encryption support**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:67 -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:86 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:58 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:77 msgid "**Alternatively**, for a specific bridge:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:74 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:65 msgid "Enable relay mode (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:76 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:67 msgid "[Relay mode](https://docs.mau.fi/bridges/general/relay-mode.html) is off by default. Check [the table on the official documentation](https://docs.mau.fi/bridges/general/relay-mode.html#support-table) for bridges which support relay mode." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:78 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:69 msgid "If you would like to enable it, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:80 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:71 msgid "**for all bridges with relay mode support**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:95 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:86 msgid "You can only have one `matrix_mautrix_SERVICENAME_configuration_extension_yaml` definition in `vars.yml` per bridge, so if you need multiple pieces of configuration there, just merge them like this:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:109 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:100 msgid "If you want to activate the relaybot in a room, send `!prefix set-relay` in the rooms where you want to use the bot (replace `!prefix` with the appropriate command prefix for the bridge, like `!signal` or `!wa`). To deactivate, send `!prefix unset-relay`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:111 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:102 msgid "Use `!prefix set-pl 100` to be able for the bot to modify room settings and invite others." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:113 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:104 msgid "Allow anyone on the homeserver to become a relay user (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:115 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:106 msgid "By default, only admins are allowed to set themselves as relay users. To allow anyone on your homeserver to set themselves as relay users, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:121 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:112 msgid "Set the bot's username (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:123 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:114 msgid "To set the bot's username, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:129 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:120 msgid "Configure the logging level (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:131 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:122 msgid "To specify the logging level, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:137 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:128 msgid "Replace `warn` with one of the following to control the verbosity of the logs generated: `trace`, `debug`, `info`, `warn`, `error` or `fatal`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:139 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:130 msgid "If you have issues with a service, and are requesting support, the higher levels of logging (those that appear earlier in the list, like `trace`) will generally be more helpful." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:141 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:132 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:143 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:134 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:145 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:136 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:147 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:138 msgid "`roles/custom/matrix-bridge-mautrix-SERVICENAME/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:148 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:139 msgid "`roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_mautrix_SERVICENAME_configuration_extension_yaml` variable" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:150 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:141 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:152 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:143 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:159 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:150 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:190 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:152 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:154 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-bridges.md:161 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:156 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:163 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:158 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:165 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:160 msgid "To use the bridge, you need to start a chat with `@SERVICENAMEbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:167 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:162 msgid "For details about the next steps, refer to each bridge's individual documentation page." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:169 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:164 msgid "Send `help` to the bot to see the available commands." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:171 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:166 msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:173 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:168 msgid "Set up Double Puppeting (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:175 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:170 msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:177 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:172 msgid "To set it up, you have 2 ways of going about it." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:179 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:174 msgid "Method 1: automatically, by enabling Appservice Double Puppet (recommended)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:181 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:176 msgid "To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html), you could enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:183 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:178 msgid "Appservice Double Puppet is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:185 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:180 msgid "To enable the Appservice Double Puppet service, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:191 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:186 msgid "When enabled, double puppeting will automatically be enabled for all bridges that support double puppeting via the appservice method." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:193 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:188 msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:195 -msgid "**Notes**:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:197 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:192 msgid "Previously there were multiple different automatic double puppeting methods like one with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but they have been superseded by this Appservice Double Puppet method. Double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future as the older methods were completely removed in the megabridge rewrites on [the upstream project](https://docs.mau.fi/bridges/general/double-puppeting.html#automatically)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:200 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:195 msgid "Some bridges like [the deprecated Facebook mautrix bridge](configuring-playbook-bridge-mautrix-facebook.md) and [matrix-appservice-kakaotalk](configuring-playbook-bridge-appservice-kakaotalk.md), which is partially based on the Facebook bridge, are compatible with the Shared Secret Auth service only. These bridges automatically perform Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:202 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:197 msgid "Method 2: manually, by asking each user to provide a working access token" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:204 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:199 msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:206 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:201 msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:208 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:203 msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:210 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:205 msgid "make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:212 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:207 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:214 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:209 msgid "For troubleshooting information with a specific bridge, please see the playbook documentation about it (some other document in in `docs/`) and the upstream ([mautrix](https://github.com/mautrix)) bridge documentation for that specific bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:216 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:211 msgid "If the bridge's bot doesn't accept the invite to a chat, refer [the official troubleshooting page](https://docs.mau.fi/bridges/general/troubleshooting.html) as well." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:218 +#: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:213 msgid "If you found bugs in mautrix bridges, they should be reported to the upstream project, in the corresponding mautrix repository, not to us." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po index 0c5c20a96..0a8b1b689 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:13 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:1 msgid "Setting up Mautrix Discord bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:15 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:17 -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." +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:5 +msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md) bridges supported by the playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:19 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:6 +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:7 +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:9 msgid "The playbook can install and configure [mautrix-discord](https://github.com/mautrix/discord) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:21 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:11 msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/discord/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:23 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:13 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)." +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:15 +msgid "There are 2 ways to login to discord using this bridge, either by [scanning a QR code](#method-1-login-using-qr-code-recommended) using the Discord mobile app **or** by using a [Discord token](#method-2-login-using-discord-token-not-recommended)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:27 -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)." +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:17 +msgid "If this is a dealbreaker for you, consider using one of the other Discord bridges supported by the playbook: [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) or [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md). These come with their own complexity and limitations, however, so we recommend that you proceed with this one if possible." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:29 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:19 msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:31 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:21 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:33 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:23 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:35 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:25 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:37 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:27 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:39 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:29 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:45 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:35 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:47 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:37 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:50 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:40 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:52 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:42 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:54 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:44 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:61 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:51 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:53 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:55 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md: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." +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:57 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:65 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:59 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:67 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:61 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:69 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:63 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:71 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:65 msgid "After logging in, the bridge will create portal rooms for some recent direct messages." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:73 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:67 msgid "Bridge guilds" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:75 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:69 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:77 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:71 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:79 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:73 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 "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 "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 ` 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 "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 "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po index f388012a7..464579147 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,24 +18,144 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:16 -msgid "Setting up Mautrix Facebook bridging (optional, removed)" +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:1 +msgid "Setting up Mautrix Facebook bridging (optional, deprecated)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:18 -msgid "🪦 The playbook used to be able to install and configure [mautrix-facebook](https://github.com/mautrix/facebook), but no longer includes this component, as it has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge." +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:3 +msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:20 -msgid "The mautrix-meta bridge can be [installed using this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md)." +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:5 +msgid "**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md). Consider using that bridge instead of this one." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:22 -msgid "Uninstalling the bridge manually" +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:7 +msgid "The playbook can install and configure [mautrix-facebook](https://github.com/mautrix/facebook) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:24 -msgid "If you still have the bridge 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:" +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:9 +msgid "See the project's [documentation](https://github.com/mautrix/facebook/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:11 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:13 +msgid "Enable Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:15 +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:17 +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-facebook.md:19 +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-facebook.md:21 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:23 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:29 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:31 +msgid "There are some additional things you may wish to configure about the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:33 +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-facebook.md:35 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:37 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:44 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:46 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:48 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:50 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:52 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:54 +msgid "To use the bridge, you need to start a chat with `@facebookbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:56 +msgid "You then need to send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable bridging for your Facebook Messenger account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:58 +msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:60 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:62 +msgid "Facebook rejecting login attempts and forcing you to change password" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:64 +msgid "If your Matrix server is in a wildly different location than where you usually use your Facebook account from, the bridge's login attempts may be outright rejected by Facebook. Along with that, Facebook may even force you to change the account's password." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:66 +msgid "If you happen to run into this problem while [setting up bridging](#usage), try to first get a successful session up by logging in to Facebook through the Matrix server's IP address." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:68 +msgid "The easiest way to do this may be to use [sshuttle](https://sshuttle.readthedocs.io/) to proxy your traffic through the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:70 +msgid "Example command for proxying your traffic through the Matrix server:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:76 +msgid "Once connected, you should be able to verify that you're browsing the web through the Matrix server's IP by checking [icanhazip](https://icanhazip.com/)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:78 +msgid "Then proceed to log in to [Facebook/Messenger](https://www.facebook.com/)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:80 +msgid "Once logged in, proceed to [set up bridging](#usage)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:82 +msgid "If that doesn't work, enable 2FA (see: [Facebook help page on enabling 2FA](https://www.facebook.com/help/148233965247823)) and try to login again with a new password, and entering the 2FA code when prompted, it may take more then one try, in between attempts, check facebook.com to see if they are requiring another password change" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po index 297bc7ee8..45dd473a0 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,104 +18,96 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:9 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:1 msgid "Setting up Mautrix Google Messages bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:11 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:13 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:5 msgid "The playbook can install and configure [mautrix-gmessages](https://github.com/mautrix/gmessages) for you, for bridging to [Google Messages](https://messages.google.com/)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:15 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:7 msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/gmessages/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:17 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:9 msgid "Prerequisite (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:19 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:11 msgid "Enable Appservice Double Puppet" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:21 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:13 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:23 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:15 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-gmessages.md:25 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:27 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:19 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:33 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:25 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:35 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:27 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:38 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:30 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-gmessages.md:40 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:32 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:42 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:34 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:49 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:41 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:43 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md: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-bridge-mautrix-gmessages.md:51 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.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-bridge-mautrix-gmessages.md:53 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:49 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:55 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:51 msgid "To use the bridge, you need to start a chat with `@gmessagesbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:57 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:53 msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/gmessages/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:59 +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:55 msgid "After logging in, the bridge will create portal rooms for recent chats." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:61 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:63 -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-gmessages`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:65 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:67 -msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po index 5e553597f..9bf8adeae 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,108 +18,100 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:10 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:1 msgid "Setting up Mautrix Google Chat bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:12 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:14 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:5 msgid "The playbook can install and configure [mautrix-googlechat](https://github.com/mautrix/googlechat) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:16 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:7 msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/googlechat/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:18 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:9 msgid "Prerequisite (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:20 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:11 msgid "Enable Appservice Double Puppet or Shared Secret Auth" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:22 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:13 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:24 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:15 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-googlechat.md:26 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:17 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-googlechat.md:28 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:19 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:30 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:21 msgid "To enable the [Google Chat](https://chat.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:36 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:27 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:38 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:29 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:41 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:32 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-googlechat.md:43 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:34 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:45 +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:36 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:52 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:54 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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-googlechat.md:56 -msgid "Usage" +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:43 +msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:58 -msgid "To use the bridge, you need to start a chat with `@googlechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:45 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:60 -msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html)." +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:47 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:62 -msgid "After logging in, the bridge will create portal rooms for recent chats. Portal rooms for other chats will be created as you receive messages." +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:49 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:64 -msgid "Troubleshooting" +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:51 +msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:66 -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-googlechat`." +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:53 +msgid "To use the bridge, you need to start a chat with `@googlechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:68 -msgid "Increase logging verbosity" +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:55 +msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:70 -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-googlechat.md:57 +msgid "After logging in, the bridge will create portal rooms for some recent chats. Portal rooms for other chats will be created as you receive messages." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po index 85677cd14..39c1b545f 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,24 +18,104 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:1 +msgid "Setting up Mautrix Hangouts bridging (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:3 +msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:5 +msgid "💡 **Note**: This bridge has been deprecated in favor of [Google Chat bridge](https://github.com/mautrix/googlechat), which can be installed using [this playbook](configuring-playbook-bridge-mautrix-googlechat.md). Installing the mautrix-hangouts bridge is **no longer possible**. For now, this documentation page remains here for historical purposes." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:7 +msgid "The playbook can install and configure [mautrix-hangouts](https://github.com/mautrix/hangouts) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:9 +msgid "Prerequisite (optional)" +msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:11 -msgid "Setting up Mautrix Hangouts bridging (optional, removed)" +msgid "Enable Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:13 -msgid "🪦 The playbook used to be able to install and configure [mautrix-hangouts](https://github.com/mautrix/hangouts), but no longer includes this component, because Google Hangouts has been discontinued since the 1st of November 2022." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:15 -msgid "You may wish to use the [Google Chat bridge](https://github.com/mautrix/googlechat) instead." +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-hangouts.md:17 -msgid "Uninstalling the bridge manually" +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-hangouts.md:19 -msgid "If you still have the Hangouts bridge 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:" +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:21 +msgid "To enable the [Google Hangouts](https://hangouts.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:27 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:29 +msgid "There are some additional things you may wish to configure about the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:31 +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-hangouts.md:33 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:35 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:42 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:44 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:46 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:48 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:50 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:52 +msgid "To use the bridge, you need to start a chat with `@hangoutsbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:54 +msgid "You then need to send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:56 +msgid "Automatic login may not work. If it does not, reload the page and select the \"Manual login\" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:58 +msgid "Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po index b13e23097..08e82de7e 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,24 +18,80 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:17 -msgid "Setting up Mautrix Instagram bridging (optional, removed)" +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:1 +msgid "Setting up Mautrix Instagram bridging (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:3 +msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:5 +msgid "**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-instagram.md). Consider using that bridge instead of this one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:7 +msgid "The playbook can install and configure [mautrix-instagram](https://github.com/mautrix/instagram) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:9 +msgid "See the project's [documentation](https://github.com/mautrix/instagram/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:13 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:19 -msgid "🪦 The playbook used to be able to install and configure [mautrix-instagram](https://github.com/mautrix/instagram), but no longer includes this component, as it has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge." +msgid "Extending the configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:21 -msgid "The mautrix-meta bridge can be [installed using this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md)." +msgid "There are some additional things you may wish to configure about the bridge." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:23 -msgid "Uninstalling the bridge manually" +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-instagram.md:25 -msgid "If you still have the bridge 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:" +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:27 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:34 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:36 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:38 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:40 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:42 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:44 +msgid "To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:46 +msgid "You then need to send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the bridge bot to enable bridging for your instagram/Messenger account." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po index 5d95366fe..119c8ba65 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,140 +18,132 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:8 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:1 msgid "Setting up Instagram bridging via Mautrix Meta (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:10 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:12 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:5 msgid "The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:14 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:7 msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/meta/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:16 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:9 msgid "Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:18 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:11 msgid "This documentation page only deals with the bridge's ability to bridge to Instagram. For bridging to Facebook/Messenger, see [Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:20 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:13 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:22 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:15 msgid "Migrating from the old mautrix-instagram bridge" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:24 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:17 msgid "If you've been using the [mautrix-instagram](./configuring-playbook-bridge-mautrix-instagram.md) bridge, **you'd better get rid of it first** or the 2 bridges will be in conflict:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:26 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:19 msgid "both trying to use `@instagrambot:example.com` as their username. This conflict may be resolved by adjusting `matrix_mautrix_instagram_appservice_bot_username` or `matrix_mautrix_meta_instagram_appservice_username`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:27 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:20 msgid "both trying to bridge the same DMs" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:29 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:22 msgid "To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@instagrambot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:31 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:24 msgid "Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:33 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:26 msgid "Enable Appservice Double Puppet (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:35 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.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-meta-instagram.md:37 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.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-meta-instagram.md:39 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:32 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:41 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.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-meta-instagram.md:47 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:40 msgid "Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:49 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:42 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:51 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:44 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:53 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:46 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-meta-instagram.md:55 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:48 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:57 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:50 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:64 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:57 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:59 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md: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-meta-instagram.md:66 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:63 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:68 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:65 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:70 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:67 msgid "To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:72 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:69 msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/meta/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:74 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:71 msgid "After logging in, the bridge will sync recent chats." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:76 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:78 -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-meta-instagram`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:80 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:82 -msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po index 97db62abb..0f8262207 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,172 +18,164 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:9 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:1 msgid "Setting up Messenger bridging via Mautrix Meta (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:11 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:13 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:5 msgid "The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:15 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:7 msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/meta/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:17 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:9 msgid "Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:19 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:11 msgid "This documentation page only deals with the bridge's ability to bridge to Facebook Messenger. For bridging to Instagram, see [Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:21 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:13 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:23 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:15 msgid "Migrating from the old mautrix-facebook bridge" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:25 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:17 msgid "If you've been using the [mautrix-facebook](./configuring-playbook-bridge-mautrix-facebook.md) bridge, it's possible to migrate the database using [instructions from the bridge documentation](https://docs.mau.fi/bridges/go/meta/facebook-migration.html) (advanced)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:27 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:19 msgid "Then you may wish to get rid of the Facebook bridge. To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@facebookbot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:29 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:21 msgid "Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:31 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:23 msgid "**Note**: the user ID of the new bridge bot is `@messengerbot:example.com`, not `@facebookbot:example.com`. After disabling the old bridge, its bot user will stop responding to a command." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:33 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:25 msgid "Enable Appservice Double Puppet (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:35 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:27 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:37 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:29 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-meta-messenger.md:39 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:31 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:41 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:33 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:47 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:39 msgid "Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:49 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:41 msgid "Bridge mode" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:51 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:43 msgid "As mentioned above, the [mautrix-meta](https://github.com/mautrix/meta) bridge supports multiple modes of operation." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:53 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:45 msgid "The bridge can pull your Messenger messages via 3 different methods:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:55 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:47 msgid "(`facebook`) Facebook via `facebook.com`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:56 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:48 msgid "(`facebook-tor`) Facebook via `facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion` ([Tor](https://www.torproject.org/)) — does not currently proxy media downloads" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:57 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:49 msgid "(default) (`messenger`) Messenger via `messenger.com` — usable even without a Facebook account" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:59 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:51 msgid "You may switch the mode via the `matrix_mautrix_meta_messenger_meta_mode` variable. The playbook defaults to the `messenger` mode, because it's most universal (every Facebook user has a Messenger account, but the opposite is not true)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:61 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:53 msgid "Note that switching the mode (especially between `facebook*` and `messenger`) will intentionally make the bridge use another database (`matrix_mautrix_meta_facebook` or `matrix_mautrix_meta_messenger`) to isolate the 2 instances. Switching between Tor and non-Tor may be possible without dataloss, but your mileage may vary. Before switching to a new mode, you may wish to de-configure the old one (send `help` to the bridge bot and unbridge your portals, etc.)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:63 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:55 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:65 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:57 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:67 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:59 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-meta-messenger.md:69 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:61 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:71 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:63 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:78 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:70 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:72 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:74 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:80 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:76 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:82 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:78 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:84 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:80 msgid "To use the bridge, you need to start a chat with `@messengerbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). Note that the user ID of the bridge's bot is not `@facebookbot:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:86 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:82 msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/meta/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:88 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:84 msgid "After logging in, the bridge will sync recent chats." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:90 +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:86 msgid "**Note**: given that the bot is configured in `messenger` [bridge mode](#bridge-mode) by default, you will need to log in to [messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain the cookies from there." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:92 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.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-mautrix-meta-messenger`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:96 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:98 -msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po index a40d2bfd4..7a5b2802a 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,120 +18,112 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:17 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:1 msgid "Setting up Mautrix Signal bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:19 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:21 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:5 msgid "The playbook can install and configure [mautrix-signal](https://github.com/mautrix/signal) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:23 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:7 msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/signal/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:25 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:9 msgid "Prerequisites (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:27 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:11 msgid "Prepare Postgres database on external Postgres server" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:29 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:13 msgid "If you're running with the Postgres database server integrated by the playbook (which is the default), you don't need to do anything special and can easily proceed with installing." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:31 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:15 msgid "However, if you're [using an external Postgres server](configuring-playbook-external-postgres.md), you'd need to manually prepare a Postgres database for this bridge and adjust the variables related to that (`matrix_mautrix_signal_database_*`)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:33 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:17 msgid "Enable Appservice Double Puppet" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:35 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:19 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:37 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:21 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-signal.md:39 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:23 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:41 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:25 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:47 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:31 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:49 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:33 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:51 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:35 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-signal.md:53 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:37 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:55 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:39 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:62 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:46 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:48 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:50 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:64 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:52 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:66 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:54 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:68 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:56 msgid "To use the bridge, you need to start a chat with `@signalbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:70 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:58 msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/signal/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:72 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:60 msgid "After logging in, the bridge will bridge chats as you receive messages." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:74 +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:62 msgid "**Note**: Signal does not support any kind of message history (even on official apps), so the bridge won't backfill any messages." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:76 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:78 -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-signal`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:80 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:82 -msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po index 0e6d9c4fb..f18f13ce5 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,86 +18,106 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:10 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:1 msgid "Setting up Mautrix Slack bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:12 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:14 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:5 +msgid "**Note**: bridging to [Slack](https://slack.com/) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:6 +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:7 +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:9 msgid "The playbook can install and configure [mautrix-slack](https://github.com/mautrix/slack) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:16 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:11 msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/slack/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:18 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:13 msgid "See the [features and roadmap](https://github.com/mautrix/slack/blob/main/ROADMAP.md) for more information." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:20 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:15 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:22 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:17 msgid "For using this bridge, you would need to authenticate by **providing your username and password** (legacy) or by using a **token login**. See more information in the [docs](https://docs.mau.fi/bridges/go/slack/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:24 -msgid "Note that neither of these methods are officially supported by Slack." +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:19 +msgid "Note that neither of these methods are officially supported by Slack. [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) uses a Slack bot account which is the only officially supported method for bridging a Slack channel." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:26 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:21 msgid "Enable Appservice Double Puppet (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:28 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:23 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:30 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:25 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:32 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:27 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:34 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:29 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:40 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:35 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:42 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:37 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../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." +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:40 +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-slack.md:46 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:42 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:48 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:44 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:51 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:53 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + #: ../../../docs/configuring-playbook-bridge-mautrix-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: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." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:59 @@ -115,19 +135,3 @@ msgstr "" #: ../../../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:67 -msgid "Troubleshooting" -msgstr "" - -#: ../../../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:71 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../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 "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po index 9ca031ca5..8496f9ebd 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,156 +18,145 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:14 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:1 msgid "Setting up Mautrix Telegram bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:16 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:18 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:5 msgid "The playbook can install and configure [mautrix-telegram](https://github.com/mautrix/telegram) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:20 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:7 msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/telegram/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:22 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:9 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:24 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:11 msgid "Obtain a Telegram API key" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:26 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:13 msgid "To use the bridge, you'd need to obtain an API key from [https://my.telegram.org/apps](https://my.telegram.org/apps)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:28 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:15 msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:30 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:17 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:32 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:19 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-telegram.md:34 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:21 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:81 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:36 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:23 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 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:25 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 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:27 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:42 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:29 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:37 msgid "Relaying" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:52 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:39 msgid "Enable relay-bot (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:54 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:41 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:51 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:53 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 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:55 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 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:57 msgid "Use the bridge for direct chats only (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:72 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:59 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:65 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:80 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:67 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:70 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:72 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:87 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:74 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:83 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:85 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:96 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:87 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:98 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:89 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:100 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:91 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 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:93 msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/telegram/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:104 +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:95 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." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:106 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:108 -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 -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:" -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po index 10b2135b3..929ff2e01 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,104 +18,100 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:10 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:1 msgid "Setting up Mautrix Twitter bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:12 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:14 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:5 +msgid "**Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md) bridge supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:7 msgid "The playbook can install and configure [mautrix-twitter](https://github.com/mautrix/twitter) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:16 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:9 msgid "See the project's [documentation](https://github.com/mautrix/twitter/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:18 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:11 msgid "Prerequisite (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:20 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:13 msgid "Enable Appservice Double Puppet" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:22 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:15 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:24 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:17 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-twitter.md:26 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:19 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:28 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:21 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:27 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:29 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:39 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:32 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-twitter.md:41 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:43 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:50 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:52 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:54 -msgid "Usage" +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:43 +msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:56 -msgid "To use the bridge, you need to start a chat with `@twitterbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:45 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:58 -msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/twitter/authentication.html)." +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:47 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:60 -msgid "After logging in, the bridge will create portal rooms for recent chats. Portal rooms for other chats will be created as you receive messages." +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:49 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:62 -msgid "Troubleshooting" +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:51 +msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:64 -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-twitter`." +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:53 +msgid "To use the bridge, you need to start a chat with `@twitterbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:66 -msgid "Increase logging verbosity" +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:55 +msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/twitter/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:68 -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:" +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:57 +msgid "After logging in, the bridge will create portal rooms for some recent chats. Portal rooms for other chats will be created as you receive messages." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po index 636db861d..b9c026ba4 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,112 +18,104 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:14 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:1 msgid "Setting up Mautrix Whatsapp bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:16 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:18 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:5 msgid "The playbook can install and configure [mautrix-whatsapp](https://github.com/mautrix/whatsapp) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:20 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:7 msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/whatsapp/index.html) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:22 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:9 msgid "Prerequisite (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:24 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:11 msgid "Enable Appservice Double Puppet or Shared Secret Auth" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:26 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:13 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:28 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:15 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-whatsapp.md:30 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:17 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-whatsapp.md:32 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:19 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:34 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:21 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:40 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:27 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:42 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:29 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:44 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:31 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-whatsapp.md:46 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:33 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:48 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:35 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:55 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:42 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:44 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:46 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md: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." +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:48 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:59 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:50 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:61 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:52 msgid "To use the bridge, you need to start a chat with `@whatsappbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:63 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:54 msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/whatsapp/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:65 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:56 msgid "Approximately in a minute after logging in, the bridge will create portal rooms for recent chats." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:67 +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:58 msgid "**Note**: your linked devices will be logged out if you don’t use your phone for over 14 days (see the official FAQ entry [here](https://faq.whatsapp.com/general/download-and-installation/about-linked-devices)). The bridge will warn you if it doesn't receive any data from the phone over 12 days." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:69 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:71 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-whatsapp`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:73 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:75 -msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po index e84cbeb8d..412bef917 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,104 +18,104 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:9 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:1 msgid "Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:11 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:3 msgid "Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:13 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:5 msgid "The playbook can install and configure [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:15 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:7 msgid "See the project's [documentation](https://github.com/mautrix/wsproxy/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:17 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:9 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:19 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:11 msgid "By default, this playbook installs wsproxy on the `wsproxy.` subdomain (`wsproxy.example.com`) and requires you to create a CNAME record for `wsproxy`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:21 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:13 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:23 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:15 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:25 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:17 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:37 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:29 msgid "Note that the tokens must match what is compiled into the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android device." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:39 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:31 msgid "Adjusting the wsproxy URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:41 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:33 msgid "By tweaking the `matrix_mautrix_wsproxy_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:43 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:35 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:50 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:42 msgid "After changing the domain, **you may need to adjust your DNS** records to point the wsproxy domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:52 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:44 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:54 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:46 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:56 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:48 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-wsproxy.md:58 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:50 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:60 +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:52 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:67 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:59 +msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.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." +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:61 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:71 -msgid "Usage" +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:63 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:73 -msgid "Follow the [mautrix-imessage documentation](https://docs.mau.fi/bridges/go/imessage/index.html) for running `android-sms` and/or `matrix-imessage` on your device(s)." +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:65 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:75 -msgid "Troubleshooting" +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:67 +msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:77 -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-wsproxy`." +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:69 +msgid "Follow the [mautrix-imessage documenation](https://docs.mau.fi/bridges/go/imessage/index.html) for running `android-sms` and/or `matrix-imessage` on your device(s)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po index 678b72d4c..fc6d17c55 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po @@ -10,7 +10,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: 2024-12-20 23:17+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,24 +18,84 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:15 -msgid "Setting up MX Puppet Discord bridging (optional, removed)" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:1 +msgid "Setting up MX Puppet Discord bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:17 -msgid "🪦 The playbook used to be able to install and configure [mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord), but no longer includes this component, as it has been unmaintained for a long time." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:3 +msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md)and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:4 +msgid "For using as a Bot we recommend the [Appservice Discord](configuring-playbook-bridge-appservice-discord.md), because it supports plumbing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:5 +msgid "For personal use with a discord account we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:7 +msgid "The playbook can install and configure [mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:9 +msgid "See the project's [documentation](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:13 +msgid "To enable the [Discord](https://discordapp.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:19 -msgid "You may wish to use the [Mautrix Discord bridge](https://github.com/mautrix/discord) instead." +msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:21 -msgid "Uninstalling the bridge manually" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:28 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:30 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:32 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:34 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:36 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:38 +msgid "To use the bridge, you need to start a chat with `Discord Puppet Bridge` with the handle `@_discordpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:40 +msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-discord [documentation](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) for more information about how to configure the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:42 +msgid "Once logged in, send `list` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:44 +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:23 -msgid "If you still have the MX Puppet Discord bridge 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:" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:46 +msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po index fd69424fa..c59253dc7 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po @@ -10,7 +10,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: 2024-12-20 23:17+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,68 +18,76 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:10 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:1 msgid "Setting up MX Puppet GroupMe bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:12 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:3 msgid "The playbook can install and configure [mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:14 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:5 msgid "See the project's [documentation](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:16 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:7 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:18 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:9 msgid "To enable the [GroupMe](https://groupme.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:24 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:15 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:26 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:17 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:33 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:26 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:28 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:35 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:30 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:37 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:32 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:39 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:34 msgid "To use the bridge, you need to start a chat with `GroupMe Puppet Bridge` with the handle `@_groupmepuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:41 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:36 msgid "One authentication method is available." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:43 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:38 msgid "To link your GroupMe account, go to [dev.groupme.com](https://dev.groupme.com/), sign in, and select \"Access Token\" from the top menu. Copy the token and message the bridge with:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:49 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:44 msgid "Once logged in, send `listrooms` to the bot user to list the available rooms." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:51 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:46 msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:53 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:48 msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po index 99e0ce5d8..3b479cfdc 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po @@ -10,7 +10,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: 2024-12-20 23:17+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,24 +18,88 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:14 -msgid "Setting up MX Puppet Instagram bridging (optional, removed)" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:1 +msgid "Setting up MX Puppet Instagram bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:16 -msgid "🪦 The playbook used to be able to install and configure [mx-puppet-instagram](https://gitlab.com/mx-puppet/instagram/mx-puppet-instagram), but no longer includes this component, as it has been unmaintained for a long time." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:3 +msgid "The playbook can install and configure [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:18 -msgid "You may wish to use the [Mautrix Meta](https://github.com/mautrix/meta) Messenger/Instagram bridge instead." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:5 +msgid "This allows you to bridge Instagram DirectMessages into Matrix." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:20 -msgid "Uninstalling the bridge manually" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:7 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:22 -msgid "If you still have the MX Puppet Instagram bridge 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:" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:9 +msgid "To enable the [Instagram](https://www.instagram.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:17 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:26 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:28 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:30 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:34 +msgid "To use the bridge, you need to start a chat with `Instagram Puppet Bridge` with the handle `@_instagrampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:36 +msgid "Send `link ` to the bridge bot to link your instagram account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:38 +msgid "The `list` commands shows which accounts are linked and which `puppetId` is associated." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:40 +msgid "For double-puppeting, you probably want to issue these commands:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:42 +msgid "`settype $puppetId puppet` to enable puppeting for the link (instead of relaying)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:43 +msgid "`setautoinvite $puppetId 1` to automatically invite you to chats" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:44 +msgid "`setmatrixtoken $accessToken` to set the access token to enable puppeting from the other side (the \"double\" in double puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:46 +msgid "If you are linking only one Instagram account, your `$puppetId` is probably 1, but use the `list` command find out." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:48 +msgid "Send `help` to the bot to see the available commands. At the time of writing, not every command is fully implemented." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po index 62c1517c5..7d7cd399b 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,16 +18,16 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:9 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:1 msgid "Setting up MX Puppet Skype bridging (optional, removed)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:11 -msgid "🪦 The playbook used to be able to install and configure [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype), but no longer includes this component, because it has been broken and unmaintained for a long time." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:3 +msgid "The playbook used to be able to install and configure [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype), but no longer includes this component, because it has been broken and unmaintained for a long time." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:13 -msgid "The playbook used to be able to install and configure [go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md) as alternative to this bridge, but no longer includes this component, because Skype has been discontinued since May 2025." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:5 +msgid "Bridging to [Skype](https://www.skype.com/) can also happen via the [go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md) bridge supported by the playbook." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po index e91e79985..9b7f2c028 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po @@ -10,7 +10,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: 2024-12-20 23:17+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,24 +18,84 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:17 -msgid "Setting up MX Puppet Slack bridging (optional, removed)" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:1 +msgid "Setting up MX Puppet Slack bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:19 -msgid "🪦 The playbook used to be able to install and configure [mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack), but no longer includes this component, as it has been unmaintained for a long time." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:3 +msgid "**Note**: bridging to [Slack](https://slack.com) can also happen via the [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook. Note that `matrix-appservice-slack` is not available for new installation unless you have already created a classic Slack application, because the creation of classic Slack applications, which this bridge makes use of, has been discontinued." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:21 -msgid "You may wish to use the [Mautrix Slack bridge](https://github.com/mautrix/slack) instead." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:5 +msgid "The playbook can install and configure [mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:23 -msgid "Uninstalling the bridge manually" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:7 +msgid "See the project's [documentation](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:25 -msgid "If you still have the MX Puppet Slack bridge 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:" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:9 +msgid "Prerequisite" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:11 +msgid "Follow the [OAuth credentials](https://gitlab.com/mx-puppet/slack/mx-puppet-slack#option-2-oauth) instructions to create a new Slack app, setting the redirect URL to `https://matrix.example.com/slack/oauth`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:15 +msgid "To enable the [Slack](https://slack.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:24 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:26 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:33 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:35 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:37 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:39 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:41 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:43 +msgid "To use the bridge, you need to start a chat with `Slack Puppet Bridge` with the handle `@_slackpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:45 +msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-slack [documentation](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for more information about how to configure the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:47 +msgid "Once logged in, send `list` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:49 +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:51 +msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po index cd29adff6..9b162ca65 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po @@ -10,7 +10,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: 2024-12-20 23:17+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,68 +18,72 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:10 -msgid "Setting up MX Puppet Steam bridging (optional, deprecated)" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:1 +msgid "Setting up MX Puppet Steam bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:12 -msgid "**Note**: This bridge has been deprecated in favor of the [matrix-steam-bridge](https://github.com/jasonlaguidice/matrix-steam-bridge) bridge for Steam, which can be [installed using this playbook](configuring-playbook-bridge-steam.md). Consider using that bridge instead of this one." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:3 +msgid "The playbook can install and configure [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:14 -msgid "The playbook can install and configure [mx-puppet-steam](https://codeberg.org/icewind/mx-puppet-steam) for you." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:5 +msgid "See the project's [documentation](https://github.com/icewind1991/mx-puppet-steam/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:16 -msgid "See the project's [documentation](https://codeberg.org/icewind/mx-puppet-steam/blob/master/README.md) to learn what it does and why it might be useful to you." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:18 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:7 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:20 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:9 msgid "To enable the [Steam](https://steampowered.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:26 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:15 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:28 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:17 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:35 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:26 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:28 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:37 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:30 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:39 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:32 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:41 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:34 msgid "To use the bridge, you need to start a chat with `Steam Puppet Bridge` with the handle `@_steampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:43 -msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-steam [documentation](https://codeberg.org/icewind/mx-puppet-steam) for more information about how to configure the bridge." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:36 +msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-steam [documentation](https://github.com/icewind1991/mx-puppet-steam) for more information about how to configure the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:45 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:38 msgid "Once logged in, send `list` to the bot user to list the available rooms." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:47 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:40 msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:49 +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:42 msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po index a127a384e..00f617467 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po @@ -10,7 +10,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: 2024-12-20 23:17+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,24 +18,84 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:1 +msgid "Setting up MX Puppet Twitter bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:3 +msgid "**Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mautrix-twitter](configuring-playbook-bridge-mautrix-twitter.md) bridge supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:5 +msgid "The playbook can install and configure [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:7 +msgid "See the project's [documentation](https://github.com/Sorunome/mx-puppet-twitter/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:9 +msgid "Prerequisite" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:11 +msgid "Make an app on [developer.twitter.com](https://developer.twitter.com/en/apps)." +msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:13 -msgid "Setting up MX Puppet Twitter bridging (optional, removed)" +msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:15 -msgid "🪦 The playbook used to be able to install and configure [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter), but no longer includes this component, as it has been unmaintained for a long time." +msgid "To enable the [Twitter](https://twitter.com) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:26 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:28 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:35 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:37 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:39 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:41 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:43 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:45 +msgid "To use the bridge, you need to start a chat with `Twitter Puppet Bridge` with the handle `@_twitterpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:47 +msgid "To log in, use `link` and click the link." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:17 -msgid "You may wish to use the [Mautrix Twitter bridge](https://github.com/mautrix/twitter) instead." +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:49 +msgid "Once logged in, send `list` to the bot user to list the available rooms." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:19 -msgid "Uninstalling the bridge manually" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:51 +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:21 -msgid "If you still have the MX Puppet Twitter bridge 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:" +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:53 +msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-steam.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-steam.po deleted file mode 100644 index 7dda43620..000000000 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-steam.po +++ /dev/null @@ -1,89 +0,0 @@ -# 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 , 2026. -# -#, fuzzy -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" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: jp\n" -"Language-Team: jp \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-bridge-steam.md:7 -msgid "Setting up Steam bridging (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:9 -msgid "The playbook can install and configure [matrix-steam-bridge](https://github.com/jasonlaguidice/matrix-steam-bridge) for you." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:11 -msgid "See the project's [documentation](https://github.com/jasonlaguidice/matrix-steam-bridge/blob/main/README.md) to learn what it does and why it might be useful to you." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:13 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:15 -msgid "To enable the [Steam](https://steampowered.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:21 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:23 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:30 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` and `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:32 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:34 -msgid "The tag for `just` commands for this bridge is `matrix-steam-bridge` - for example: `just install-service matrix-steam-bridge`" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:36 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:38 -msgid "To use the bridge, you need to start a chat with `Steam bridge bot` with the handle `@steambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:40 -msgid "The bridge supports QR code and password-based login as well as SteamGuard codes via app, SMS, or e-mail. See matrix-steam-bridge [documentation](https://github.com/jasonlaguidice/matrix-steam-bridge) for more information about how to configure the bridge." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:42 -msgid "To login, send `login [flow ID]` where possible flow IDs are `password` or `qr`" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:44 -msgid "Once logged in, send `search [name]` to search through recognized Steam friends. You can send a user name, display name, or all forms of Steam ID. Send `start-chat [identifier]` to request the bridge bot to open a chat room with a user." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:46 -msgid "Chat rooms will automatically be opened as new messages are received." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-steam.md:48 -msgid "Send `help` to the bot to see the available commands." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po index a46fc251b..2e989018f 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,96 +18,60 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-bridge-wechat.md:8 +#: ../../../docs/configuring-playbook-bridge-wechat.md:1 msgid "Setting up WeChat bridging (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:10 +#: ../../../docs/configuring-playbook-bridge-wechat.md:3 msgid "The playbook can install and configure [matrix-wechat](https://github.com/duo/matrix-wechat) for you, for bridging to [WeChat](https://www.wechat.com/)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:12 +#: ../../../docs/configuring-playbook-bridge-wechat.md:5 msgid "See the project's [documentation](https://github.com/duo/matrix-wechat/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:14 -msgid "[!WARNING] This bridge does not work against newer versions of Synapse anymore. See [this issue](https://github.com/duo/matrix-wechat/issues/33). Don't even bother installing it. Unless bridge maintenance is resumed and fixes this issue, we have no choice but to remove it from the playbook." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:17 +#: ../../../docs/configuring-playbook-bridge-wechat.md:7 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:19 +#: ../../../docs/configuring-playbook-bridge-wechat.md:9 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:25 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:27 -msgid "There are some additional things you may wish to configure about the bridge." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:29 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:31 -msgid "`roles/custom/matrix-bridge-wechat/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:32 -msgid "`roles/custom/matrix-bridge-wechat/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_wechat_configuration_extension_yaml` variable" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:34 +#: ../../../docs/configuring-playbook-bridge-wechat.md:15 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:36 +#: ../../../docs/configuring-playbook-bridge-wechat.md:17 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:43 +#: ../../../docs/configuring-playbook-bridge-wechat.md:24 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:45 +#: ../../../docs/configuring-playbook-bridge-wechat.md:26 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:28 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:47 +#: ../../../docs/configuring-playbook-bridge-wechat.md:30 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:49 +#: ../../../docs/configuring-playbook-bridge-wechat.md:32 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:51 +#: ../../../docs/configuring-playbook-bridge-wechat.md:34 msgid "To use the bridge, you need to start a chat with `@wechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-wechat.md:53 +#: ../../../docs/configuring-playbook-bridge-wechat.md:36 msgid "Send `help` to the bot to see the available commands." msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:55 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:57 -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-wechat`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:59 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-wechat.md:61 -msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po index dee254cf2..1cf8f2205 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,180 +18,188 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-cactus-comments.md:10 +#: ../../../docs/configuring-playbook-cactus-comments.md:1 msgid "Setting up Cactus Comments (optional)" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:12 +#: ../../../docs/configuring-playbook-cactus-comments.md:3 msgid "The playbook can install and configure the [Cactus Comments](https://cactus.chat) system for you." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:14 +#: ../../../docs/configuring-playbook-cactus-comments.md:5 msgid "Cactus Comments is a **federated comment system** built on Matrix. It respects your privacy, and puts you in control." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:16 +#: ../../../docs/configuring-playbook-cactus-comments.md:7 msgid "See the project's [documentation](https://cactus.chat/docs/getting-started/introduction/) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:18 +#: ../../../docs/configuring-playbook-cactus-comments.md:9 msgid "The playbook contains 2 roles for configuring different pieces of the Cactus Comments system:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:20 +#: ../../../docs/configuring-playbook-cactus-comments.md:11 msgid "`matrix-cactus-comments` — the backend appservice integrating with the Matrix homeserver" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:22 +#: ../../../docs/configuring-playbook-cactus-comments.md:13 msgid "`matrix-cactus-comments-client` — a static website server serving the [cactus-client](https://cactus.chat/docs/client/introduction/) static assets (`cactus.js` and `styles.css`)" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:24 +#: ../../../docs/configuring-playbook-cactus-comments.md:15 msgid "You can enable whichever component you need (typically both)." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:26 +#: ../../../docs/configuring-playbook-cactus-comments.md:17 msgid "Adjusting DNS records (optional)" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:28 +#: ../../../docs/configuring-playbook-cactus-comments.md:19 msgid "By default, this playbook installs Cactus Comments' client on the `matrix.` subdomain, at the `/cactus-comments` path (https://matrix.example.com/cactus-comments). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:30 +#: ../../../docs/configuring-playbook-cactus-comments.md:21 msgid "If you wish to adjust it, see the section [below](#adjusting-the-cactus-comments-client-url-optional) for details about DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:32 +#: ../../../docs/configuring-playbook-cactus-comments.md:23 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:34 +#: ../../../docs/configuring-playbook-cactus-comments.md:25 msgid "To enable Cactus Comments, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:54 +#: ../../../docs/configuring-playbook-cactus-comments.md:45 msgid "Adjusting the Cactus Comments' client URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:56 +#: ../../../docs/configuring-playbook-cactus-comments.md:47 msgid "By tweaking the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:58 +#: ../../../docs/configuring-playbook-cactus-comments.md:49 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:67 +#: ../../../docs/configuring-playbook-cactus-comments.md:58 msgid "If you've changed the default hostname, you may need to create a CNAME record for the Cactus Comments' client domain (`cactus.example.com`), which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:69 +#: ../../../docs/configuring-playbook-cactus-comments.md:60 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:71 +#: ../../../docs/configuring-playbook-cactus-comments.md:62 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:73 +#: ../../../docs/configuring-playbook-cactus-comments.md:64 msgid "There are some additional things you may wish to configure about the components." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:75 +#: ../../../docs/configuring-playbook-cactus-comments.md:66 msgid "For `matrix-cactus-comments`, take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:77 +#: ../../../docs/configuring-playbook-cactus-comments.md:68 msgid "`roles/custom/matrix-cactus-comments/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:79 +#: ../../../docs/configuring-playbook-cactus-comments.md:70 msgid "For `matrix-cactus-comments-client`, take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:81 +#: ../../../docs/configuring-playbook-cactus-comments.md:72 msgid "`roles/custom/matrix-cactus-comments-client/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:83 +#: ../../../docs/configuring-playbook-cactus-comments.md:74 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:85 +#: ../../../docs/configuring-playbook-cactus-comments.md:76 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:92 +#: ../../../docs/configuring-playbook-cactus-comments.md:83 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:85 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:87 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:94 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-cactus-comments.md:89 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:96 +#: ../../../docs/configuring-playbook-cactus-comments.md:91 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:98 +#: ../../../docs/configuring-playbook-cactus-comments.md:93 msgid "To use the component, you need to start a chat with `@bot.cactusbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:100 +#: ../../../docs/configuring-playbook-cactus-comments.md:95 msgid "Then, register a site by sending `register YOUR_SITE_NAME_HERE` (where `YOUR_SITE_NAME_HERE` is a unique identifier you choose. It does not have to match your domain). You will then be invited into a moderation room." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:102 +#: ../../../docs/configuring-playbook-cactus-comments.md:97 msgid "Now you are good to go and can embed the comment section on your website!" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:104 +#: ../../../docs/configuring-playbook-cactus-comments.md:99 msgid "Embed Cactus Comments" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:106 +#: ../../../docs/configuring-playbook-cactus-comments.md:101 msgid "The official [documentation](https://cactus.chat/docs/getting-started/quick-start/) provides a useful guide to embed Cactus Comments on your website." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:108 +#: ../../../docs/configuring-playbook-cactus-comments.md:103 msgid "After including the JavaScript and CSS asset files, insert a `
` where you'd like to display the comment section:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:114 +#: ../../../docs/configuring-playbook-cactus-comments.md:109 msgid "Then, you need to initialize the comment section. Make sure to replace `example.com` with your base domain and `YOUR_SITE_NAME_HERE` with the one that has been registered above:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:128 +#: ../../../docs/configuring-playbook-cactus-comments.md:123 msgid "Adjust the domain name for self-hosting" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:130 +#: ../../../docs/configuring-playbook-cactus-comments.md:125 msgid "To have the assets served from your homeserver (not from `cactus.chat`), you need to adjust the domain name on the official documentation." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:132 +#: ../../../docs/configuring-playbook-cactus-comments.md:127 msgid "Make sure to replace `example.com` with your base domain before you include the following lines, instead of the one provided by the official documentation:" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:139 +#: ../../../docs/configuring-playbook-cactus-comments.md:134 msgid "**Note**: if the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_path_prefix` variables are tweaked, you would need to adjust the URLs of the assets accordingly." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:141 +#: ../../../docs/configuring-playbook-cactus-comments.md:136 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:143 +#: ../../../docs/configuring-playbook-cactus-comments.md:138 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-cactus-comments` for the backend appservice or `journalctl -fu matrix-cactus-comments-client` for the server serving the client assets, respectively." msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:145 +#: ../../../docs/configuring-playbook-cactus-comments.md:140 msgid "Increase logging verbosity" msgstr "" -#: ../../../docs/configuring-playbook-cactus-comments.md:147 +#: ../../../docs/configuring-playbook-cactus-comments.md:142 msgid "It is possible to increase logging verbosity for `matrix-cactus-comments-client`. The default logging level for this component is `error`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-cinny.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-cinny.po index 75e9c3e10..952d54a06 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-cinny.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-cinny.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,108 +18,80 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-client-cinny.md:9 +#: ../../../docs/configuring-playbook-client-cinny.md:1 msgid "Setting up Cinny (optional)" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:11 +#: ../../../docs/configuring-playbook-client-cinny.md:3 msgid "The playbook can install and configure the [Cinny](https://github.com/ajbura/cinny) Matrix web client for you." msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:13 +#: ../../../docs/configuring-playbook-client-cinny.md:5 msgid "Cinny is a web client focusing primarily on simple, elegant and secure interface. It can be installed alongside or instead of [Element Web](./configuring-playbook-client-element-web.md)." msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:15 +#: ../../../docs/configuring-playbook-client-cinny.md:7 msgid "💡 **Note**: the latest version of Cinny is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting:" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:17 +#: ../../../docs/configuring-playbook-client-cinny.md:9 msgid "[app.cinny.in](https://app.cinny.in), hosted by the [Cinny](https://cinny.in/) developers" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:19 +#: ../../../docs/configuring-playbook-client-cinny.md:11 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:21 +#: ../../../docs/configuring-playbook-client-cinny.md:13 msgid "By default, this playbook installs Cinny on the `cinny.` subdomain (`cinny.example.com`) and requires you to create a CNAME record for `cinny`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:23 +#: ../../../docs/configuring-playbook-client-cinny.md:15 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:25 +#: ../../../docs/configuring-playbook-client-cinny.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:27 +#: ../../../docs/configuring-playbook-client-cinny.md:19 msgid "To enable Cinny, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:33 +#: ../../../docs/configuring-playbook-client-cinny.md:25 msgid "Adjusting the Cinny URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:35 -msgid "By tweaking the `cinny_hostname` variable, you can easily make the service available at a **different hostname** than the default one." +#: ../../../docs/configuring-playbook-client-cinny.md:27 +msgid "By tweaking the `matrix_client_cinny_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:37 +#: ../../../docs/configuring-playbook-client-cinny.md:29 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:47 +#: ../../../docs/configuring-playbook-client-cinny.md:39 msgid "After changing the domain, **you may need to adjust your DNS** records to point the Cinny domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:49 -msgid "**Note**: while there is a `cinny_path_prefix` variable for changing the path where Cinny is served, overriding it is [not possible](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Cinny requires an application rebuild (with a tweaked build config) to be functional under a custom path. You'd need to serve Cinny at a dedicated subdomain." -msgstr "" - -#: ../../../docs/configuring-playbook-client-cinny.md:51 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-client-cinny.md:53 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-client-cinny.md:55 -msgid "Take a look at:" +#: ../../../docs/configuring-playbook-client-cinny.md:41 +msgid "**Note**: while there is a `matrix_client_cinny_path_prefix` variable for changing the path where Cinny is served, overriding it is [not possible](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Cinny requires an application rebuild (with a tweaked build config) to be functional under a custom path. You'd need to serve Cinny at a dedicated subdomain." msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:57 -msgid "`roles/galaxy/cinny/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-client-cinny.md:58 -msgid "`roles/galaxy/cinny/templates/config.json.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `cinny_configuration_extension_json` variable" -msgstr "" - -#: ../../../docs/configuring-playbook-client-cinny.md:60 +#: ../../../docs/configuring-playbook-client-cinny.md:43 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:62 +#: ../../../docs/configuring-playbook-client-cinny.md:45 msgid "After configuring the playbook and [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:69 +#: ../../../docs/configuring-playbook-client-cinny.md:52 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-client-cinny.md:71 +#: ../../../docs/configuring-playbook-client-cinny.md:54 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-client-cinny.md:73 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-client-cinny.md:75 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-client-cinny`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-element-web.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-element-web.po index 6500873bc..cfc6b6d62 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-element-web.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-element-web.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,176 +18,152 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-client-element-web.md:11 +#: ../../../docs/configuring-playbook-client-element-web.md:1 msgid "Configuring Element Web (optional)" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:13 +#: ../../../docs/configuring-playbook-client-element-web.md:3 msgid "By default, this playbook installs the [Element Web](https://github.com/element-hq/element-web) Matrix client for you. If that's okay, you can skip this document." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:15 +#: ../../../docs/configuring-playbook-client-element-web.md:5 msgid "If you'd like to stop the playbook installing the client, see the section [below](#disabling-element-web) to check the configuration for disabling it." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:17 +#: ../../../docs/configuring-playbook-client-element-web.md:7 msgid "💡 **Note**: the latest version of Element Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting (by [disabling Element Web](#disabling-element-web)):" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:19 +#: ../../../docs/configuring-playbook-client-element-web.md:9 msgid "[app.element.io](https://app.element.io/), hosted by [Element](https://element.io/)" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:20 +#: ../../../docs/configuring-playbook-client-element-web.md:10 msgid "[app.etke.cc](https://app.etke.cc/), hosted by [etke.cc](https://etke.cc/)" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:22 +#: ../../../docs/configuring-playbook-client-element-web.md:12 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:24 +#: ../../../docs/configuring-playbook-client-element-web.md:14 msgid "By default, this playbook installs Element Web on the `element.` subdomain (`element.example.com`) and requires you to create a CNAME record for `element`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:26 +#: ../../../docs/configuring-playbook-client-element-web.md:16 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:28 +#: ../../../docs/configuring-playbook-client-element-web.md:18 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:30 -msgid "Set the country code for phone number inputs" -msgstr "" - -#: ../../../docs/configuring-playbook-client-element-web.md:32 -msgid "You can change the country code (default: `GB`) to use when showing phone number inputs. To change it to `FR` for example, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-element-web.md:38 +#: ../../../docs/configuring-playbook-client-element-web.md:20 msgid "Themes" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:40 -msgid "Change the default theme" -msgstr "" - -#: ../../../docs/configuring-playbook-client-element-web.md:42 -msgid "You can change the default theme from `light` to `dark`. To do so, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-client-element-web.md:22 +msgid "You can change the look of Element Web by pulling themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project or defining your own themes manually." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:49 +#: ../../../docs/configuring-playbook-client-element-web.md:24 msgid "Use themes by `element-themes`" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:51 -msgid "You can change the look of Element Web by pulling themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project or defining your own themes manually." -msgstr "" - -#: ../../../docs/configuring-playbook-client-element-web.md:53 -msgid "To pull the themes and use them for your Element Web instance, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-client-element-web.md:26 +msgid "To pull the themes from the `element-themes` project and use them for your Element Web instance, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:59 +#: ../../../docs/configuring-playbook-client-element-web.md:32 msgid "If the variable is set to `true`, all themes found in the repository specified with `matrix_client_element_themes_repository_url` will be installed and enabled automatically." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:61 +#: ../../../docs/configuring-playbook-client-element-web.md:34 msgid "Note that for a custom theme to work well, all Element Web instances that you use must have the same theme installed." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:63 +#: ../../../docs/configuring-playbook-client-element-web.md:36 msgid "Define themes manually" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:65 +#: ../../../docs/configuring-playbook-client-element-web.md:38 msgid "You can also define your own themes manually by adding and adjusting the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:72 +#: ../../../docs/configuring-playbook-client-element-web.md:45 msgid "If you define your own themes with it and set `matrix_client_element_themes_enabled` to `true` for the themes by `element-themes`, your themes will be preserved as well." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:74 +#: ../../../docs/configuring-playbook-client-element-web.md:47 msgid "If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:76 +#: ../../../docs/configuring-playbook-client-element-web.md:49 msgid "Adjusting the Element Web URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:78 +#: ../../../docs/configuring-playbook-client-element-web.md:51 msgid "By tweaking the `matrix_client_element_hostname` and `matrix_client_element_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:80 +#: ../../../docs/configuring-playbook-client-element-web.md:53 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:91 +#: ../../../docs/configuring-playbook-client-element-web.md:64 msgid "After changing the domain, **you may need to adjust your DNS** records to point the Element domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:93 +#: ../../../docs/configuring-playbook-client-element-web.md:66 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:95 +#: ../../../docs/configuring-playbook-client-element-web.md:68 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:97 +#: ../../../docs/configuring-playbook-client-element-web.md:70 msgid "There are some additional things you may wish to configure about the component." msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:99 +#: ../../../docs/configuring-playbook-client-element-web.md:72 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:101 +#: ../../../docs/configuring-playbook-client-element-web.md:74 msgid "`roles/custom/matrix-client-element/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:102 +#: ../../../docs/configuring-playbook-client-element-web.md:75 msgid "`roles/custom/matrix-client-element/templates/config.json.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_client_element_configuration_extension_json` variable" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:104 +#: ../../../docs/configuring-playbook-client-element-web.md:77 msgid "For example, to override some Element Web settings, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:122 +#: ../../../docs/configuring-playbook-client-element-web.md:95 msgid "Disabling Element Web" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:124 +#: ../../../docs/configuring-playbook-client-element-web.md:97 msgid "If you'd like for the playbook to not install Element Web (or to uninstall it if it was previously installed), add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:130 +#: ../../../docs/configuring-playbook-client-element-web.md:103 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:132 +#: ../../../docs/configuring-playbook-client-element-web.md:105 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:139 +#: ../../../docs/configuring-playbook-client-element-web.md:112 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-client-element-web.md:141 +#: ../../../docs/configuring-playbook-client-element-web.md:114 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-client-element-web.md:143 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-client-element-web.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-client-element`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-fluffychat-web.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-fluffychat-web.po deleted file mode 100644 index 08103bca9..000000000 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-fluffychat-web.po +++ /dev/null @@ -1,105 +0,0 @@ -# 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 , 2026. -# -#, fuzzy -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" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: jp\n" -"Language-Team: jp \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-client-fluffychat-web.md:8 -msgid "Setting up FluffyChat Web (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:10 -msgid "The playbook can install and configure the [FluffyChat Web](https://github.com/krille-chan/fluffychat) Matrix client for you." -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:12 -msgid "FluffyChat Web is a cute cross-platform (web, iOS, Android) messenger for Matrix written in [Flutter](https://flutter.dev/)." -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:14 -msgid "💡 **Note**: the latest version of FluffyChat Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Application, you can consider using it from there:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:16 -msgid "[fluffychat.im](https://fluffychat.im/web), hosted by the [FluffyChat](https://fluffy.chat/) developers" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:18 -msgid "Adjusting DNS records" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:20 -msgid "By default, this playbook installs FluffyChat Web on the `fluffychat.` subdomain (`fluffychat.example.com`) and requires you to create a CNAME record for `fluffychat`, which targets `matrix.example.com`." -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:22 -msgid "When setting, replace `example.com` with your own." -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:24 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:26 -msgid "To enable FluffyChat Web, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:32 -msgid "Adjusting the FluffyChat Web URL (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:34 -msgid "By tweaking the `matrix_client_fluffychat_hostname` and `matrix_client_fluffychat_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:36 -msgid "Example additional configuration for your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:47 -msgid "After changing the domain, **you may need to adjust your DNS** records to point the FluffyChat Web domain to the Matrix server." -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:49 -msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:51 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:53 -msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:60 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:62 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:64 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-client-fluffychat-web.md:66 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-client-fluffychat`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po index ef77f7882..58c50b741 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,100 +18,72 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-client-hydrogen.md:10 +#: ../../../docs/configuring-playbook-client-hydrogen.md:1 msgid "Setting up Hydrogen (optional)" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:12 +#: ../../../docs/configuring-playbook-client-hydrogen.md:3 msgid "The playbook can install and configure the [Hydrogen](https://github.com/element-hq/hydrogen-web) Matrix web client for you." msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:14 +#: ../../../docs/configuring-playbook-client-hydrogen.md:5 msgid "Hydrogen is a lightweight web client that supports mobile and legacy web browsers. It can be installed alongside or instead of Element Web." msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:16 +#: ../../../docs/configuring-playbook-client-hydrogen.md:7 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:18 +#: ../../../docs/configuring-playbook-client-hydrogen.md:9 msgid "By default, this playbook installs Hydrogen on the `hydrogen.` subdomain (`hydrogen.example.com`) and requires you to create a CNAME record for `hydrogen`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:20 +#: ../../../docs/configuring-playbook-client-hydrogen.md:11 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:22 +#: ../../../docs/configuring-playbook-client-hydrogen.md:13 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:24 +#: ../../../docs/configuring-playbook-client-hydrogen.md:15 msgid "To enable Hydrogen, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:30 +#: ../../../docs/configuring-playbook-client-hydrogen.md:21 msgid "Adjusting the Hydrogen URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:32 -msgid "By tweaking the `hydrogen_hostname` and `hydrogen_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +#: ../../../docs/configuring-playbook-client-hydrogen.md:23 +msgid "By tweaking the `matrix_client_hydrogen_hostname` and `matrix_client_hydrogen_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:34 +#: ../../../docs/configuring-playbook-client-hydrogen.md:25 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:45 +#: ../../../docs/configuring-playbook-client-hydrogen.md:36 msgid "After changing the domain, **you may need to adjust your DNS** records to point the Hydrogen domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:47 +#: ../../../docs/configuring-playbook-client-hydrogen.md:38 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:49 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-client-hydrogen.md:51 -msgid "There are some additional things you may wish to configure about the client." -msgstr "" - -#: ../../../docs/configuring-playbook-client-hydrogen.md:53 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-hydrogen.md:55 -msgid "`roles/galaxy/hydrogen/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-client-hydrogen.md:56 -msgid "`roles/galaxy/hydrogen/templates/config.json.j2` for the client's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `hydrogen_configuration_extension_json` variable" -msgstr "" - -#: ../../../docs/configuring-playbook-client-hydrogen.md:58 +#: ../../../docs/configuring-playbook-client-hydrogen.md:40 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:60 +#: ../../../docs/configuring-playbook-client-hydrogen.md:42 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:67 +#: ../../../docs/configuring-playbook-client-hydrogen.md:49 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-client-hydrogen.md:69 +#: ../../../docs/configuring-playbook-client-hydrogen.md:51 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-client-hydrogen.md:71 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-client-hydrogen.md:73 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-client-hydrogen`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-sable.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-sable.po deleted file mode 100644 index 767435c9d..000000000 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-sable.po +++ /dev/null @@ -1,117 +0,0 @@ -# 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 , 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 \n" -"Language: jp\n" -"Language-Team: jp \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-client-sable.md:9 -msgid "Setting up Sable (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:11 -msgid "The playbook can install and configure the [Sable](https://github.com/7w1/sable) Matrix web client for you." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:13 -msgid "Sable is a web client focusing primarily on simple, elegant and secure interface. It can be installed alongside or instead of [Element Web](./configuring-playbook-client-element-web.md), [Cinny](./configuring-playbook-client-cinny.md) and others." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:15 -msgid "Adjusting DNS records" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:17 -msgid "By default, this playbook installs Sable on the `sable.` subdomain (`sable.example.com`) and requires you to create a CNAME record for `sable`, which targets `matrix.example.com`." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:19 -msgid "When setting, replace `example.com` with your own." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:21 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:23 -msgid "To enable Sable, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:29 -msgid "Adjusting the Sable URL (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:31 -msgid "By tweaking the `sable_hostname` variable, you can easily make the service available at a **different hostname** than the default one." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:33 -msgid "Example additional configuration for your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:43 -msgid "After changing the domain, **you may need to adjust your DNS** records to point the Sable domain to the Matrix server." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:45 -msgid "**Note**: while there is a `sable_path_prefix` variable for changing the path where Sable is served, overriding it is [not possible](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Sable requires an application rebuild (with a tweaked build config) to be functional under a custom path. You'd need to serve Sable at a dedicated subdomain." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:47 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:49 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:51 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:53 -msgid "`roles/galaxy/sable/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:54 -msgid "`roles/galaxy/sable/templates/config.json.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `sable_configuration_extension_json` variable" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:56 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:58 -msgid "After configuring the playbook and [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:65 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:67 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:69 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:71 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-client-sable`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po index 14b063985..29b81d345 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,168 +18,144 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:9 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:1 msgid "Setting up SchildiChat Web (optional)" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:11 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:3 msgid "The playbook can install and configure the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) Matrix client for you." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:13 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:5 msgid "SchildiChat Web is a feature-rich messenger for Matrix based on Element Web with some extras and tweaks. It can be installed alongside or instead of Element Web." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:15 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:7 msgid "💡 **Note**: the latest version of SchildiChat Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Application, you can consider using it from there:" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:17 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:9 msgid "[app.schildi.chat](https://app.schildi.chat/), hosted by the [SchildiChat](https://schildi.chat/) developers" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:19 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:11 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:21 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:13 msgid "By default, this playbook installs SchildiChat Web on the `schildichat.` subdomain (`schildichat.example.com`) and requires you to create a CNAME record for `schildichat`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:23 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:15 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:25 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:27 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:19 msgid "To enable SchildiChat Web, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:33 -msgid "Set the country code for phone number inputs" -msgstr "" - -#: ../../../docs/configuring-playbook-client-schildichat-web.md:35 -msgid "You can change the country code (default: `GB`) to use when showing phone number inputs. To change it to `FR` for example, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-schildichat-web.md:41 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:25 msgid "Themes" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:43 -msgid "Change the default theme" -msgstr "" - -#: ../../../docs/configuring-playbook-client-schildichat-web.md:45 -msgid "You can change the default theme from `light` to `dark`. To do so, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-client-schildichat-web.md:27 +msgid "You can change the look of SchildiChat Web by pulling themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project or defining your own themes manually." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:52 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:29 msgid "Use themes by `element-themes`" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:54 -msgid "You can change the look of SchildiChat Web by pulling themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project or defining your own themes manually." +#: ../../../docs/configuring-playbook-client-schildichat-web.md:31 +msgid "To pull the themes from the `element-themes` project and use them for your SchildiChat Web instance, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:56 -msgid "To pull the themes and use them for your SchildiChat Web instance, add the following configuration to your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-schildichat-web.md:62 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:37 msgid "If the variable is set to `true`, all themes found in the repository specified with `matrix_client_schildichat_themes_repository_url` will be installed and enabled automatically." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:64 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:39 msgid "Note that for a custom theme to work well, all SchildiChat Web instances that you use must have the same theme installed." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:66 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:41 msgid "Define themes manually" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:68 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:43 msgid "You can also define your own themes manually by adding and adjusting the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:75 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:50 msgid "If you define your own themes with it and set `matrix_client_schildichat_themes_enabled` to `true` for the themes by `element-themes`, your themes will be preserved as well." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:77 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:52 msgid "If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:79 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:54 msgid "Adjusting the SchildiChat Web URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:81 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:56 msgid "By tweaking the `matrix_client_schildichat_hostname` and `matrix_client_schildichat_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:83 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:58 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:94 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:69 msgid "After changing the domain, **you may need to adjust your DNS** records to point the SchildiChat Web domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:96 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:71 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:98 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:73 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:100 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:75 msgid "There are some additional things you may wish to configure about the component." msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:102 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:77 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:104 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:79 msgid "`roles/custom/matrix-client-schildichat/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:105 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:80 msgid "`roles/custom/matrix-client-schildichat/templates/config.json.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_client_schildichat_configuration_extension_json` variable" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:107 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:82 msgid "For example, to override some SchildiChat Web settings, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:125 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:100 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:127 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:102 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:134 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:109 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-client-schildichat-web.md:136 +#: ../../../docs/configuring-playbook-client-schildichat-web.md:111 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-client-schildichat-web.md:138 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-client-schildichat-web.md:140 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-client-schildichat`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduit.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduit.po index a48ae0724..ce1b9fbe1 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduit.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduit.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,120 +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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-conduit.md:8 +#: ../../../docs/configuring-playbook-conduit.md:1 msgid "Configuring Conduit (optional)" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:10 +#: ../../../docs/configuring-playbook-conduit.md:3 msgid "The playbook can install and configure the [Conduit](https://conduit.rs) Matrix server for you." msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:12 +#: ../../../docs/configuring-playbook-conduit.md:5 msgid "See the project's [documentation](https://docs.conduit.rs/) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:14 +#: ../../../docs/configuring-playbook-conduit.md:7 msgid "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." msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:16 -msgid "[!WARNING]" +#: ../../../docs/configuring-playbook-conduit.md:9 +msgid "💡 **Note**: The playbook also supports installing a (currently) faster-moving Conduit fork called [conduwuit](./configuring-playbook-conduwuit.md)." msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:17 +#: ../../../docs/configuring-playbook-conduit.md:11 +msgid "⚠️ **Warnings**:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:13 msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet." msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:18 +#: ../../../docs/configuring-playbook-conduit.md:15 msgid "**Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:20 +#: ../../../docs/configuring-playbook-conduit.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:22 +#: ../../../docs/configuring-playbook-conduit.md:19 msgid "To use Conduit, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below:" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:28 +#: ../../../docs/configuring-playbook-conduit.md:25 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:30 +#: ../../../docs/configuring-playbook-conduit.md:27 msgid "There are some additional things you may wish to configure about the server." msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:32 +#: ../../../docs/configuring-playbook-conduit.md:29 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:34 +#: ../../../docs/configuring-playbook-conduit.md:31 msgid "`roles/custom/matrix-conduit/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:35 +#: ../../../docs/configuring-playbook-conduit.md:32 msgid "`roles/custom/matrix-conduit/templates/conduit.toml.j2` for the server's default configuration" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:37 +#: ../../../docs/configuring-playbook-conduit.md:34 msgid "If you'd like to have your own different configuration, feel free to copy and paste the original files into your inventory (e.g. in `inventory/host_vars/matrix.example.com/`) and then change the specific host's `vars.yml` file like this:" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:43 +#: ../../../docs/configuring-playbook-conduit.md:40 msgid "Creating the first user account" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:45 +#: ../../../docs/configuring-playbook-conduit.md:42 msgid "Since it is difficult to create the first user account on Conduit (see [famedly/conduit#276](https://gitlab.com/famedly/conduit/-/issues/276) and [famedly/conduit#354](https://gitlab.com/famedly/conduit/-/merge_requests/354)) and it does not support [registering users](registering-users.md) (via the command line or via the playbook) like Synapse and Dendrite do, we recommend the following procedure:" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:47 +#: ../../../docs/configuring-playbook-conduit.md:44 msgid "Add `matrix_conduit_allow_registration: true` to your `vars.yml` the first time around, temporarily" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:48 +#: ../../../docs/configuring-playbook-conduit.md:45 msgid "Run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start` — see [Installing](installing.md))" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:49 +#: ../../../docs/configuring-playbook-conduit.md:46 msgid "Create your first user via Element Web or any other client which supports creating users" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:50 +#: ../../../docs/configuring-playbook-conduit.md:47 msgid "Get rid of `matrix_conduit_allow_registration: true` from your `vars.yml`" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:51 +#: ../../../docs/configuring-playbook-conduit.md:48 msgid "Run the playbook again (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-conduit,start` would be enough this time)" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:52 +#: ../../../docs/configuring-playbook-conduit.md:49 msgid "You can now use your server safely. Additional users can be created by messaging the internal Conduit bot" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:54 +#: ../../../docs/configuring-playbook-conduit.md:51 msgid "Configuring bridges / appservices" msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:56 +#: ../../../docs/configuring-playbook-conduit.md:53 msgid "For other homeserver implementations (like Synapse and Dendrite), the playbook automatically registers appservices (for bridges, bots, etc.) with the homeserver." msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:58 +#: ../../../docs/configuring-playbook-conduit.md:55 msgid "For Conduit, you will have to manually register appservices using the the [register-appservice](https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.md) command." msgstr "" -#: ../../../docs/configuring-playbook-conduit.md:60 +#: ../../../docs/configuring-playbook-conduit.md:57 msgid "Find the `registration.yaml` in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`, then pass the content to Conduit:" msgstr "" - -#: ../../../docs/configuring-playbook-conduit.md:83 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-conduit.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-conduit`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduwuit.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduwuit.po index 57b64c8be..bd93d6f8a 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduwuit.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduwuit.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,44 +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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-conduwuit.md:18 -msgid "Configuring conduwuit (optional, removed)" +#: ../../../docs/configuring-playbook-conduwuit.md:1 +msgid "Configuring conduwuit (optional)" msgstr "" -#: ../../../docs/configuring-playbook-conduwuit.md:20 -msgid "🪦 The playbook used to be able to install and configure the [conduwuit](https://conduwuit.puppyirl.gay/) Matrix server, but no longer includes this component, as it's been abandoned and unmaintained." +#: ../../../docs/configuring-playbook-conduwuit.md:3 +msgid "The playbook can install and configure the [conduwuit](https://conduwuit.puppyirl.gay/) Matrix server for you." msgstr "" -#: ../../../docs/configuring-playbook-conduwuit.md:22 -msgid "Uninstalling the service manually" +#: ../../../docs/configuring-playbook-conduwuit.md:5 +msgid "See the project's [documentation](https://conduwuit.puppyirl.gay/) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-conduwuit.md:24 -msgid "If you still have conduwuit installed on your Matrix server, the playbook can no longer help you uninstall it and you will need to do it manually." +#: ../../../docs/configuring-playbook-conduwuit.md:7 +msgid "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." msgstr "" -#: ../../../docs/configuring-playbook-conduwuit.md:26 -msgid "To uninstall the service, run the command below on the server:" +#: ../../../docs/configuring-playbook-conduwuit.md:9 +msgid "💡 **Note**: conduwuit is a fork of [Conduit](./configuring-playbook-conduit.md), which the playbook also supports. See [Differences from upstream Conduit](https://conduwuit.puppyirl.gay/differences.html)." msgstr "" -#: ../../../docs/configuring-playbook-conduwuit.md:32 -msgid "Migrating to Continuwuity" +#: ../../../docs/configuring-playbook-conduwuit.md:11 +msgid "⚠️ **Warnings**:" msgstr "" -#: ../../../docs/configuring-playbook-conduwuit.md:34 -msgid "Since [Continuwuity](configuring-playbook-continuwuity.md) is a drop-in replacement for conduwuit, migration is possible. Please refer to [this section](./configuring-playbook-continuwuity.md#migrating-from-conduwuit) for details." +#: ../../../docs/configuring-playbook-conduwuit.md:13 +msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> conduwuit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet." msgstr "" -#: ../../../docs/configuring-playbook-conduwuit.md:36 -msgid "Removing data manually" +#: ../../../docs/configuring-playbook-conduwuit.md:15 +msgid "**Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding" msgstr "" -#: ../../../docs/configuring-playbook-conduwuit.md:38 -msgid "If you are not going to migrate to [Continuwuity](configuring-playbook-continuwuity.md), you can remove data by running the command on the server:" +#: ../../../docs/configuring-playbook-conduwuit.md:17 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:19 +msgid "To use conduwuit, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:33 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:35 +msgid "There are some additional things you may wish to configure about the server." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:37 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:39 +msgid "`roles/custom/matrix-conduwuit/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:40 +msgid "`roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2` for the server's default configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:42 +msgid "There are various Ansible variables that control settings in the `conduwuit.toml` file." msgstr "" #: ../../../docs/configuring-playbook-conduwuit.md:44 -msgid "[!WARNING] Once you removing the path, there is no going back. Your data on the homeserver (including chat history, rooms, etc.) will be deleted and not be possible to restore them. Please be certain." +msgid "If a specific setting you'd like to change does not have a dedicated Ansible variable, you can either submit a PR to us to add it, or you can [override the setting using an environment variable](https://conduwuit.puppyirl.gay/configuration.html#environment-variables) using `matrix_conduwuit_environment_variables_extension`. For example:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:52 +msgid "Creating the first user account" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:54 +msgid "Unlike other homeserver implementations (like Synapse and Dendrite), conduwuit does not support creating users via the command line or via the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:56 +msgid "If you followed the instructions above (see [Adjusting the playbook configuration](#adjusting-the-playbook-configuration)), you should have registration enabled and protected by a registration token." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:58 +msgid "This should allow you to create the first user account via any client (like [Element Web](./configuring-playbook-client-element-web.md)) which supports creating users." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:60 +msgid "The **first user account that you create will be marked as an admin** and **will be automatically invited to an admin room**." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:63 +msgid "Configuring bridges / appservices" +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:65 +msgid "For other homeserver implementations (like Synapse and Dendrite), the playbook automatically registers appservices (for bridges, bots, etc.) with the homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:67 +msgid "For conduwuit, you will have to manually register appservices using the [`!admin appservices register` command](https://conduwuit.puppyirl.gay/appservices.html#set-up-the-appservice---general-instructions) sent to the server bot account." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:69 +msgid "The server's bot account has a Matrix ID of `@conduit:example.com` (not `@conduwuit:example.com`!) due to conduwuit's historical legacy. Your first user account would already have been invited to an admin room with this bot." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:72 +msgid "Find the appservice file you'd like to register. This can be any `registration.yaml` file found in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`." +msgstr "" + +#: ../../../docs/configuring-playbook-conduwuit.md:74 +msgid "Then, send its content to the existing admin room:" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-continuwuity.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-continuwuity.po deleted file mode 100644 index 5e3f950a9..000000000 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-continuwuity.po +++ /dev/null @@ -1,165 +0,0 @@ -# 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 , 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 \n" -"Language: jp\n" -"Language-Team: jp \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-continuwuity.md:8 -msgid "Configuring Continuwuity (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:10 -msgid "The playbook can install and configure the [Continuwuity](https://continuwuity.org) Matrix server for you." -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:12 -msgid "See the project's [documentation](https://continuwuity.org) to learn what it does and why it might be useful to you." -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:14 -msgid "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." -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:16 -msgid "💡 **Note**: continuwuity is a fork of [conduwuit](./configuring-playbook-conduwuit.md), which the playbook has supported." -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:18 -msgid "[!WARNING]" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:19 -msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Continuwuity). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet." -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:20 -msgid "**Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:22 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:24 -msgid "To use Continuwuity, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:38 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:40 -msgid "There are some additional things you may wish to configure about the server." -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:42 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:44 -msgid "`roles/custom/matrix-continuwuity/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:45 -msgid "`roles/custom/matrix-continuwuity/templates/continuwuity.toml.j2` for the server's default configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:47 -msgid "There are various Ansible variables that control settings in the `continuwuity.toml` file." -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:49 -msgid "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:" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:57 -msgid "Creating the first user account" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:59 -msgid "Unlike other homeserver implementations (like Synapse and Dendrite), continuwuity does not support creating users via the command line or via the playbook." -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:61 -msgid "On first startup, Continuwuity creates a special one-time-use registration token and logs it to the server's console. To access this, you will need to SSH into the server and run the following command:" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:68 -msgid "Find the token, highlight it, and copy it (ctrl+shift+C). This token should allow you to create the first user account via any client (like [Element Web](./configuring-playbook-client-element-web.md)) which supports creating users." -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:70 -msgid "The **first user account that you create will be marked as an admin** and **will be automatically invited to an admin room**." -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:73 -msgid "Configuring bridges / appservices" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:75 -msgid "For other homeserver implementations (like Synapse and Dendrite), the playbook automatically registers appservices (for bridges, bots, etc.) with the homeserver." -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:77 -msgid "For continuwuity, you will have to manually register appservices using the [`!admin appservices register` command](https://continuwuity.org/appservices.html#set-up-the-appservice---general-instructions) sent to the server bot account." -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:79 -msgid "The server's bot account has a Matrix ID of `@conduit:example.com` (not `@continuwuity:example.com`!) due to continuwuity's historical legacy. Your first user account would already have been invited to an admin room with this bot." -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:82 -msgid "Find the appservice file you'd like to register. This can be any `registration.yaml` file found in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`." -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:84 -msgid "Then, send its content to the existing admin room:" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:108 -msgid "Migrating from conduwuit" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:110 -msgid "Since Continuwuity is a drop-in replacement for [conduwuit](configuring-playbook-conduwuit.md), migration is possible." -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:112 -msgid "Make sure that Continuwuity is properly set up on your `vars.yml` as described above" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:114 -msgid "Make sure that Conduwuit references are removed from your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:116 -msgid "Run the installation in a way that installs new services and uninstalls old ones (e.g. `just setup-all`)" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:118 -msgid "Run the playbook with the `continuwuity-migrate-from-conduwuit` tag (e.g. `just run-tags continuwuity-migrate-from-conduwuit`). This migrates data from `/matrix/conduwuit` to `/matrix/continuwuity`" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:120 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-continuwuity.md:122 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-continuwuity`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dendrite.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dendrite.po index a77cb39a1..67a63aae8 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dendrite.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dendrite.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,96 +18,80 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-dendrite.md:9 +#: ../../../docs/configuring-playbook-dendrite.md:1 msgid "Configuring Dendrite (optional)" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:11 +#: ../../../docs/configuring-playbook-dendrite.md:3 msgid "The playbook can install and configure the [Dendrite](https://github.com/element-hq/dendrite) Matrix server for you." msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:13 +#: ../../../docs/configuring-playbook-dendrite.md:5 msgid "See the project's [documentation](https://element-hq.github.io/dendrite/) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:15 +#: ../../../docs/configuring-playbook-dendrite.md:7 msgid "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." msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:17 -msgid "[!WARNING]" +#: ../../../docs/configuring-playbook-dendrite.md:9 +msgid "⚠️ **Warnings**:" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:18 +#: ../../../docs/configuring-playbook-dendrite.md:11 msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Dendrite). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet." msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:19 +#: ../../../docs/configuring-playbook-dendrite.md:13 msgid "**Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:21 +#: ../../../docs/configuring-playbook-dendrite.md:15 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:23 +#: ../../../docs/configuring-playbook-dendrite.md:17 msgid "To use Dendrite, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below:" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:29 +#: ../../../docs/configuring-playbook-dendrite.md:23 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:31 +#: ../../../docs/configuring-playbook-dendrite.md:25 msgid "There are some additional things you may wish to configure about the server." msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:33 +#: ../../../docs/configuring-playbook-dendrite.md:27 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:35 +#: ../../../docs/configuring-playbook-dendrite.md:29 msgid "`roles/custom/matrix-dendrite/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:36 +#: ../../../docs/configuring-playbook-dendrite.md:30 msgid "`roles/custom/matrix-dendrite/templates/dendrite.yaml.j2` for the server's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_dendrite_configuration_extension_yaml` variable" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:38 +#: ../../../docs/configuring-playbook-dendrite.md:32 msgid "For example, to override some Dendrite settings, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:59 +#: ../../../docs/configuring-playbook-dendrite.md:53 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:61 +#: ../../../docs/configuring-playbook-dendrite.md:55 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:68 +#: ../../../docs/configuring-playbook-dendrite.md:62 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-dendrite.md:70 +#: ../../../docs/configuring-playbook-dendrite.md:64 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-dendrite.md:72 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-dendrite.md:74 -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-dendrite`." -msgstr "" - -#: ../../../docs/configuring-playbook-dendrite.md:76 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-dendrite.md:78 -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 "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dimension.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dimension.po index 477825ec0..00d28e025 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dimension.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dimension.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,20 +18,197 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" + +#: ../../../docs/configuring-playbook-dimension.md:1 +msgid "Setting up Dimension integration manager (optional, unmaintained)" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:3 +#: ../../../docs/configuring-playbook-dimension.md:109 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:4 +msgid "Dimension is **[officially unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299)**. We recommend not bothering with installing it." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:5 +msgid "This playbook now supports running Dimension in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:7 +msgid "The playbook can install and configure the [Dimension](https://dimension.t2bot.io) integration manager for you." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:9 +msgid "See the project's [documentation](https://github.com/turt2live/matrix-dimension/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:13 +msgid "Open Matrix Federation port" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:15 +msgid "Enabling the Dimension service will automatically reconfigure your Synapse homeserver to expose the `openid` API endpoints on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. If you enable the component, make sure that the port is accessible." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:17 +msgid "Install Matrix services" +msgstr "" #: ../../../docs/configuring-playbook-dimension.md:19 -msgid "Setting up Dimension integration manager (optional, removed)" +msgid "Dimension can only be installed after Matrix services are installed and running. If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) and come back here later." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:21 -msgid "🪦 The playbook used to be able to install and configure [Dimension](https://dimension.t2bot.io) integration manager, but no longer includes this component, as it has been unmaintained." +msgid "Register a dedicated Matrix user (optional, recommended)" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:23 -msgid "Uninstalling the component manually" +msgid "We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username)." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:25 -msgid "If you still have the Dimension integration manager 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:" +msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:27 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:33 +msgid "Obtain an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:35 +msgid "Dimension requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:37 +msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:40 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:42 +msgid "By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to create a CNAME record for `dimension`, which targets `matrix.example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:44 +msgid "When setting, replace `example.com` with your own." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:46 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:48 +msgid "To enable Dimension, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:56 +msgid "Define admin users" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:58 +msgid "To define admin users who can modify the integrations this Dimension supports, add the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:66 +msgid "The admin interface is accessible within Element Web by accessing it in any room and clicking the cog wheel/settings icon in the top right. Currently, Dimension can be opened in Element Web by the \"Add widgets, bridges, & bots\" link in the room information." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:68 +msgid "Adjusting the Dimension URL (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:70 +msgid "By tweaking the `matrix_dimension_hostname` and `matrix_dimension_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:72 +msgid "Example additional configuration for your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:83 +msgid "After changing the domain, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:85 +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:87 +msgid "**Note**: while there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You'd need to serve Dimension at a dedicated subdomain." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:89 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:91 +msgid "There are some additional things you may wish to configure about the component." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:93 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:95 +msgid "`roles/custom/matrix-dimension/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:96 +msgid "`roles/custom/matrix-dimension/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_dimension_configuration_extension_yaml` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:98 +msgid "You can find all configuration options on [GitHub page of Dimension project](https://github.com/turt2live/matrix-dimension/blob/master/config/default.yaml)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:100 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:102 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:111 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:113 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:115 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:117 +msgid "After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the room info button (`i`) on the top right corner, and then clicking the \"Add widgets, bridges, & bots\" link." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:119 +msgid "Set up a Jitsi widget" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:121 +msgid "By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:123 +msgid "To set up the widget, an admin user needs to configure the domain via the admin UI once Dimension is running. In Element Web, go to *Manage Integrations* → *Settings* → *Widgets* → *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:125 +msgid "There is unfortunately no way to configure the widget via the playbook. See [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po index a0ff656e0..40444b011 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,116 +18,60 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-dynamic-dns.md:22 +#: ../../../docs/configuring-playbook-dynamic-dns.md:1 msgid "Setting up Dynamic DNS (optional)" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:24 +#: ../../../docs/configuring-playbook-dynamic-dns.md:3 msgid "The playbook can configure Dynamic DNS with [ddclient⁠](https://github.com/ddclient/ddclient) for you. It is a Perl client used to update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider." msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:26 +#: ../../../docs/configuring-playbook-dynamic-dns.md:5 msgid "Most cloud providers / ISPs will charge you extra for a static IP address. If you're not hosting a highly reliable homeserver you can workaround this via dynamic DNS." msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:28 -msgid "For details about configuring the [Ansible role for ddclient](https://github.com/mother-of-all-self-hosting/ansible-role-ddclient), you can check them via:" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:29 -msgid "🌐 [the role's documentation](https://github.com/mother-of-all-self-hosting/ansible-role-ddclient/blob/main/docs/configuring-ddclient.md) online" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:30 -msgid "📁 `roles/galaxy/ddclient/docs/configuring-ddclient.md` locally, if you have [fetched the Ansible roles](../installing.md)" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:32 +#: ../../../docs/configuring-playbook-dynamic-dns.md:7 msgid "Prerequisite" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:34 -msgid "You'll need to authenticate with your DNS provider somehow, in most cases this is simply a username and password but can differ from provider to provider. Please consult with your providers documentation and the upstream [ddclient documentation](https://github.com/ddclient/ddclient/blob/main/ddclient.conf.in) to determine what you'll need to provide to authenticate." +#: ../../../docs/configuring-playbook-dynamic-dns.md:9 +msgid "You'll need to get a username and password from your DNS provider. Please consult with the provider about how to retrieve them." msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:36 +#: ../../../docs/configuring-playbook-dynamic-dns.md:11 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:38 +#: ../../../docs/configuring-playbook-dynamic-dns.md:13 msgid "To enable dynamic DNS, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:51 -msgid "Keep in mind that certain providers may require a different configuration of the `ddclient_domain_configurations` variable, for provider specific examples see the [upstream documentation](https://github.com/ddclient/ddclient/blob/main/ddclient.conf.in)." -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:53 -msgid "Configuring the endpoint to obtain IP address (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:55 -msgid "The playbook sets the default endpoint for obtaining the IP address to `https://cloudflare.com/cdn-cgi/trace`. You can replace it by specifying yours to `ddclient_web` and `ddclient_web_skip` if necessary." -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:57 -msgid "Refer to [this section](https://github.com/mother-of-all-self-hosting/ansible-role-ddclient/blob/main/docs/configuring-ddclient.md#setting-the-endpoint-to-obtain-ip-address-optional) for more information." -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:59 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:61 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:63 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:65 -msgid "`roles/galaxy/ddclient/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:67 +#: ../../../docs/configuring-playbook-dynamic-dns.md:26 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:69 +#: ../../../docs/configuring-playbook-dynamic-dns.md:28 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:76 +#: ../../../docs/configuring-playbook-dynamic-dns.md:35 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:78 +#: ../../../docs/configuring-playbook-dynamic-dns.md:37 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:80 +#: ../../../docs/configuring-playbook-dynamic-dns.md:39 msgid "Additional Reading" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:82 +#: ../../../docs/configuring-playbook-dynamic-dns.md:41 msgid "Additional resources:" msgstr "" -#: ../../../docs/configuring-playbook-dynamic-dns.md:84 +#: ../../../docs/configuring-playbook-dynamic-dns.md:43 msgid "https://matrix.org/docs/guides/free-small-matrix-server" msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:85 -msgid "https://github.com/linuxserver/docker-ddclient" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:87 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-dynamic-dns.md:89 -msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-ddclient/blob/main/docs/configuring-ddclient.md#troubleshooting) on the role's documentation for details." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-element-call.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-element-call.po deleted file mode 100644 index 9b55f25d8..000000000 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-element-call.po +++ /dev/null @@ -1,249 +0,0 @@ -# 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 , 2026. -# -#, fuzzy -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" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: jp\n" -"Language-Team: jp \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-call.md:8 -msgid "Setting up Element Call (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:10 -msgid "The playbook can install and configure [Element Call](https://github.com/element-hq/element-call) and its supporting components that are part of the [Matrix RTC stack](configuring-playbook-matrix-rtc.md)." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:12 -msgid "Element Call is a native Matrix video conferencing application developed by [Element](https://element.io), designed for secure, scalable, privacy-respecting, and decentralized video and voice calls over the Matrix protocol. Built on MatrixRTC ([MSC4143](https://github.com/matrix-org/matrix-spec-proposals/pull/4143)), it utilizes [MSC4195](https://github.com/hughns/matrix-spec-proposals/blob/hughns/matrixrtc-livekit/proposals/4195-matrixrtc-livekit.md) with [LiveKit Server](configuring-playbook-livekit-server.md) as its backend." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:14 -msgid "See the project's [documentation](https://github.com/element-hq/element-call) to learn more." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:16 -msgid "Prerequisites" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:18 -msgid "A [Synapse](configuring-playbook-synapse.md) homeserver (see the warning below)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:19 -msgid "The [Matrix RTC (Real-Time Communication) stack](configuring-playbook-matrix-rtc.md) (automatically done when Element Call is enabled)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:20 -msgid "A client compatible with Element Call. As of 2025-03-15, that's just [Element Web](configuring-playbook-client-element-web.md) and the Element X mobile clients (iOS and Android)." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:21 -msgid "(Optional) Guest accounts being enabled for your Matrix server, if you'd like guests to be able to use Element Call. See [Allowing guests to use Element Call](#allowing-guests-to-use-element-call-optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:23 -msgid "[!WARNING] Because Element Call [requires](https://github.com/element-hq/element-call/blob/93ae2aed9841e0b066d515c56bd4c122d2b591b2/docs/self-hosting.md#a-matrix-homeserver) a few experimental features in the Matrix protocol, it's **very likely that it only works with the Synapse homeserver**." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:26 -msgid "Decide between Element Call vs just the Matrix RTC stack" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:28 -msgid "All clients that can currently use Element Call (Element Web and Element X on mobile) already embed the Element Call frontend within them. These **clients will use their own embedded Element Call frontend**, so **self-hosting the Element Call frontend by the playbook is largely unnecessary**." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:31 -msgid "💡 A reason you may wish to continue installing the Element Call frontend (despite Matrix clients not making use of it), is if you need to use it standalone - directly via a browser (without a Matrix client). Note that unless you [allow guest accounts to use Element Call](#allowing-guests-to-use-element-call-optional), you will still need a Matrix user account **on the same homeserver** to be able to use Element Call." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:33 -msgid "The playbook makes a distinction between enabling Element Call (`matrix_element_call_enabled`) and enabling the Matrix RTC Stack (`matrix_rtc_enabled`). Enabling Element Call automatically enables the Matrix RTC stack. Because installing the Element Call frontend is now unnecessary, **we recommend only installing the Matrix RTC stack, without the Element Call frontend**." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "Description / Variable" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "Element Call frontend" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "[LiveKit Server](configuring-playbook-livekit-server.md)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "[LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "Description" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "Static website that provides the Element Call UI (but often embedded by clients)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "Scalable, multi-user conferencing solution based on WebRTC" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "A helper component that allows Element Call to integrate with LiveKit Server" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "Required for Element Call to function" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "No" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "Yes" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "`matrix_element_call_enabled`" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "✅ Installed" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "`matrix_rtc_enabled`" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md -msgid "❌ Not Installed, but usually unnecessary" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:42 -msgid "All documentation below assumes that you've decided to install Element Call and not just the Matrix RTC stack." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:44 -msgid "Decide on a domain and path" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:46 -msgid "By default, the Element Call frontend is configured to be served on the `call.element.example.com` domain." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:48 -msgid "If you'd like to run Element Call on another hostname, see the [Adjusting the Element Call URL](#adjusting-the-element-call-url-optional) section below." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:50 -msgid "Adjusting DNS records" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:52 -msgid "By default, this playbook installs Element Call on the `call.element.` subdomain (`call.element.example.com`) and requires you to create a `CNAME` record for `call.element`, which targets `matrix.example.com`." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:54 -msgid "When setting these values, replace `example.com` with your own." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:56 -msgid "All dependency services for Element Call ([LiveKit Server](configuring-playbook-livekit-server.md) and [Livekit JWT Service](configuring-playbook-livekit-jwt-service.md)) are installed and configured automatically by the playbook. By default, these services are installed on subpaths on the `matrix.` domain (e.g. `/livekit-server`, `/livekit-jwt-service`), so no DNS record adjustments are required for them." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:58 -msgid "Adjusting firewall rules" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:60 -msgid "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." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:62 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:64 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:72 -msgid "Adjusting the Element Call URL (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:74 -msgid "By tweaking the `matrix_element_call_hostname` variable, you can easily make the service available at a **different hostname** than the default one." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:76 -msgid "Example additional configuration for your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:82 -msgid "[!WARNING] A `matrix_element_call_path_prefix` variable is also available and mean to let you configure a path prefix for the Element Call service, but [Element Call does not support running under a sub-path yet](https://github.com/element-hq/element-call/issues/3084)." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:85 -msgid "Allowing guests to use Element Call (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:87 -msgid "By default, Element Call can only be used by people having accounts on your Matrix server." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:89 -msgid "If you'd like guests to be able to use Element Call as well, you need to enable guest accounts support for your homeserver." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:91 -msgid "[!WARNING] Enabling guest accounts means that your homeserver's user database may get polluted with guest account signups (potentially made by bots). Guest accounts should be limited in what (damage) they can do to your server and the rest of the Matrix ecosystem, but it's better to not enable them unless necessary." -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:95 -msgid "For [Synapse](configuring-playbook-synapse.md) (the default homeserver implementation), the configuration is like this:" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:101 -msgid "For [Dendrite](configuring-playbook-dendrite.md), the configuration is like this:" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:107 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:109 -msgid "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:" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:116 -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-call.md:118 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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-element-call.md:120 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-element-call.md:122 -msgid "Once installed, Element Call integrates seamlessly with Matrix clients like [Element Web](configuring-playbook-client-element-web.md) and Element X on mobile (iOS and Android)." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email.po index 4c3ae6b5e..dbeb7698b 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,136 +18,76 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-email.md:10 +#: ../../../docs/configuring-playbook-email.md:1 msgid "Adjusting email-sending settings (optional)" msgstr "" -#: ../../../docs/configuring-playbook-email.md:12 -msgid "By default, this playbook sets up an [Exim](https://www.exim.org/) relay SMTP mailer service (powered by [exim-relay](https://github.com/devture/exim-relay) and the [ansible-role-exim-relay](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay) Ansible role), through which all Matrix services send emails." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:14 -msgid "**With the default setting, exim-relay attempts to deliver emails directly with the address `matrix@matrix.example.com`**, as specified by the `exim_relay_sender_address` playbook variable. See below if you want to configure the playbook to relay email through another SMTP server." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:16 -msgid "The [Ansible role for exim-relay](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring exim-relay, you can check them via:" +#: ../../../docs/configuring-playbook-email.md:3 +msgid "By default, this playbook sets up an [Exim](https://www.exim.org/) email server through which all Matrix services send emails." msgstr "" -#: ../../../docs/configuring-playbook-email.md:17 -msgid "🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md) online" +#: ../../../docs/configuring-playbook-email.md:5 +msgid "The email server would attempt to deliver emails directly to their final destination. This may or may not work, depending on your domain configuration (SPF settings, etc.)" msgstr "" -#: ../../../docs/configuring-playbook-email.md:18 -msgid "📁 `roles/galaxy/exim_relay/docs/configuring-exim-relay.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" +#: ../../../docs/configuring-playbook-email.md:7 +msgid "By default, emails are sent from `matrix@matrix.example.com`, as specified by the `exim_relay_sender_address` playbook variable." msgstr "" -#: ../../../docs/configuring-playbook-email.md:20 -msgid "Why use exim-relay?" +#: ../../../docs/configuring-playbook-email.md:9 +msgid "[!WARNING] On some cloud providers (Google Cloud, etc.), [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible. You will need to [relay email through another SMTP server](#relaying-email-through-another-smtp-server)." msgstr "" -#: ../../../docs/configuring-playbook-email.md:22 -msgid "**Benefits of using exim-relay** instead of configuring SMTP directly in each service:" +#: ../../../docs/configuring-playbook-email.md:12 +msgid "💡 To improve deliverability, we recommend [relaying email through another SMTP server](#relaying-email-through-another-smtp-server) anyway." msgstr "" -#: ../../../docs/configuring-playbook-email.md:24 -msgid "**Final delivery capability**: Can deliver emails directly if you don't have an SMTP server" +#: ../../../docs/configuring-playbook-email.md:14 +msgid "Firewall settings" msgstr "" -#: ../../../docs/configuring-playbook-email.md:26 -msgid "**Centralized configuration**: Configure your upstream SMTP server once in exim-relay, then point all services ([Synapse](configuring-playbook-synapse.md), [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), etc.) there—no need to configure SMTP in each component" +#: ../../../docs/configuring-playbook-email.md:16 +msgid "No matter whether you send email directly (the default) or you relay email through another host (see how below), you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration)." msgstr "" -#: ../../../docs/configuring-playbook-email.md:28 -msgid "**Local spooling**: Stores messages locally and retries delivery if your upstream SMTP server is temporarily unavailable" +#: ../../../docs/configuring-playbook-email.md:18 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-email.md:30 -msgid "Firewall settings" +#: ../../../docs/configuring-playbook-email.md:20 +msgid "Relaying email through another SMTP server" msgstr "" -#: ../../../docs/configuring-playbook-email.md:32 -msgid "No matter whether you send email directly (the default) or you relay email through another host, you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration)." +#: ../../../docs/configuring-playbook-email.md:22 +msgid "If you'd like to relay email through another SMTP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-email.md:34 -msgid "Docker automatically opens these ports in the server's firewall, so you likely don't need to do anything. If you use another firewall in front of the server, you may need to adjust it." +msgid "**Note**: only the secure submission protocol (using `STARTTLS`, usually on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port `465`) **is not supported**." msgstr "" #: ../../../docs/configuring-playbook-email.md:36 -msgid "Adjusting the playbook configuration" +msgid "Sending emails using Sendgrid" msgstr "" #: ../../../docs/configuring-playbook-email.md:38 -msgid "Enable DKIM authentication to improve deliverability (optional)" +msgid "An easy and free SMTP service to set up is [Sendgrid](https://sendgrid.com/). Its free tier allows for up to 100 emails per day to be sent." msgstr "" #: ../../../docs/configuring-playbook-email.md:40 -msgid "By default, exim-relay attempts to deliver emails directly. This may or may not work, depending on your domain configuration." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:42 -msgid "To improve email deliverability, you can configure authentication methods such as DKIM (DomainKeys Identified Mail), SPF, and DMARC for your domain. Without setting any of these authentication methods, your outgoing email is most likely to be quarantined as spam at recipient's mail servers." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:44 -msgid "For details about configuring DKIM, refer [this section](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md#enable-dkim-support-optional) on the role's documentation." +msgid "To set it up, add the following configuration to your `vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-email.md:46 -msgid "💡 If you cannot enable DKIM, SPF, or DMARC on your domain for some reason, we recommend relaying email through another SMTP server." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:48 -msgid "Relaying email through another SMTP server (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:50 -msgid "**On some cloud providers such as Google Cloud, [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible.** In this case, you will need to relay email through another SMTP server." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:52 -msgid "For details about configuration, refer [this section](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md#relaying-email-through-another-smtp-server) on the role's document." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:54 -msgid "Disable mail service (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:56 -msgid "For a low-power server you might probably want to disable exim-relay. To do so, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:62 -msgid "Note that disabling exim-relay will stop email-notifications and other similar functions from working." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:64 -msgid "See [this entry on the FAQ](faq.md#how-do-i-optimize-this-setup-for-a-low-power-server) for other possible optimizations for a low-power server." -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:66 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:68 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:75 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:77 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-email.md:57 +msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-email.md:79 -msgid "Troubleshooting" +#: ../../../docs/configuring-playbook-email.md:59 +msgid "If you're having trouble with email not being delivered, it may be useful to inspect the mailer logs." msgstr "" -#: ../../../docs/configuring-playbook-email.md:81 -msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md#troubleshooting) on the role's documentation for details." +#: ../../../docs/configuring-playbook-email.md:61 +msgid "To do so, log in to the server with SSH and run `journalctl -f -u matrix-exim-relay`." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po index b832496ca..b5a041a9c 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,24 +18,260 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" + +#: ../../../docs/configuring-playbook-email2matrix.md:1 +msgid "Setting up Email2Matrix (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:3 +msgid "**Note**: this component has been deprecated. We recommend not bothering with installing it. While not a 1:1 replacement, 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). Consider using that component instead of this one." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:5 +msgid "The playbook can install and configure [Email2Matrix](https://github.com/devture/email2matrix) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:7 +msgid "See the project's [documentation](https://github.com/devture/email2matrix/blob/master/docs/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:9 +msgid "Preparation" +msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:11 -msgid "Setting up Email2Matrix (optional, removed)" +msgid "Port availability" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:13 -msgid "🪦 The playbook used to be able to install and configure [Email2Matrix](https://github.com/devture/email2matrix), but no longer includes this component." +msgid "Ensure that port 25 is available on your Matrix server and open in your firewall." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:15 -msgid "For a long time now, it been replaced by the much better and more maintained [Postmoogle](https://github.com/etkecc/postmoogle) bridge, which can also be [installed using this playbook](configuring-playbook-bridge-postmoogle.md)." +msgid "If you have `postfix` or some other email server software installed, you may need to manually remove it first (unless you need it, of course)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:17 +msgid "If you really need to run an email server on the Matrix machine for other purposes, it may be possible to run Email2Matrix on another port (with a configuration like `matrix_email2matrix_smtp_host_bind_port: \"127.0.0.01:2525\"`) and have your other email server relay messages there." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:19 +msgid "For details about using Email2Matrix alongside [Postfix](http://www.postfix.org/), see [here](https://github.com/devture/email2matrix/blob/master/docs/setup_with_postfix.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:21 +msgid "Register a dedicated Matrix user (optional, recommended)" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:23 +msgid "We recommend that you create a dedicated Matrix user for Email2Matrix." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:25 +msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:27 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:33 +msgid "Take note of the user's ID as it needs to be specified as `MatrixUserId` on your `inventory/host_vars/matrix.example.com/vars.yml` file later." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:35 +msgid "Obtain an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:37 +msgid "Email2Matrix requires an access token for the sender user to be able to send messages to the room. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:39 +msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:42 +msgid "Join to rooms as the sender user manually" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:44 +msgid "ℹ️ **Email2Matrix does not accept room invitations automatically**. To deliver messages to rooms, the sender user must be joined to all rooms manually." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:46 +msgid "For each new room you would like the user to deliver messages to, invite the user to the room." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:48 +msgid "Then, log in as the sender user using any Matrix client of your choosing, accept the room invitation from the user's account." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:50 +msgid "Make sure that you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there, then log out." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:52 +msgid "Take note of each room's room ID (different clients show the room ID in a different place). You'll need the room ID when [configuring the playbook](#adjusting-the-playbook-configuration) below." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:54 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:56 +msgid "To increase the chances that incoming emails reach your server, you can set up a `MX` record for `matrix.example.com` that looks like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "Type" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "Host" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "Priority" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "Weight" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "Port" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "Target" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "MX" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "`matrix`" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "10" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "0" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "-" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md +msgid "`matrix.example.com`" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:62 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:64 +msgid "To enable Email2Matrix, add the following configuration to your `vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE` and `ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE` with the ones created [above](#obtain-an-access-token)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:90 +msgid "where:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:92 +msgid "MailboxName — local-part of the email address, through which emails are bridged to the room whose ID is defined with MatrixRoomId" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:93 +msgid "MatrixRoomId — internal ID of the room, to which received emails are sent as Matrix message" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:94 +msgid "MatrixHomeserverUrl — URL of your Matrix homeserver, through which to send Matrix messages. You can also set `MatrixHomeserverUrl` to the container URL where your homeserver's Client-Server API lives by using the `{{ matrix_addons_homeserver_client_api_url }}` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:95 +msgid "MatrixUserId — the full ID of the sender user which sends bridged messages to the room. On this configuration it is `@email2matrix1:example.com` and `@email2matrix2:example.com` (where `example.com` is your base domain, not the `matrix.` domain)" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:96 +msgid "MatrixAccessToken — sender user's access token" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:97 +msgid "IgnoreSubject — if set to \"true\", the subject is not bridged to Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:98 +msgid "IgnoreBody — if set to \"true\", the message body is not bridged to Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:99 +msgid "SkipMarkdown — if set to \"true\", emails are bridged as plain text Matrix message instead of Markdown (actually HTML)" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:101 +msgid "Refer to the official documentation [here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:103 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:105 +msgid "There are some additional things you may wish to configure about the component." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:107 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:109 +msgid "`roles/custom/matrix-email2matrix/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:111 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:113 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:120 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:122 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service email2matrix` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:124 +msgid "`just install-service email2matrix` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:126 +msgid "After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:128 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:130 +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-email2matrix`." msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:18 -msgid "Uninstalling Email2Matrix manually" +#: ../../../docs/configuring-playbook-email2matrix.md:132 +msgid "Increase logging verbosity" msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:20 -msgid "If you still have the Email2Matrix component installed on your Matrix server, the playbook can no longer help you uninstall it and you will need to do it manually. To uninstall manually, run these commands on the server:" +#: ../../../docs/configuring-playbook-email2matrix.md:134 +msgid "If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-etherpad.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-etherpad.po index ff4d2df1d..8610d48fe 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-etherpad.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-etherpad.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,148 +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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-etherpad.md:13 +#: ../../../docs/configuring-playbook-etherpad.md:1 msgid "Setting up Etherpad (optional)" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:15 +#: ../../../docs/configuring-playbook-etherpad.md:3 msgid "The playbook can install and configure [Etherpad](https://etherpad.org) for you." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:17 +#: ../../../docs/configuring-playbook-etherpad.md:5 msgid "Etherpad is an open source collaborative text editor. It can not only be integrated with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS) as a widget, but also be used as standalone web app." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:19 -msgid "When enabled together with the Jitsi video-conferencing platform (see [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made available as an option during the conferences." +#: ../../../docs/configuring-playbook-etherpad.md:7 +msgid "When enabled together with the Jitsi audio/video conferencing system (see [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made available as an option during the conferences." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:21 -msgid "The [Ansible role for Etherpad](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring Etherpad, you can check them via:" +#: ../../../docs/configuring-playbook-etherpad.md:9 +msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:23 -msgid "🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md) online" +#: ../../../docs/configuring-playbook-etherpad.md:11 +msgid "By default, this playbook installs Etherpad on the `etherpad.` subdomain (`etherpad.example.com`) and requires you to create a CNAME record for `etherpad`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:24 -msgid "📁 `roles/galaxy/etherpad/docs/configuring-etherpad.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" +#: ../../../docs/configuring-playbook-etherpad.md:13 +msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:26 -msgid "Adjusting DNS records" +#: ../../../docs/configuring-playbook-etherpad.md:15 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:28 -msgid "By default, this playbook installs Etherpad on the `etherpad.` subdomain (`etherpad.example.com`) and requires you to create a CNAME record for `etherpad`, which targets `matrix.example.com`." +#: ../../../docs/configuring-playbook-etherpad.md:17 +msgid "To enable Etherpad, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:30 -msgid "When setting, replace `example.com` with your own." +#: ../../../docs/configuring-playbook-etherpad.md:27 +msgid "Adjusting the Etherpad URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:32 -msgid "Adjusting the playbook configuration" +#: ../../../docs/configuring-playbook-etherpad.md:29 +msgid "By tweaking the `etherpad_hostname` and `etherpad_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:34 -msgid "To enable Etherpad, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +#: ../../../docs/configuring-playbook-etherpad.md:31 +msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:52 -msgid "As the most of the necessary settings for the role have been taken care of by the playbook, you can enable Etherpad on your Matrix server with this minimum configuration." +#: ../../../docs/configuring-playbook-etherpad.md:42 +msgid "After changing the domain, **you may need to adjust your DNS** records to point the Etherpad domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:54 -msgid "See the role's documentation for details about configuring Etherpad per your preference (such as [the name of the instance](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md#set-the-name-of-the-instance-optional) and [the default pad text](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md#set-the-default-text-optional))." +#: ../../../docs/configuring-playbook-etherpad.md:44 +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:56 -msgid "Create admin user (optional)" +#: ../../../docs/configuring-playbook-etherpad.md:46 +msgid "Configure the default text (optional)" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:58 -msgid "You probably might want to enable authentication to disallow anonymous access to your Etherpad." +#: ../../../docs/configuring-playbook-etherpad.md:48 +msgid "You can also edit the default text on a new pad with the variable `etherpad_default_pad_text`." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:60 -msgid "It is possible to enable HTTP basic authentication by **creating an admin user** with `etherpad_admin_username` and `etherpad_admin_password` variables. The admin user account is also used by plugins for authentication and authorization." +#: ../../../docs/configuring-playbook-etherpad.md:50 +msgid "To do so, add the following configuration to your `vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:62 -msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md#create-admin-user-optional) on the role's documentation for details about how to create the admin user." +msgid "Extending the configuration" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:64 -msgid "Adjusting the Etherpad URL (optional)" +msgid "There are some additional things you may wish to configure about the component." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:66 -msgid "By tweaking the `etherpad_hostname` and `etherpad_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgid "Take a look at:" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:68 -msgid "Example additional configuration for your `vars.yml` file:" +msgid "[etherpad role](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/defaults/main.yml) for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `etherpad_configuration_extension_json` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:70 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:72 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:79 -msgid "After changing the domain, **you may need to adjust your DNS** records to point the Etherpad domain to the Matrix server." +msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:81 -msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the Etherpad admin user (`etherpad_admin_username`)." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:83 -msgid "Installing" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:85 -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:" +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:92 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-etherpad.md:94 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-etherpad.md:87 +msgid "If you change the Etherpad admin user's password (`etherpad_admin_password` in your `vars.yml` file) subsequently, the admin user's credentials on the homeserver won't be updated automatically. If you'd like to change the admin user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `etherpad_admin_password` to let the admin user know its new password." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:96 +#: ../../../docs/configuring-playbook-etherpad.md:89 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:98 -msgid "By default, the Etherpad UI should be available at `https://etherpad.example.com`, while the admin UI (if enabled) should then be available at `https://etherpad.example.com/admin`." +#: ../../../docs/configuring-playbook-etherpad.md:91 +msgid "The Etherpad UI should be available at `https://etherpad.example.com`, while the admin UI (if enabled) should then be available at `https://etherpad.example.com/admin`." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:100 +#: ../../../docs/configuring-playbook-etherpad.md:93 msgid "If you've [decided on another hostname or path-prefix](#adjusting-the-etherpad-url-optional) (e.g. `https://matrix.example.com/etherpad`), adjust these URLs accordingly before using it." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:102 -msgid "💡 For more information about usage, take a look at [this section](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md#usage) on the role's documentation." +#: ../../../docs/configuring-playbook-etherpad.md:95 +msgid "Managing / Deleting old pads" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:104 -msgid "Integrating a Etherpad widget in a room" +#: ../../../docs/configuring-playbook-etherpad.md:97 +msgid "If you want to manage and remove old unused pads from Etherpad, you will first need to create the Etherpad admin user as described above." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:106 -msgid "**Note**: this is how it works in Element Web. It might work quite similar with other clients:" +#: ../../../docs/configuring-playbook-etherpad.md:99 +msgid "After logging in to the admin web UI, go to the plugin manager page, and install the `adminpads2` plugin." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:108 -msgid "To integrate a standalone Etherpad in a room, create your pad by visiting `https://etherpad.example.com`. When the pad opens, copy the URL and send a command like this to the room: `/addwidget URL`. You will then find your integrated Etherpad within the right sidebar in the `Widgets` section." +#: ../../../docs/configuring-playbook-etherpad.md:101 +msgid "Once the plugin is installed, you should have a \"Manage pads\" section in the UI." msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:110 -msgid "Troubleshooting" +#: ../../../docs/configuring-playbook-etherpad.md:103 +msgid "Integrating a Etherpad widget in a room" msgstr "" -#: ../../../docs/configuring-playbook-etherpad.md:112 -msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md#troubleshooting) on the role's documentation for details." +#: ../../../docs/configuring-playbook-etherpad.md:105 +msgid "**Note**: this is how it works in Element Web. It might work quite similar with other clients:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:107 +msgid "To integrate a standalone Etherpad in a room, create your pad by visiting `https://etherpad.example.com`. When the pad opens, copy the URL and send a command like this to the room: `/addwidget URL`. You will then find your integrated Etherpad within the right sidebar in the `Widgets` section." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-federation.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-federation.po index 1d0e7e56e..994cfd58c 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-federation.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-federation.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,72 +18,72 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-federation.md:9 +#: ../../../docs/configuring-playbook-federation.md:1 msgid "Controlling Matrix federation (optional)" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:11 +#: ../../../docs/configuring-playbook-federation.md:3 msgid "By default, your server federates with the whole Matrix network. That is, people on your server can communicate with people on any other Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-federation.md:13 -msgid "**Note**: in the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com` and set up [server delegation](howto-server-delegation.md) / redirection. Without a proper configuration, your server will effectively not be part of the Matrix network. If you find your server is not federated, make sure to [check whether services work](maintenance-and-troubleshooting.md#how-to-check-if-services-work) and your server is properly delegated." +#: ../../../docs/configuring-playbook-federation.md:5 +msgid "**Note**: in the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com` and set up [server delegation](howto-server-delegation.md) / redirection. Without a proper configuration, your server will effectively not be part of the Matrix network. If you find your server is not federated, make sure to [check whether services work](maintenance-checking-services.md) and your server is properly delegated." msgstr "" -#: ../../../docs/configuring-playbook-federation.md:15 +#: ../../../docs/configuring-playbook-federation.md:7 msgid "Federating only with select servers" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:17 +#: ../../../docs/configuring-playbook-federation.md:9 msgid "To make your server only federate with servers of your choosing, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:25 +#: ../../../docs/configuring-playbook-federation.md:17 msgid "If you wish to disable federation, you can do that with an empty list (`[]`), or better yet by completely disabling federation (see below)." msgstr "" -#: ../../../docs/configuring-playbook-federation.md:27 +#: ../../../docs/configuring-playbook-federation.md:19 msgid "Exposing the room directory over federation" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:29 +#: ../../../docs/configuring-playbook-federation.md:21 msgid "By default, your server's public rooms directory is not exposed to other servers via federation." msgstr "" -#: ../../../docs/configuring-playbook-federation.md:31 +#: ../../../docs/configuring-playbook-federation.md:23 msgid "To expose it, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:37 +#: ../../../docs/configuring-playbook-federation.md:29 msgid "Disabling federation" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:39 +#: ../../../docs/configuring-playbook-federation.md:31 msgid "To completely disable federation, isolating your server from the rest of the Matrix network, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:45 +#: ../../../docs/configuring-playbook-federation.md:37 msgid "With that, your server's users will only be able to talk among themselves, but not to anyone who is on another server." msgstr "" -#: ../../../docs/configuring-playbook-federation.md:47 -msgid "**Disabling federation does not necessarily disable the federation port** (`8448`). Even if you disable federation and only if necessary, we may still be exposing the federation port and serving the `openid` APIs there. To override this and completely disable Synapse's federation port use:" +#: ../../../docs/configuring-playbook-federation.md:39 +msgid "**Disabling federation does not necessarily disable the federation port** (`8448`). Services like [Dimension](configuring-playbook-dimension.md) and [ma1sd](configuring-playbook-ma1sd.md) normally rely on `openid` APIs exposed on that port. Even if you disable federation and only if necessary, we may still be exposing the federation port and serving the `openid` APIs there. To override this and completely disable Synapse's federation port use:" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:59 +#: ../../../docs/configuring-playbook-federation.md:51 msgid "Changing the federation port from 8448 to a different port to use a CDN that only accepts 443/80 ports" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:61 +#: ../../../docs/configuring-playbook-federation.md:53 msgid "Why? This change could be useful for people running small Synapse instances on small severs/VPSes to avoid being impacted by a simple DOS/DDOS when bandwidth, RAM, an CPU resources are limited and if your hosting provider does not provide a DOS/DDOS protection." msgstr "" -#: ../../../docs/configuring-playbook-federation.md:63 +#: ../../../docs/configuring-playbook-federation.md:55 msgid "To make it possible to proxy the federation through a CDN such as CloudFlare or any other, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-federation.md:74 +#: ../../../docs/configuring-playbook-federation.md:66 msgid "**Use this at you own risk as all the possible side-effects of doing this are not fully known. However, it has been tested and works fine and passes all the tests on without issues.**" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jitsi.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jitsi.po index 7e645a97f..fc1cf86e6 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jitsi.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jitsi.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,164 +18,488 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-jitsi.md:17 +#: ../../../docs/configuring-playbook-jitsi.md:1 msgid "Setting up the Jitsi video-conferencing platform (optional)" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:19 +#: ../../../docs/configuring-playbook-jitsi.md:3 msgid "The playbook can install and configure the [Jitsi](https://jitsi.org/) video-conferencing platform for you." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:21 -msgid "Because Jitsi still requires a TURN server, enabling Jitsi automatically enables coturn (`coturn_enabled: true`) unless you explicitly disable it." +#: ../../../docs/configuring-playbook-jitsi.md:5 +msgid "Jitsi can not only be integrated with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS) as a widget, but also be used as standalone web app." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:24 -msgid "Jitsi is an open source video-conferencing platform. It can not only be integrated with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS) as a widget, but also be used as standalone web app." +#: ../../../docs/configuring-playbook-jitsi.md:7 +msgid "See the project's [documentation](https://jitsi.github.io/handbook/) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:26 -msgid "💡 If you're into experimental technology, you may also be interested in trying out [Element Call](configuring-playbook-element-call.md) - a native Matrix video conferencing application." +#: ../../../docs/configuring-playbook-jitsi.md:9 +msgid "**Note**: the configuration by the playbook is similar to the one by [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the official documentation for Docker deployment [here](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:13 +msgid "You may need to open the following ports to your server:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:15 +msgid "`4443/tcp` — RTP media fallback over TCP" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:16 +msgid "`10000/udp` — RTP media over UDP. Depending on your firewall/NAT configuration, incoming RTP packets on port `10000` may have the external IP of your firewall as destination address, due to the usage of STUN in JVB (see [`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/defaults/main.yml))." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:18 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:20 +msgid "By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to create a CNAME record for `jitsi`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:28 -msgid "The [Ansible role for Jitsi](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring Jitsi, you can check them via:" +#: ../../../docs/configuring-playbook-jitsi.md:22 +msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:29 -msgid "🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md) online" +#: ../../../docs/configuring-playbook-jitsi.md:24 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:30 -msgid "📁 `roles/galaxy/jitsi/docs/configuring-jitsi.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" +#: ../../../docs/configuring-playbook-jitsi.md:26 +msgid "To enable Jitsi, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:32 -msgid "Prerequisites" +msgid "Adjusting the Jitsi URL (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:34 -msgid "Before proceeding, make sure to check server's requirements recommended by [the official deployment guide](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-requirements)." +msgid "By tweaking the `jitsi_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:36 -msgid "You may need to open some ports to your server, if you use another firewall in front of the server. Refer [the role's documentation](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#prerequisites) to check which ones to be configured." +msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:38 -msgid "Adjusting DNS records" +#: ../../../docs/configuring-playbook-jitsi.md:43 +msgid "After changing the domain, **you may need to adjust your DNS** records to point the Jitsi domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:40 -msgid "By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to create a CNAME record for `jitsi`, which targets `matrix.example.com`." +#: ../../../docs/configuring-playbook-jitsi.md:45 +msgid "Configure Jitsi authentication and guests mode (optional)" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:42 -msgid "When setting, replace `example.com` with your own." +#: ../../../docs/configuring-playbook-jitsi.md:47 +msgid "By default the Jitsi instance does not require for anyone to log in, and is open to use without an account. To control who is allowed to start meetings on your Jitsi instance, you'd need to enable Jitsi's authentication and optionally guests mode." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:44 -msgid "Adjusting the playbook configuration" +#: ../../../docs/configuring-playbook-jitsi.md:49 +msgid "Authentication type must be one of them: `internal` (default), `jwt`, `matrix` or `ldap`. Currently, only `internal`, `matrix` and `ldap` mechanisms are supported by the [Jitsi role](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi)." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:46 -msgid "To enable Jitsi, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +#: ../../../docs/configuring-playbook-jitsi.md:51 +msgid "With authentication enabled, all meetings have to be started by a registered user. After the meeting is started by that user, then guests are free to join. If the registered user is not yet present, the guests are put on hold in individual waiting rooms." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:64 -msgid "As the most of the necessary settings for the role have been taken care of by the playbook, you can enable Jitsi on your Matrix server with this minimum configuration." +#: ../../../docs/configuring-playbook-jitsi.md:53 +msgid "**Note**: authentication is not tested by the playbook's self-checks. We therefore recommend that you would make sure by yourself that authentication is configured properly. To test it, start a meeting at `jitsi.example.com` on your browser." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:66 -msgid "However, **since Jitsi's performance heavily depends on server resource (bandwidth, RAM, and CPU), it is recommended to review settings and optimize them as necessary before deployment.** You can check [here](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#example-configurations) for an example set of configurations to set up a Jitsi instance, focusing on performance. If you will host a large conference, you probably might also want to consider to provision additional JVBs ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)). See [here](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#set-up-additional-jvbs-for-more-video-conferences-optional) for details about setting them up with the playbook." +#: ../../../docs/configuring-playbook-jitsi.md:55 +msgid "Authenticate using Jitsi accounts: Auth-Type `internal` (recommended)" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:68 -msgid "See the role's documentation for details about configuring Jitsi per your preference (such as setting [a custom hostname](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#set-the-hostname) and [the environment variable for running Jitsi in a LAN](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#configure-jvb_advertise_ips-for-running-behind-nat-or-on-a-lan-environment-optional))." +#: ../../../docs/configuring-playbook-jitsi.md:57 +msgid "The default authentication mechanism is `internal` auth, which requires a Jitsi account to have been configured. This is a recommended method, as it also works in federated rooms." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:70 -msgid "Enable authentication and guests mode (optional)" +#: ../../../docs/configuring-playbook-jitsi.md:59 +msgid "To enable authentication with a Jitsi account, add the following configuration to your `vars.yml` file. Make sure to replace `USERNAME_…` and `PASSWORD_…` with your own values." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:72 -msgid "By default the Jitsi Meet instance **does not require for anyone to log in, and is open to use without an account**." +#: ../../../docs/configuring-playbook-jitsi.md:71 +msgid "**Note**: as Jitsi account removal function is not integrated into the playbook, these accounts will not be able to be removed from the Prosody server automatically, even if they are removed from your `vars.yml` file subsequently." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:74 -msgid "If you would like to control who is allowed to start meetings on your instance, you'd need to enable Jitsi's authentication and optionally guests mode." +#: ../../../docs/configuring-playbook-jitsi.md:73 +msgid "Authenticate using Matrix OpenID: Auth-Type `matrix`" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:76 -msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#configure-jitsi-authentication-and-guests-mode-optional) on the role's documentation for details about how to configure the authentication and guests mode. The recommended authentication method is `internal` as it also works in federated rooms. If you want to enable authentication with Matrix OpenID making use of [Matrix User Verification Service (UVS)](configuring-playbook-user-verification-service.md), see [here](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix) for details about how to set it up." +#: ../../../docs/configuring-playbook-jitsi.md:75 +msgid "[!WARNING] This breaks the Jitsi instance on federated rooms probably and does not allow sharing conference links with guests." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:78 -msgid "Enable Gravatar (optional)" +msgid "This authentication method requires [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service), which can be installed using this [playbook](configuring-playbook-user-verification-service.md). It verifies against Matrix openID, and requires a user-verification-service to run." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:80 +msgid "To enable authentication with Matrix OpenID, add the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:88 +msgid "For more information see also [https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification](https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:90 +msgid "Authenticate using LDAP: Auth-Type `ldap`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:92 +msgid "To enable authentication with LDAP, add the following configuration to your `vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:112 +msgid "For more information refer to the [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:114 +msgid "Configure `JVB_ADVERTISE_IPS` for running behind NAT or on a LAN environment (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:116 +msgid "When running Jitsi in a LAN environment, or on the public Internet via NAT, the `JVB_ADVERTISE_IPS` enviornment variable should be set." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:118 +msgid "This variable allows to control which IP addresses the JVB will advertise for WebRTC media traffic. It is necessary to set it regardless of the use of a reverse proxy, since it's the IP address that will receive the media (audio / video) and not HTTP traffic, hence it's oblivious to the reverse proxy." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:120 +msgid "If your users are coming in over the Internet (and not over LAN), this will likely be your public IP address. If this is not set up correctly, calls will crash when more than two users join a meeting." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:122 +msgid "To set the variable, add the following configuration to your `vars.yml` file. Make sure to replace `LOCAL_IP_ADDRESS_OF_THE_HOST_HERE` with a proper value." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:129 +msgid "Check [the official documentation](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/#running-behind-nat-or-on-a-lan-environment) for more details about it." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:131 +msgid "Set a maximum number of participants on a Jitsi conference (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:133 +msgid "You can set a maximum number of participants allowed to join a Jitsi conference. By default the number is not specified." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:135 +msgid "To set it, add the following configuration to your `vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:141 +msgid "Enable Gravatar (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:143 msgid "In the default Jisti Meet configuration, `gravatar.com` is enabled as an avatar service." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:82 -msgid "Since the Element clients send the URL of configured Matrix avatars to the Jitsi instance, our configuration has disabled the Gravatar service." +#: ../../../docs/configuring-playbook-jitsi.md:145 +msgid "Since the Element clients send the URL of configured Matrix avatars to the Jitsi instance, our default configuration has disabled the Gravatar service." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:84 -msgid "To enable the Gravatar service nevertheless, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-jitsi.md:147 +msgid "To enable the Gravatar service, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:90 +#: ../../../docs/configuring-playbook-jitsi.md:153 msgid "[!WARNING] This will result in third party request leaking data to the Gravatar Service (`gravatar.com`, unless configured otherwise). Besides metadata, the Matrix user_id and possibly the room ID (via `referrer` header) will be also sent to the third party." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:93 +#: ../../../docs/configuring-playbook-jitsi.md:156 +msgid "Fine tune Jitsi (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:158 +msgid "If you'd like to have Jitsi save up resources, add the following configuration to your `vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:171 +msgid "These configurations:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:173 +msgid "**limit the maximum video resolution**, to save up resources on both server and clients" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:174 +msgid "**suspend unused video layers** until they are requested again, to save up resources on both server and clients. Read more on this feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-feature/)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:175 +msgid "**disable audio levels** to avoid excessive refresh of the client-side page and decrease the CPU consumption involved" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:176 +msgid "**limit the number of video feeds forwarded to each client**, to save up resources on both server and clients. As clients’ bandwidth and CPU may not bear the load, use this setting to avoid lag and crashes. This feature is available by default on other webconference applications such as Office 365 Teams (the number is limited to 4). Read how it works [here](https://github.com/jitsi/jitsi-videobridge/blob/5ff195985edf46c9399dcf263cb07167f0a2c724/doc/allocation.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:178 +msgid "Example configurations" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:180 +msgid "Here is an example set of configurations for running a Jitsi instance with:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:182 +msgid "authentication using a Jitsi account (username: `US3RNAME`, password: `passw0rd`)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:183 +msgid "guests: allowed" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:184 +msgid "maximum participants: 6 people" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:185 +msgid "fine tuning with the configurations presented above" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:186 +msgid "other miscellaneous options (see the official Jitsi documentation [here](https://jitsi.github.io/handbook/docs/dev-guide/dev-guide-configuration) and [here](https://jitsi.github.io/handbook/docs/user-guide/user-guide-advanced))" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:206 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:95 +#: ../../../docs/configuring-playbook-jitsi.md:208 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:102 +#: ../../../docs/configuring-playbook-jitsi.md:215 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:104 +#: ../../../docs/configuring-playbook-jitsi.md:217 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:106 +#: ../../../docs/configuring-playbook-jitsi.md:219 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:108 +#: ../../../docs/configuring-playbook-jitsi.md:221 msgid "You can use the self-hosted Jitsi server in multiple ways:" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:110 +#: ../../../docs/configuring-playbook-jitsi.md:223 msgid "**by adding a widget to a room via Element Web** (the one configured by the playbook at `https://element.example.com`). Just start a voice or a video call in a room containing more than 2 members and that would create a Jitsi widget which utilizes your self-hosted Jitsi server." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:112 -msgid "**directly (without any Matrix integration)**. Just go to `https://jitsi.example.com`, and you can start a videoconference." +#: ../../../docs/configuring-playbook-jitsi.md:225 +msgid "**directly (without any Matrix integration)**. Just go to `https://jitsi.example.com`" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:114 -msgid "Note that you'll need to log in to your Jitsi's account to start a conference if you have configured authentication with `internal` auth." +#: ../../../docs/configuring-playbook-jitsi.md:227 +msgid "Set up additional JVBs for more video-conferences (optional)" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:116 -msgid "Check [the official user guide](https://jitsi.github.io/handbook/docs/category/user-guide) for details about how to use Jitsi." +#: ../../../docs/configuring-playbook-jitsi.md:229 +msgid "By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)) is deployed on the same host as the Matrix server. To allow more video-conferences to happen at the same time, you'd need to provision additional JVB services on other hosts." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:118 +#: ../../../docs/configuring-playbook-jitsi.md:231 +msgid "These settings below will allow you to provision those extra JVB instances. The instances will register themselves with the Prosody service, and be available for Jicofo to route conferences too." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:233 +msgid "Add the `jitsi_jvb_servers` section on `hosts` file" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:235 +msgid "For additional JVBs, you'd need to add the section titled `jitsi_jvb_servers` on the ansible `hosts` file with the details of the JVB hosts as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:242 +msgid "Make sure to replace `jvb-2.example.com` with your hostname for the JVB and `192.168.0.2` with your JVB's external IP address, respectively." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:244 +msgid "You could add JVB hosts as many as you would like. When doing so, add lines with the details of them." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:246 +msgid "Prepare `vars.yml` files for additional JVBs" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:248 +msgid "If the main server is `matrix.example.com` and the additional JVB instance is going to be deployed at `jvb-2.example.com`, the variables for the latter need to be specified on `vars.yml` in its directory (`inventory/host_vars/jvb-2.example.com`)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:250 +msgid "Note that most (if not all) variables are common for both servers." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:252 +msgid "If you are setting up multiple JVB instances, you'd need to create `vars.yml` files for each of them too (`inventory/host_vars/jvb-3.example.com/vars.yml`, for example)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:254 +msgid "Set the server ID to each JVB" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:256 +msgid "Each JVB requires a server ID to be set, so that it will be uniquely identified. The server ID allows Jitsi to keep track of which conferences are on which JVB." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:258 +msgid "The server ID can be set with the variable `jitsi_jvb_server_id`. It will end up as the `JVB_WS_SERVER_ID` environment variables in the JVB docker container." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:260 +msgid "To set the server ID to `jvb-2`, add the following configuration to either `hosts` or `vars.yml` files (adapt to your needs)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:262 +msgid "On `hosts`:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:264 +msgid "Add `jitsi_jvb_server_id=jvb-2` after your JVB's external IP addresses as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:272 +msgid "On `vars.yml` files:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:278 +msgid "Alternatively, you can specify the variable as a parameter to [the ansible command](#run-the-playbook)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:280 +msgid "**Note**: the server ID `jvb-1` is reserved for the JVB instance running on the Matrix host, therefore should not be used as the ID of an additional JVB host." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:282 +msgid "Set colibri WebSocket port" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:284 +msgid "The additional JVBs will need to expose the colibri WebSocket port." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:286 +msgid "To expose the port, add the following configuration to your `vars.yml` files:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:292 +msgid "Set Prosody XMPP server" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:294 +msgid "The JVB will also need to know the location of the Prosody XMPP server." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:296 +msgid "Similar to the server ID (`jitsi_jvb_server_id`), this can be set with the variable for the JVB by using the variable `jitsi_xmpp_server`." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:298 +msgid "Set the Matrix domain" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:300 +msgid "The Jitsi Prosody container is deployed on the Matrix server by default, so the value can be set to the Matrix domain. To set the value, add the following configuration to your `vars.yml` files:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:306 +msgid "Set an IP address of the Matrix server" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:308 +msgid "Alternatively, the IP address of the Matrix server can be set. This can be useful if you would like to use a private IP address." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:310 +msgid "To set the IP address of the Matrix server, add the following configuration to your `vars.yml` files:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:316 +msgid "Expose XMPP port" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:318 +msgid "By default, the Matrix server does not expose the XMPP port (`5222`); only the XMPP container exposes it internally inside the host. This means that the first JVB (which runs on the Matrix server) can reach it but the additional JVBs cannot. Therefore, the XMPP server needs to expose the port, so that the additional JVBs can connect to it." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:320 +msgid "To expose the port and have Docker forward the port, add the following configuration to your `vars.yml` files:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:326 +msgid "Reverse-proxy with Traefik" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:328 +msgid "To make Traefik reverse-proxy to these additional JVBs, add the following configuration to your main `vars.yml` file (`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:364 +msgid "Run the playbook" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:366 +msgid "After configuring `hosts` and `vars.yml` files, run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:372 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:120 -msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#troubleshooting) on the role's documentation for details." +#: ../../../docs/configuring-playbook-jitsi.md:374 +msgid "`Error: Account creation/modification not supported`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:376 +msgid "If you get an error like `Error: Account creation/modification not supported` with authentication enabled, it's likely that you had previously installed Jitsi without auth/guest support." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:378 +msgid "In this case, you should consider to rebuild your Jitsi installation." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:380 +msgid "Rebuilding your Jitsi installation" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:382 +msgid "If you ever run into any trouble or if you have changed configuration (`jitsi_*` variables) too much, you can rebuild your Jitsi installation." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:384 +msgid "We normally don't recommend manual intervention, but Jitsi services tend to generate a lot of configuration files, and it is often wise to start afresh setting the services up, rather than messing with the existing configuration files. Since not all of those files are managed by Ansible (at least not yet), you may sometimes need to delete them by yourself manually." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:386 +msgid "To rebuild your Jitsi configuration, follow the procedure below:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:388 +msgid "run this command locally to stop all Jitsi services: `just run-tags stop-group --extra-vars=group=jitsi`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:389 +msgid "log in the server with SSH" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:390 +msgid "run this command remotely to remove all Jitsi configuration & data: `rm -rf /matrix/jitsi`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:391 +msgid "run this command locally to set up Jitsi anew and restart services: `just install-service jitsi`" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jwt-service.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jwt-service.po deleted file mode 100644 index 4c71fa34f..000000000 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jwt-service.po +++ /dev/null @@ -1,97 +0,0 @@ -# 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 , 2026. -# -#, fuzzy -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" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: jp\n" -"Language-Team: jp \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-jwt-service.md:8 -msgid "Setting up JWT Service (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:10 -msgid "The playbook can install and configure [LiveKit JWT Service](https://github.com/element-hq/lk-jwt-service) for you." -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:12 -msgid "LK-JWT-Service is currently used for a single reason: generate JWT tokens with a given identity for a given room, so that users can use them to authenticate against LiveKit SFU." -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:14 -msgid "See the project's [documentation](https://github.com/element-hq/lk-jwt-service/) to learn more." -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:16 -msgid "Decide on a domain and path" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:18 -msgid "By default, JWT Service is configured to be served:" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:20 -msgid "on the Matrix domain (`matrix.example.com`), configurable via `matrix_livekit_jwt_service_hostname`" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:21 -msgid "under a `/livekit-jwt-service` path prefix, configurable via `matrix_livekit_jwt_service_path_prefix`" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:23 -msgid "This makes it easy to set it up, **without** having to adjust your DNS records manually." -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:25 -msgid "Adjusting DNS records" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:27 -msgid "If you've changed the default hostname, **you may need to adjust your DNS** records accordingly to point to the correct server." -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:29 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:31 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:37 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:39 -msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:41 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:43 -msgid "Once installed, a new `org.matrix.msc4143.rtc_foci` section is added to the Element Web client to point to your JWT service URL (e.g., `https://matrix.example.com/livekit-jwt-service`)." -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:45 -msgid "Additional Information" -msgstr "" - -#: ../../../docs/configuring-playbook-jwt-service.md:47 -msgid "Refer to the LiveKit JWT-Service documentation for more details on configuring and using JWT Service." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po index fb2b2c0a7..2d335b2bf 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,60 +18,48 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-ldap-auth.md:10 +#: ../../../docs/configuring-playbook-ldap-auth.md:1 msgid "Setting up the LDAP authentication password provider module (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:12 +#: ../../../docs/configuring-playbook-ldap-auth.md:3 msgid "The playbook can install and configure the [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) LDAP Auth password provider for you." msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:14 +#: ../../../docs/configuring-playbook-ldap-auth.md:5 msgid "See the project's [documentation](https://github.com/matrix-org/matrix-synapse-ldap3/blob/main/README.rst) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:16 -msgid "Adjusting the playbook configuration" +#: ../../../docs/configuring-playbook-ldap-auth.md:7 +msgid "If you decide that you'd like to let this playbook install it for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:18 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" -msgstr "" - -#: ../../../docs/configuring-playbook-ldap-auth.md:35 +#: ../../../docs/configuring-playbook-ldap-auth.md:24 msgid "Authenticating only using a password provider" msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:37 -msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, you can disable it by adding the following configuration to your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-ldap-auth.md:43 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-ldap-auth.md:45 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +#: ../../../docs/configuring-playbook-ldap-auth.md:26 +msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:" msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:52 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +#: ../../../docs/configuring-playbook-ldap-auth.md:32 +msgid "Using ma1sd Identity Server for authentication (not recommended)" msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:54 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-ldap-auth.md:34 +msgid "The playbook can instead configure [ma1sd](https://github.com/ma1uta/ma1sd) Identity Server for LDAP authentication. However, **we recommend not bothering with installing it** as ma1sd has been unmaintained for years." msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:56 -msgid "Usage" +#: ../../../docs/configuring-playbook-ldap-auth.md:36 +msgid "If you wish to install it anyway, consult the [ma1sd Identity Server configuration](configuring-playbook-ma1sd.md#authentication)." msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:58 +#: ../../../docs/configuring-playbook-ldap-auth.md:38 msgid "Handling user registration" msgstr "" -#: ../../../docs/configuring-playbook-ldap-auth.md:60 +#: ../../../docs/configuring-playbook-ldap-auth.md:40 msgid "If you wish for users to also be able to make new registrations against LDAP, you may **also** wish to [set up the ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-livekit-jwt-service.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-livekit-jwt-service.po deleted file mode 100644 index a6d77b832..000000000 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-livekit-jwt-service.po +++ /dev/null @@ -1,49 +0,0 @@ -# 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 , 2026. -# -#, fuzzy -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" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: jp\n" -"Language-Team: jp \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-livekit-jwt-service.md:7 -msgid "Setting up LiveKit JWT Service (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-jwt-service.md:9 -msgid "The playbook can install and configure [LiveKit JWT Service](https://github.com/element-hq/lk-jwt-service/) for you." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-jwt-service.md:11 -msgid "This is a helper component which is part of the [Matrix RTC stack](configuring-playbook-matrix-rtc.md) that allows [Element Call](configuring-playbook-element-call.md) to integrate with [LiveKit Server](configuring-playbook-livekit-server.md)." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-jwt-service.md:13 -msgid "💡 LiveKit JWT Service is automatically installed and configured when either [Element Call](configuring-playbook-element-call.md) or the [Matrix RTC stack](configuring-playbook-matrix-rtc.md) is enabled, so you don't need to do anything extra." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-jwt-service.md:15 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-jwt-service.md:17 -msgid "`roles/custom/matrix-livekit-jwt-service/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-jwt-service.md:18 -msgid "`roles/custom/matrix-livekit-jwt-service/templates/env.j2` for the component's default configuration." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-livekit-server.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-livekit-server.po deleted file mode 100644 index 92dcb5ad2..000000000 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-livekit-server.po +++ /dev/null @@ -1,141 +0,0 @@ -# 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 , 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 \n" -"Language: jp\n" -"Language-Team: jp \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-livekit-server.md:8 -msgid "Setting up LiveKit Server (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:10 -msgid "The playbook can install and configure [LiveKit Server](https://github.com/livekit/livekit) for you." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:12 -msgid "LiveKit Server is an open source project that provides scalable, multi-user conferencing based on WebRTC. It's designed to provide everything you need to build real-time video audio data capabilities in your applications." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:14 -msgid "💡 LiveKit Server is automatically installed and configured when either [Element Call](configuring-playbook-element-call.md) or the [Matrix RTC stack](configuring-playbook-matrix-rtc.md) is enabled, so you don't need to do anything extra." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:16 -msgid "The [Ansible role for LiveKit Server](https://github.com/mother-of-all-self-hosting/ansible-role-livekit-server) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring LiveKit Server, you can check them via:" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:17 -msgid "🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-livekit-server/blob/main/docs/configuring-livekit-server.md) online" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:18 -msgid "📁 `roles/galaxy/livekit_server/docs/configuring-livekit-server.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:20 -msgid "Adjusting firewall rules" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:22 -msgid "To ensure LiveKit Server functions correctly, the following firewall rules and port forwarding settings are required:" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:24 -msgid "`7881/tcp`: ICE/TCP" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:26 -msgid "`7882/udp`: ICE/UDP Mux" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:28 -msgid "`3479/udp`: TURN/UDP. Also see the [Limitations](#limitations) section below." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:30 -msgid "`5350/tcp`: TURN/TCP. Also see the [Limitations](#limitations) section below." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:32 -msgid "`30000-30020/udp`: TURN relay range used by LiveKit's embedded TURN server." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:34 -msgid "💡 The suggestions above are inspired by the upstream [Ports and Firewall](https://docs.livekit.io/home/self-hosting/ports-firewall/) documentation based on how LiveKit is configured in the playbook. If you're using custom configuration for the LiveKit Server role, you may need to adjust firewall rules accordingly." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:36 -msgid "TURN TLS handling" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:38 -msgid "When `matrix_playbook_reverse_proxy_type` is `playbook-managed-traefik` (which is the default for this playbook), TURN over TCP is terminated by Traefik and forwarded to LiveKit with `turn.external_tls = true`. In this playbook default, this mode is enabled automatically when SSL is enabled and TURN is enabled." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:40 -msgid "The playbook installs a dedicated Traefik TCP entrypoint for TURN (`matrix-livekit-turn`) by default and binds it to `tcp/5350`." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:41 -msgid "`livekit_server_config_turn_external_tls` is automatically enabled for this setup." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:42 -msgid "Because Traefik handles TLS, LiveKit no longer needs certificate-file paths for TURN in this mode." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:44 -msgid "To opt out and keep TURN TLS termination in LiveKit itself, set:" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:50 -msgid "In this playbook, certificate paths are managed automatically via `group_vars/matrix_servers` when certificate dumping is enabled." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:52 -msgid "If your setup uses `other-traefik-container` or [another reverse-proxy](./configuring-playbook-own-webserver.md), behavior is unchanged by default and still relies on certificates being available inside the container as before." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:54 -msgid "Deployments using `other-traefik-container` can opt into the same Traefik-terminated mode there, by setting:" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:62 -msgid "and configuring their own Traefik TCP entrypoint dedicated to LiveKit TURN traffic." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:64 -msgid "Limitations" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:66 -msgid "LiveKit Server's TURN listener behavior depends on where TLS is terminated:" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:68 -msgid "Direct LiveKit TURN listeners (`livekit_server_config_turn_external_tls: false`) still use IPv4-only sockets for `3479/udp` and `5350/tcp`, so IPv6 connectivity to these endpoints is not possible." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:69 -msgid "With [TURN TLS handling](#turn-tls-handling) (`livekit_server_config_turn_external_tls: true`), the playbook's dedicated `matrix-livekit-turn` TCP entrypoint can still listen on both IPv4 and IPv6. Traefik then forwards TURN/TCP to LiveKit." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:71 -msgid "It appears that LiveKit Server intentionally only listens on `udp4` and `tcp4` in direct mode, as seen [here](https://github.com/livekit/livekit/blob/154b4d26b769c68a03c096124094b97bf61a996f/pkg/service/turn.go#L128) and [here](https://github.com/livekit/livekit/blob/154b4d26b769c68a03c096124094b97bf61a996f/pkg/service/turn.go#L92)." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ma1sd.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ma1sd.po index 02a30b5e4..94ce2e465 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ma1sd.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ma1sd.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-02-06 16:30+0900\n" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,24 +18,208 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" + +#: ../../../docs/configuring-playbook-ma1sd.md:1 +msgid "Setting up ma1sd Identity Server (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:3 +msgid "**⚠️Note**: ma1sd itself has also been unmaintained for years (the latest commit and release being from 2021). The role of identity servers in the Matrix specification also has an uncertain future. **We recommend not bothering with installing it unless it's the only way you can do what you need to do**. For example, certain things like LDAP integration can also be implemented via [the LDAP provider module for Synapse](./configuring-playbook-ldap-auth.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:5 +msgid "The playbook can configure the [ma1sd](https://github.com/ma1uta/ma1sd) Identity Server for you. It is a fork of [mxisd](https://github.com/kamax-io/mxisd) which was pronounced end of life 2019-06-21." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:7 +msgid "ma1sd is used for 3PIDs (3rd party identifiers like E-mail and phone numbers) and some [enhanced features](https://github.com/ma1uta/ma1sd/#features). It is private by default, potentially at the expense of user discoverability." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:9 +msgid "See the project's [documentation](https://github.com/ma1uta/ma1sd/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:13 +msgid "Open Matrix Federation port" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:15 +msgid "Enabling the ma1sd service will automatically reconfigure your Synapse homeserver to expose the `openid` API endpoints on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. If you enable the component, make sure that the port is accessible." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:17 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:19 +msgid "To make the ma1sd Identity Server enable its federation features, set up a SRV record that looks like this:" +msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:21 -msgid "Setting up ma1sd Identity Server (optional, removed)" +msgid "Name: `_matrix-identity._tcp` (use this text as-is)" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:22 +msgid "Content: `10 0 443 matrix.example.com` (replace `example.com` with your own)" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:24 +msgid "See [ma1sd's documentation](https://github.com/ma1uta/ma1sd/wiki/mxisd-and-your-privacy#choices-are-never-easy) for information on the privacy implications of setting up this SRV record." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:26 +msgid "When setting up a SRV record, if you are asked for a service and protocol instead of a hostname split the host value from the table where the period is. For example use service as `_matrix-identity` and protocol as `_tcp`." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:28 +msgid "**Note**: This `_matrix-identity._tcp` SRV record for the identity server is different from the `_matrix._tcp` that can be used for Synapse delegation. See [howto-server-delegation.md](howto-server-delegation.md) for more information about delegation." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:30 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:32 +msgid "To enable ma1sd, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:38 +msgid "Matrix.org lookup forwarding" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:40 +msgid "To ensure maximum discovery, you can make your identity server also forward lookups to the central matrix.org Identity server (at the cost of potentially leaking all your contacts information)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:42 +msgid "Enabling this is discouraged and you'd better [learn more](https://github.com/ma1uta/ma1sd/blob/master/docs/features/identity.md#lookups) before proceeding." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:44 +msgid "To enable matrix.org forwarding, add the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:50 +msgid "Additional features" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:52 +msgid "What this playbook configures for your is some bare minimum Identity Server functionality, so that you won't need to rely on external 3rd party services." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:54 +msgid "A few variables can be toggled in this playbook to alter the ma1sd configuration that gets generated." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:56 +msgid "Still, ma1sd can do much more. You can refer to the [ma1sd website](https://github.com/ma1uta/ma1sd) for more details and configuration options." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:58 +msgid "To use a more custom configuration, you can define a `matrix_ma1sd_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_ma1sd_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-ma1sd/defaults/main.yml) of the ma1sd component." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:60 +msgid "Customizing email templates" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:62 +msgid "If you'd like to change the default email templates used by ma1sd, take a look at the `matrix_ma1sd_threepid_medium_email_custom_` variables (in the `roles/custom/matrix-ma1sd/defaults/main.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:64 +msgid "ma1sd-controlled Registration" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:66 +msgid "To use the [Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) feature of ma1sd, you can make use of the following variables:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:68 +msgid "`matrix_synapse_enable_registration` — to enable user-initiated registration in Synapse" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:70 +msgid "`matrix_synapse_enable_registration_captcha` — to validate registering users using reCAPTCHA, as described in the [enabling reCAPTCHA](configuring-captcha.md) documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:72 +msgid "`matrix_synapse_registrations_require_3pid` — a list of 3pid types (among `'email'`, `'msisdn'`) required by the Synapse server for registering" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:74 +msgid "variables prefixed with `matrix_ma1sd_container_labels_` (e.g. `matrix_ma1sd_container_labels_matrix_client_3pid_registration_enabled`) — to configure the Traefik reverse-proxy to capture and send registration requests to ma1sd (instead of Synapse), so it can apply its additional functionality" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:76 +msgid "`matrix_ma1sd_configuration_extension_yaml` — to configure ma1sd as required. See the [Registration feature's docs](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) for inspiration. Also see the [Additional features](#additional-features) section below to learn more about how to use `matrix_ma1sd_configuration_extension_yaml`." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:78 +msgid "**Note**: For this to work, either the homeserver needs to [federate](configuring-playbook-federation.md) or the `openid` APIs need to exposed on the federation port. When federation is disabled and ma1sd is enabled, we automatically expose the `openid` APIs (only!) on the federation port. Make sure the federation port (usually `https://matrix.example.com:8448`) is whitelisted in your firewall (even if you don't actually use/need federation)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:80 +msgid "Authentication" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:82 +msgid "[Authentication](https://github.com/ma1uta/ma1sd/blob/master/docs/features/authentication.md) provides the possibility to use your own [Identity Stores](https://github.com/ma1uta/ma1sd/blob/master/docs/stores/README.md) (for example LDAP) to authenticate users on your Homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:84 +msgid "To enable authentication against an LDAP server, add the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:104 +msgid "Example: SMS verification" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:106 +msgid "If your use case requires mobile verification, it is quite simple to integrate ma1sd with [Twilio](https://www.twilio.com/), an online telephony services gateway. Their prices are reasonable for low-volume projects and integration can be done with the following configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:120 +msgid "Example: Open Registration for every Domain" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:122 +msgid "If you want to open registration for any domain, you have to setup the allowed domains with ma1sd's `blacklist` and `whitelist`. The default behavior when neither the `blacklist`, nor the `whitelist` match, is to allow registration. Beware: you can't block toplevel domains (aka `.xy`) because the internal architecture of ma1sd doesn't allow that." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:136 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:138 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:145 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:147 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-ma1sd.md:23 -msgid "🪦 The playbook used to be able to install and configure the [ma1sd](https://github.com/ma1uta/ma1sd) Identity Server, but no longer includes this component, as it has been unmaintained for a long time." +#: ../../../docs/configuring-playbook-ma1sd.md:149 +msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-ma1sd.md:25 -msgid "Please note that some of the functions can be achieved with other components. For example, if you wish to implement LDAP integration, you might as well check out [the LDAP provider module for Synapse](./configuring-playbook-ldap-auth.md) instead." +#: ../../../docs/configuring-playbook-ma1sd.md:151 +msgid "If email address validation emails sent by ma1sd are not reaching you, you should look into [Adjusting email-sending settings](configuring-playbook-email.md)." msgstr "" -#: ../../../docs/configuring-playbook-ma1sd.md:27 -msgid "Uninstalling the component manually" +#: ../../../docs/configuring-playbook-ma1sd.md:153 +msgid "If you'd like additional logging information, temporarily enable verbose logging for ma1sd." msgstr "" -#: ../../../docs/configuring-playbook-ma1sd.md:29 -msgid "If you still have the ma1sd Identity Server 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:" +#: ../../../docs/configuring-playbook-ma1sd.md:155 +msgid "To enable it, add the following configuration to your `vars.yml` file:" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po index 38e7c649f..0301ef979 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,148 +18,112 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-matrix-corporal.md:9 +#: ../../../docs/configuring-playbook-matrix-corporal.md:1 msgid "Setting up Matrix Corporal (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:11 +#: ../../../docs/configuring-playbook-matrix-corporal.md:5 msgid "[!WARNING] This is an advanced feature! It requires prior experience with Matrix and a specific need for using [Matrix Corporal](https://github.com/devture/matrix-corporal). If you're unsure whether you have such a need, you most likely don't." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:14 +#: ../../../docs/configuring-playbook-matrix-corporal.md:10 msgid "The playbook can install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:16 -msgid "In short, it's a sort of automation and firewalling service, which is helpful if you're installing Matrix services in a controlled corporate environment." +#: ../../../docs/configuring-playbook-matrix-corporal.md:12 +msgid "In short, it's a sort of automation and firewalling service, which is helpful if you're instaling Matrix services in a controlled corporate environment." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:18 +#: ../../../docs/configuring-playbook-matrix-corporal.md:14 msgid "See the project's [documentation](https://github.com/devture/matrix-corporal/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:20 +#: ../../../docs/configuring-playbook-matrix-corporal.md:16 msgid "If you decide that you'd like to let this playbook install it for you, you'd need to also:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:21 +#: ../../../docs/configuring-playbook-matrix-corporal.md:17 msgid "(required) [set up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:22 +#: ../../../docs/configuring-playbook-matrix-corporal.md:18 msgid "(optional, but encouraged) [set up the REST authentication password provider module](configuring-playbook-rest-auth.md)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:24 +#: ../../../docs/configuring-playbook-matrix-corporal.md:20 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:26 +#: ../../../docs/configuring-playbook-matrix-corporal.md:22 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:79 +#: ../../../docs/configuring-playbook-matrix-corporal.md:75 msgid "Matrix Corporal operates with a specific Matrix user on your server. By default, it's `matrix-corporal` (controllable by the `matrix_corporal_reconciliation_user_id_local_part` setting, see above)." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:81 +#: ../../../docs/configuring-playbook-matrix-corporal.md:77 msgid "No matter what Matrix user ID you configure to run it with, make sure that:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:83 +#: ../../../docs/configuring-playbook-matrix-corporal.md:79 msgid "the Matrix Corporal user is created by [registering it](registering-users.md) **with administrator privileges**. Use a password you remember, as you'll need to log in from time to time to create or join rooms" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:85 +#: ../../../docs/configuring-playbook-matrix-corporal.md:81 msgid "the Matrix Corporal user is joined and has Admin/Moderator-level access to any rooms you want it to manage" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:87 +#: ../../../docs/configuring-playbook-matrix-corporal.md:83 msgid "Using a locally-stored static policy" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:89 +#: ../../../docs/configuring-playbook-matrix-corporal.md:85 msgid "If you'd like to use a [static policy file](https://github.com/devture/matrix-corporal/blob/master/docs/policy-providers.md#static-file-pull-style-policy-provider), you can use a configuration like this:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:121 +#: ../../../docs/configuring-playbook-matrix-corporal.md:117 msgid "To learn more about what the policy configuration, see the matrix-corporal documentation on [policy](https://github.com/devture/matrix-corporal/blob/master/docs/policy.md)." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:123 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:125 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:127 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:129 -msgid "`roles/custom/matrix-corporal/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:130 -msgid "`roles/custom/matrix-corporal/templates/config.json.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_corporal_configuration_extension_json` variable" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:132 +#: ../../../docs/configuring-playbook-matrix-corporal.md:119 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:134 +#: ../../../docs/configuring-playbook-matrix-corporal.md:121 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:141 +#: ../../../docs/configuring-playbook-matrix-corporal.md:128 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-aux-files,setup-corporal,start` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:143 +#: ../../../docs/configuring-playbook-matrix-corporal.md:130 msgid "`just run-tags setup-aux-files,setup-corporal,start` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:145 +#: ../../../docs/configuring-playbook-matrix-corporal.md:132 msgid "Matrix Corporal files" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:147 +#: ../../../docs/configuring-playbook-matrix-corporal.md:134 msgid "The following local filesystem paths are mounted in the `matrix-corporal` container and can be used in your configuration (or policy):" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:149 +#: ../../../docs/configuring-playbook-matrix-corporal.md:136 msgid "`/matrix/corporal/config` is mounted at `/etc/matrix-corporal` (read-only)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:151 +#: ../../../docs/configuring-playbook-matrix-corporal.md:138 msgid "`/matrix/corporal/var` is mounted at `/var/matrix-corporal` (read and write)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:153 +#: ../../../docs/configuring-playbook-matrix-corporal.md:140 msgid "`/matrix/corporal/cache` is mounted at `/var/cache/matrix-corporal` (read and write)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:155 +#: ../../../docs/configuring-playbook-matrix-corporal.md:142 msgid "As an example: you can create your own configuration files in `/matrix/corporal/config` and they will appear in `/etc/matrix-corporal` in the Docker container. Your configuration (stuff in `matrix_corporal_policy_provider_config`) needs to refer to these files via the local container paths — `/etc/matrix-corporal` (read-only), `/var/matrix-corporal` (read and write), `/var/cache/matrix-corporal` (read and write)." msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:157 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:159 -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-corporal`." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:161 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-corporal.md:163 -msgid "If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po index f6c4187e1..8996149c8 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,76 +18,48 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:9 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:1 msgid "Setting up matrix-ldap-registration-proxy (optional)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:11 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:3 msgid "The playbook can install and configure [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) for you." msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:13 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:5 msgid "This proxy handles Matrix registration requests and forwards them to LDAP." msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:15 -msgid "See the project's [documentation](https://gitlab.com/activism.international/matrix_ldap_registration_proxy/-/blob/main/README.md) to learn what it does and why it might be useful to you." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:17 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:7 msgid "**Note**: This does support the full Matrix specification for registrations. It only provide a very coarse implementation of a basic password registration." msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:19 -msgid "Adjusting the playbook configuration" +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:9 +msgid "Quickstart" msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:21 -msgid "To enable the component, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:11 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:33 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:22 msgid "If you already use the [synapse external password provider via LDAP](configuring-playbook-ldap-auth.md) (that is, you have `matrix_synapse_ext_password_provider_ldap_enabled: true` and other options in your configuration) you can use the following values as configuration:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:46 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:48 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:50 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:52 -msgid "`roles/custom/matrix-ldap-registration-proxy/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:54 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:35 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:56 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:37 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:63 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:44 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:65 +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:46 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:67 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.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-ldap-registration-proxy`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po index 63d7ce721..82cecc0af 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po @@ -10,7 +10,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: 2024-12-28 10:25+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,219 +18,151 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:10 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:1 msgid "Storing Matrix media files using matrix-media-repo (optional)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:12 -msgid "The playbook can install and configure [matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often abbreviated \"MMR\") for you." +#: ../../../docs/configuring-playbook-matrix-media-repo.md:3 +msgid "[matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often abbreviated \"MMR\") is a highly customizable multi-domain media repository for Matrix. Intended for medium to large environments consisting of several homeservers, this media repo de-duplicates media (including remote media) while being fully compliant with the specification." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:14 -msgid "MMR is a highly customizable multi-domain media repository for Matrix. Intended for medium to large environments consisting of several homeservers, this media repo de-duplicates media (including remote media) while being fully compliant with the specification." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:16 -msgid "**Notes**:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:17 -msgid "If MMR is enabled, other media store roles should be disabled (if using Synapse with other media store roles)." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:18 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:5 msgid "Smaller/individual homeservers can still make use of this project's features, though it may be difficult to set up or have higher than expected resource consumption. Please do your research before deploying this as this project may not be useful for your environment." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:19 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:7 msgid "For a simpler alternative (which allows you to offload your media repository storage to S3, etc.), you can [configure S3 storage](configuring-playbook-s3.md) instead of setting up matrix-media-repo." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:21 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:23 -msgid "To enable matrix-media-repo, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:34 -msgid "**For existing installations**: retrieve the current datastore ID from the server's config file before proceeding:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:40 -msgid "Then use that value for `matrix_media_repo_datastore_file_id`. This is not a secret — it is a plain identifier used by matrix-media-repo to link media files to their storage backend." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:42 -msgid "By default, the media-repo will use the local filesystem for data storage. You can alternatively use a `s3` cloud backend as well. Access token caching is also enabled by default since the logout endpoints are proxied through the media repo." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:44 -msgid "Enable metrics" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:46 -msgid "The playbook can enable and configure the metrics of the service for you." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:48 -msgid "Metrics are **only enabled by default** if the builtin [Prometheus](configuring-playbook-prometheus-grafana.md) is enabled (by default, Prometheus isn't enabled). If so, metrics will automatically be collected by Prometheus and made available in Grafana. You will, however, need to set up your own Dashboard for displaying them." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:50 -msgid "To enable the metrics, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-matrix-media-repo.md +msgid "**Table of Contents**" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:57 -msgid "**To collect metrics from an external Prometheus server**, besides enabling metrics as described above, you will also need to enable metrics exposure on `https://matrix.example.com/metrics/matrix-media-repo` by adding the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-matrix-media-repo.md +msgid "[Quickstart](#quickstart)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:63 -msgid "By default metrics are exposed publicly **without** password-protection. To password-protect the metrics with dedicated credentials, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-matrix-media-repo.md +msgid "[Additional configuration options](#configuring-the-media-repo)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:70 -msgid "To `matrix_media_repo_container_labels_traefik_metrics_middleware_basic_auth_users`, set the Basic Authentication credentials (raw `htpasswd` file content) used to protect the endpoint. See https://doc.traefik.io/traefik/middlewares/http/basicauth/#users for details about it." +#: ../../../docs/configuring-playbook-matrix-media-repo.md +msgid "[Importing data from an existing media store](#importing-data-from-an-existing-media-store)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:72 -msgid "**Note**: alternatively, you can use `matrix_metrics_exposure_enabled` to expose all services on this `/metrics/*` feature, and you can use `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users` to password-protect the metrics of them. See [this section](configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) for more information." +#: ../../../docs/configuring-playbook-matrix-media-repo.md:15 +msgid "Quickstart" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:74 -msgid "Enable Grafana (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:76 -msgid "Probably you wish to enable Grafana along with Prometheus for generating graphs of the metrics." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:78 -msgid "To enable Grafana, see [this section](configuring-playbook-prometheus-grafana.md#adjusting-the-playbook-configuration-grafana) for instructions." +#: ../../../docs/configuring-playbook-matrix-media-repo.md:17 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file and [re-run the installation process](./installing.md) for the playbook:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:80 -msgid "Extending the configuration" +#: ../../../docs/configuring-playbook-matrix-media-repo.md:26 +msgid "The repo is pre-configured for integrating with the Postgres database, Traefik proxy and [Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) (if metrics enabled) from this playbook for all the available homeserver roles. When the media repo is enabled, other media store roles should be disabled (if using Synapse with other media store roles)." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:82 -msgid "There are some additional things you may wish to configure about the component." +#: ../../../docs/configuring-playbook-matrix-media-repo.md:28 +msgid "By default, the media-repo will use the local filesystem for data storage. You can alternatively use a `s3` cloud backend as well. Access token caching is also enabled by default since the logout endpoints are proxied through the media repo." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:84 -msgid "Take a look at:" +#: ../../../docs/configuring-playbook-matrix-media-repo.md:30 +msgid "Configuring the media-repo" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:86 -msgid "`roles/custom/matrix-media-repo/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +#: ../../../docs/configuring-playbook-matrix-media-repo.md:32 +msgid "Additional common configuration options:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:88 -msgid "Here is a list of additional common configuration options:" +#: ../../../docs/configuring-playbook-matrix-media-repo.md:91 +msgid "Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](../roles/custom/matrix-media-repo/defaults/main.yml)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:150 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:93 msgid "Signing Keys" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:152 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:95 msgid "Authenticated media endpoints ([MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916)) requires MMR to have a configured signing key to authorize outbound federation requests. Additionally, the signing key must be merged with your homeserver's signing key file." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:154 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:97 msgid "The playbook default is to generate a MMR signing key when invoking the setup role and merge it with your homeserver if you are using Synapse or Dendrite. This can be disabled if desired by setting the option in your inventory:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:160 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:103 msgid "If you wish to manually generate the signing key and merge it with your homeserver's signing key file, see https://docs.t2bot.io/matrix-media-repo/v1.3.5/installation/signing-key/ for more details." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:162 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:105 msgid "**Note that if you uninstall MMR from the playbook, it will not remove the old MMR signing key from your homeserver's signing key file. You will have to remove it manually.**" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:164 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:107 msgid "Key backup and revoking" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:166 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:109 msgid "Since your homeserver signing key file is modified by the playbook, a backup will be created in `HOMESERVER_DIR/config/example.com.signing.key.backup`. If you need to remove/revoke old keys, you can restore from this backup or remove the MMR key ID from your `example.com.signing.key` file." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:168 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:111 msgid "Additionally, its recommended after revoking a signing key to update your homeserver config file (`old_signing_keys` field for Synapse and `old_private_keys` for Dendrite). See your homeserver config file for further documentation on how to populate the field." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:170 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:113 msgid "Importing data from an existing media store" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:172 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:115 msgid "If you want to add this repo to an existing homeserver managed by the playbook, you will need to import existing media into MMR's database or you will lose access to older media while it is active. MMR versions up to `v1.3.3` only support importing from Synapse, but newer versions (at time of writing: only `latest`) also support importing from Dendrite." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:174 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:117 msgid "**Before importing**: ensure you have an initial matrix-media-repo deployment by following the [quickstart](#quickstart) guide above" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:176 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:119 msgid "Depending on the homeserver implementation yu're using (Synapse, Dendrite), you'll need to use a different import tool (part of matrix-media-repo) and point it to the homeserver's database." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:178 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:121 msgid "Importing data from the Synapse media store" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:180 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:123 msgid "To import the Synapse media store, you're supposed to invoke the `import_synapse` tool which is part of the matrix-media-repo container image. Your Synapse database is called `synapse` by default, unless you've changed it by modifying `matrix_synapse_database_database`." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:182 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:125 msgid "This guide here is adapted from the [upstream documentation about the import_synapse script](https://github.com/turt2live/matrix-media-repo#importing-media-from-synapse)." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:184 -#: ../../../docs/configuring-playbook-matrix-media-repo.md:206 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:127 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:149 msgid "Run the following command on the server (after replacing `postgres_connection_password` in it with the value found in your `vars.yml` file):" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:196 -#: ../../../docs/configuring-playbook-matrix-media-repo.md:218 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:139 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:161 msgid "Enter `1` for the Machine ID when prompted (you are not doing any horizontal scaling) unless you know what you're doing." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:198 -#: ../../../docs/configuring-playbook-matrix-media-repo.md:220 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:141 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:163 msgid "This should output a `msg=\"Import completed\"` when finished successfully!" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:200 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:143 msgid "Importing data from the Dendrite media store" msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:202 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:145 msgid "If you're using the [Dendrite](configuring-playbook-dendrite.md) homeserver instead of the default for this playbook (Synapse), follow this importing guide here." msgstr "" -#: ../../../docs/configuring-playbook-matrix-media-repo.md:204 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:147 msgid "To import the Dendrite media store, you're supposed to invoke the `import_dendrite` tool which is part of the matrix-media-repo container image. Your Dendrite database is called `dendrite_mediaapi` by default, unless you've changed it by modifying `matrix_dendrite_media_api_database`." msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:222 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:224 -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-media-repo`." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:226 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-media-repo.md:228 -msgid "If you want to turn on sentry's built-in debugging, add the following configuration to your `vars.yml` file and re-run the playbook:" -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po index 2458fa44b..d436873d7 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,168 +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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-matrix-registration.md:9 +#: ../../../docs/configuring-playbook-matrix-registration.md:1 msgid "Setting up matrix-registration (optional)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:11 -msgid "[!WARNING]" +#: ../../../docs/configuring-playbook-matrix-registration.md:3 +msgid "⚠️ **Warnings**:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:12 +#: ../../../docs/configuring-playbook-matrix-registration.md:4 msgid "This is a poorly maintained and buggy project. It's better to avoid using it." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:13 +#: ../../../docs/configuring-playbook-matrix-registration.md:5 msgid "This is not related to [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:15 +#: ../../../docs/configuring-playbook-matrix-registration.md:7 msgid "The playbook can install and configure [matrix-registration](https://github.com/ZerataX/matrix-registration) for you. It is a simple python application to have a token based Matrix registration." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:17 +#: ../../../docs/configuring-playbook-matrix-registration.md:9 msgid "Use matrix-registration to **create unique registration links**, which people can use to register on your Matrix server. It allows certain people (these having a special link) to register a user account, **keeping your server's registration closed (private)**." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:19 +#: ../../../docs/configuring-playbook-matrix-registration.md:11 msgid "**matrix-registration** provides 2 things:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:21 +#: ../../../docs/configuring-playbook-matrix-registration.md:13 msgid "**an API for creating registration tokens** (unique registration links). This API can be used via `curl` or via the playbook (see [Usage](#usage) below)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:23 +#: ../../../docs/configuring-playbook-matrix-registration.md:15 msgid "**a user registration page**, where people can use these registration tokens. By default, exposed at `https://matrix.example.com/matrix-registration`" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:25 +#: ../../../docs/configuring-playbook-matrix-registration.md:17 msgid "Adjusting DNS records (optional)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:27 +#: ../../../docs/configuring-playbook-matrix-registration.md:19 msgid "By default, this playbook installs the matrix-registration on the `matrix.` subdomain, at the `/matrix-registration` path (https://matrix.example.com/matrix-registration). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:29 +#: ../../../docs/configuring-playbook-matrix-registration.md:21 msgid "If you wish to adjust it, see the section [below](#adjusting-the-matrix-registration-url-optional) for details about DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:31 +#: ../../../docs/configuring-playbook-matrix-registration.md:23 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:33 +#: ../../../docs/configuring-playbook-matrix-registration.md:25 msgid "To enable matrix-registration, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:42 +#: ../../../docs/configuring-playbook-matrix-registration.md:34 msgid "Adjusting the matrix-registration URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:44 +#: ../../../docs/configuring-playbook-matrix-registration.md:36 msgid "By tweaking the `matrix_registration_hostname` and `matrix_registration_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:46 +#: ../../../docs/configuring-playbook-matrix-registration.md:38 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:54 +#: ../../../docs/configuring-playbook-matrix-registration.md:46 msgid "If you've changed the default hostname, you may need to create a CNAME record for the matrix-registration domain (`registration.example.com`), which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:56 +#: ../../../docs/configuring-playbook-matrix-registration.md:48 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:58 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-registration.md:60 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-registration.md:62 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-registration.md:64 -msgid "`roles/custom/matrix-registration/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-registration.md:65 -msgid "`roles/custom/matrix-registration/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_registration_configuration_extension_yaml` variable" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-registration.md:67 +#: ../../../docs/configuring-playbook-matrix-registration.md:50 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:69 +#: ../../../docs/configuring-playbook-matrix-registration.md:52 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:76 +#: ../../../docs/configuring-playbook-matrix-registration.md:59 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:78 +#: ../../../docs/configuring-playbook-matrix-registration.md:61 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:80 +#: ../../../docs/configuring-playbook-matrix-registration.md:63 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:82 +#: ../../../docs/configuring-playbook-matrix-registration.md:65 msgid "**matrix-registration** gets exposed at `https://matrix.example.com/matrix-registration`" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:84 +#: ../../../docs/configuring-playbook-matrix-registration.md:67 msgid "It provides various [APIs](https://github.com/ZerataX/matrix-registration/wiki/api) — for creating registration tokens, listing tokens, disabling tokens, etc. To make use of all of its capabilities, consider using `curl`." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:86 +#: ../../../docs/configuring-playbook-matrix-registration.md:69 msgid "We make the most common APIs easy to use via the playbook (see below)." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:88 +#: ../../../docs/configuring-playbook-matrix-registration.md:71 msgid "Creating registration tokens" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:90 +#: ../../../docs/configuring-playbook-matrix-registration.md:73 msgid "To **create a new user registration token (link)**, use this command:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:98 +#: ../../../docs/configuring-playbook-matrix-registration.md:81 msgid "The above command creates and returns a **one-time use** token, which **expires** on the 31st of December 2021. Adjust the `one_time` and `ex_date` variables as you see fit." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:100 +#: ../../../docs/configuring-playbook-matrix-registration.md:83 msgid "Share the unique registration link (generated by the command above) with users to let them register on your Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:102 +#: ../../../docs/configuring-playbook-matrix-registration.md:85 msgid "Listing registration tokens" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:104 +#: ../../../docs/configuring-playbook-matrix-registration.md:87 msgid "To **list the existing user registration tokens**, use this command:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-registration.md:111 +#: ../../../docs/configuring-playbook-matrix-registration.md:94 msgid "The shortcut command with `just` program is also available: `just run-tags list-matrix-registration-tokens`" msgstr "" - -#: ../../../docs/configuring-playbook-matrix-registration.md:113 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-registration.md:115 -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-registration`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-rtc.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-rtc.po deleted file mode 100644 index d02a9bf8e..000000000 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-rtc.po +++ /dev/null @@ -1,109 +0,0 @@ -# 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 , 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 \n" -"Language: jp\n" -"Language-Team: jp \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-matrix-rtc.md:8 -msgid "Setting up the Matrix RTC stack (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:10 -msgid "The playbook can install and configure the Matrix RTC (Real-Time Communication) stack." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:12 -msgid "The Matrix RTC stack is a set of supporting components ([LiveKit Server](configuring-playbook-livekit-server.md) and [LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md)) that allow the new [Element Call](configuring-playbook-element-call.md) audio/video calls to function." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:14 -msgid "💡 If you only plan on doing audio/video calls via Matrix client (which typically embed the Element Call frontend UI within them), you only need to install the Matrix RTC stack and don't necessarily need to install [Element Call](configuring-playbook-element-call.md). See the [Decide between Element Call vs just the Matrix RTC stack](configuring-playbook-element-call.md#decide-between-element-call-vs-just-the-matrix-rtc-stack) section of the [Element Call documentation](configuring-playbook-element-call.md) for more details." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:16 -msgid "Prerequisites" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:18 -msgid "A [Synapse](configuring-playbook-synapse.md) homeserver (see the warning below)" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:19 -msgid "Various experimental features for the Synapse homeserver which Element Call [requires](https://github.com/element-hq/element-call/blob/93ae2aed9841e0b066d515c56bd4c122d2b591b2/docs/self-hosting.md#a-matrix-homeserver) (automatically done when Element Call is enabled)" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:20 -msgid "A [LiveKit Server](configuring-playbook-livekit-server.md) (automatically installed when [Element Call or the Matrix RTC stack is enabled](configuring-playbook-element-call.md#decide-between-element-call-vs-just-the-matrix-rtc-stack))" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:21 -msgid "The [LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md) (automatically installed when [Element Call or the Matrix RTC stack is enabled](configuring-playbook-element-call.md#decide-between-element-call-vs-just-the-matrix-rtc-stack))" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:22 -msgid "A client compatible with Element Call. As of 2025-03-15, that's just [Element Web](configuring-playbook-client-element-web.md) and the Element X mobile clients (iOS and Android)." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:24 -msgid "[!WARNING] Because Element Call [requires](https://github.com/element-hq/element-call/blob/93ae2aed9841e0b066d515c56bd4c122d2b591b2/docs/self-hosting.md#a-matrix-homeserver) a few experimental features in the Matrix protocol, it's **very likely that it only works with the Synapse homeserver**." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:27 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:29 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:37 -msgid "Adjusting firewall rules" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:39 -msgid "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." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:41 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:43 -msgid "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:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:50 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:52 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:54 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:56 -msgid "Once installed, Matrix clients which support Element Call (like [Element Web](configuring-playbook-client-element-web.md) and Element X on mobile (iOS and Android)) will automatically use the Matrix RTC stack." -msgstr "" - -#: ../../../docs/configuring-playbook-matrix-rtc.md:58 -msgid "These clients typically embed the Element Call frontend UI within them, so installing [Element Call](configuring-playbook-element-call.md) is only necessary if you'd like to use it standalone - directly via a browser." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrixto.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrixto.po deleted file mode 100644 index 1e7825bb8..000000000 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrixto.po +++ /dev/null @@ -1,117 +0,0 @@ -# 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 , 2026. -# -#, fuzzy -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" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: jp\n" -"Language-Team: jp \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-matrixto.md:8 -msgid "Setting up Matrix.to (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:10 -msgid "The playbook can install and configure the [Matrix.to](https://github.com/matrix-org/matrix.to) URL redirection service for you." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:12 -msgid "See the project's [documentation](https://github.com/matrix-org/matrix.to/blob/main/README.md) to learn what it does and why it might be useful to you." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:14 -msgid "Adjusting DNS records" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:16 -msgid "By default, this playbook installs Matrix.to on the `mt.` subdomain (`mt.example.com`) and requires you to create a CNAME record for `mt`, which targets `matrix.example.com`." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:18 -msgid "When setting, replace `example.com` with your own." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:20 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:22 -msgid "To enable Matrix.to, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:28 -msgid "Adjusting the Matrix.to URL (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:30 -msgid "By tweaking the `matrix_matrixto_hostname` variable, you can easily make the service available at a **different hostname** than the default one." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:32 -msgid "Example additional configuration for your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:39 -msgid "After changing the domain, **you may need to adjust your DNS** records to point the Matrix.to domain to the Matrix server." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:41 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:43 -msgid "There are some additional things you may wish to configure about the server." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:45 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:47 -msgid "`roles/custom/matrix-matrixto/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:49 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:51 -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-matrixto.md:58 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:60 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:62 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:64 -msgid "Refer to the project's [documentation](https://github.com/matrix-org/matrix.to/blob/main/README.md) for available parameters, etc." -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:66 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-matrixto.md:68 -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-matrixto`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ntfy.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ntfy.po index 6671d02ba..a1b1d2551 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ntfy.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ntfy.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,260 +18,220 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-ntfy.md:12 +#: ../../../docs/configuring-playbook-ntfy.md:1 msgid "Setting up the ntfy push notifications server (optional)" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:14 -msgid "The playbook can install and configure the [ntfy](https://ntfy.sh/) (pronounced \"notify\") push notifications server for you." +#: ../../../docs/configuring-playbook-ntfy.md:3 +msgid "The playbook can install and configure the [ntfy](https://ntfy.sh/) push notifications server for you." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:16 -msgid "ntfy lets you send push notifications to your phone or desktop via scripts from any computer, using simple HTTP PUT or POST requests. It makes it possible to send/receive notifications, without relying on servers owned and controlled by third parties." +#: ../../../docs/configuring-playbook-ntfy.md:5 +msgid "Using the [UnifiedPush](https://unifiedpush.org) standard, ntfy enables self-hosted (Google-free) push notifications from Matrix (and other) servers to UnifiedPush-compatible Matrix compatible client apps running on Android and other devices." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:18 -msgid "With the [UnifiedPush](https://unifiedpush.org) standard, ntfy also enables self-hosted push notifications from Matrix (and other) servers to UnifiedPush-compatible Matrix client apps running on Android devices." +#: ../../../docs/configuring-playbook-ntfy.md:7 +msgid "This role is intended to support UnifiedPush notifications for use with the Matrix and Matrix-related services that this playbook installs. This role is not intended to support all of ntfy's other features." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:20 -msgid "See the project's [documentation](https://docs.ntfy.sh/) to learn what ntfy does and why it might be useful to you." +#: ../../../docs/configuring-playbook-ntfy.md:9 +msgid "**Note**: In contrast to push notifications using Google's FCM or Apple's APNs, the use of UnifiedPush allows each end-user to choose the push notification server that they prefer. As a consequence, deploying this ntfy server does not by itself ensure any particular user or device or client app will use it." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:22 -msgid "The [Ansible role for ntfy](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring ntfy, you can check them via:" -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:23 -msgid "🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/docs/configuring-ntfy.md) online" -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:24 -msgid "📁 `roles/galaxy/ntfy/docs/configuring-ntfy.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:26 -msgid "**Note**: this playbook focuses on setting up a ntfy server for getting it send push notifications with UnifiedPush to Matrix-related services that this playbook installs, while the installed server will be available for other non-Matrix apps like [Tusky](https://tusky.app/) and [DAVx⁵](https://www.davx5.com/) as well. This playbook does not intend to support all of ntfy's features. If you want to use them as well, refer the role's documentation for details to configure them by yourself." -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:28 -msgid "Improve push notification's privacy with ntfy" -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:30 -msgid "By default, push notifications received on Matrix apps on Android/iOS act merely as \"wake-up calls\" for the application, which contain only event IDs, and do not transmit actual message payload such as text message data." -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:32 -msgid "While your messages remain private even without ntfy, it makes it possible to improve privacy and sovereignty of your Matrix installation, offering greater control over your data, by avoiding routing these \"application wake-up calls\" through Google or Apple servers and having them pass through the self-hosted ntfy instance on your Matrix server." -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:34 -msgid "How ntfy works with UnifiedPush" -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:36 -msgid "⚠️ [UnifiedPush does not work on iOS.](https://unifiedpush.org/users/faq/#will-unifiedpush-ever-work-on-ios)" -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:38 -msgid "ntfy implements UnifiedPush, the standard which makes it possible to send and receive push notifications without using Google's Firebase Cloud Messaging (FCM) service." -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:40 -msgid "Working as a **Push Server**, a ntfy server can forward messages via [the ntfy Android app](https://docs.ntfy.sh/subscribe/phone/) as a **Distributor** to a UnifiedPush-compatible Matrix client such as Element Android and FluffyChat Android (see [here](https://unifiedpush.org/users/distributors/#definitions) for the definition of the Push Server and the Distributor)." -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:42 -msgid "Note that UnifiedPush-compatible applications must be able to communicate with the ntfy Android app which works as the Distributor on the same device, in order to receive push notifications from the Push Server." -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:44 -msgid "As the ntfy Android app functions as the Distributor, you do not have to install something else on your device, besides a UnifiedPush-compatible Matrix client." -msgstr "" - -#: ../../../docs/configuring-playbook-ntfy.md:46 +#: ../../../docs/configuring-playbook-ntfy.md:11 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:48 +#: ../../../docs/configuring-playbook-ntfy.md:13 msgid "By default, this playbook installs ntfy on the `ntfy.` subdomain (`ntfy.example.com`) and requires you to create a CNAME record for `ntfy`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:50 +#: ../../../docs/configuring-playbook-ntfy.md:15 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:52 +#: ../../../docs/configuring-playbook-ntfy.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:54 -msgid "To enable a ntfy server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +#: ../../../docs/configuring-playbook-ntfy.md:19 +msgid "To enable ntfy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:72 -msgid "As the most of the necessary settings for the role have been taken care of by the playbook, you can enable the ntfy server on your Matrix server with this minimum configuration." +#: ../../../docs/configuring-playbook-ntfy.md:33 +msgid "For a more complete list of variables that you could override, see the [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/defaults/main.yml) of the ntfy Ansible role." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:74 -msgid "See the role's documentation for details about configuring ntfy per your preference (such as [setting access control with authentication](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/docs/configuring-ntfy.md#enable-access-control-with-authentication-optional))." +#: ../../../docs/configuring-playbook-ntfy.md:35 +msgid "For a complete list of ntfy config options that you could put in `ntfy_configuration_extension_yaml`, see the [ntfy config documentation](https://ntfy.sh/docs/config/#config-options)." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:76 +#: ../../../docs/configuring-playbook-ntfy.md:37 msgid "Adjusting the ntfy URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:78 +#: ../../../docs/configuring-playbook-ntfy.md:39 msgid "By tweaking the `ntfy_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:80 +#: ../../../docs/configuring-playbook-ntfy.md:41 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:87 +#: ../../../docs/configuring-playbook-ntfy.md:48 msgid "After changing the domain, **you may need to adjust your DNS** records to point the ntfy domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:89 -msgid "Enable web app (optional)" +#: ../../../docs/configuring-playbook-ntfy.md:50 +msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:91 -msgid "The ntfy server can be accessed via its web app where you can subscribe to and push to \"topics\" from the browser. The web app may be helpful to troubleshoot notification issues or to use ntfy for other purposes than getting ntfy send UnifiedPush notifications to your Matrix-related services." +#: ../../../docs/configuring-playbook-ntfy.md:52 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:93 -msgid "**Note**: subscribing to a topic is not necessary for using the nfty server as the Push Server for UnifiedPush." +#: ../../../docs/configuring-playbook-ntfy.md:59 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:95 -msgid "To enable the web app, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-ntfy.md:61 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:101 -msgid "See [the official documentation](https://docs.ntfy.sh/subscribe/web/) for details about how to use it." +#: ../../../docs/configuring-playbook-ntfy.md:63 +msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:103 -msgid "Installing" +#: ../../../docs/configuring-playbook-ntfy.md:65 +msgid "To make use of your ntfy installation, on Android for example, you need two things:" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:105 -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:" +#: ../../../docs/configuring-playbook-ntfy.md:67 +msgid "the `ntfy` app" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:112 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +#: ../../../docs/configuring-playbook-ntfy.md:68 +msgid "a UnifiedPush-compatible Matrix app" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:114 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-ntfy.md:70 +msgid "You need to install the `ntfy` app on each device on which you want to receive push notifications through your ntfy server. The `ntfy` app will provide UnifiedPush notifications to any number of UnifiedPush-compatible messaging apps installed on the same device." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:116 -msgid "Usage" +#: ../../../docs/configuring-playbook-ntfy.md:72 +msgid "Setting up the `ntfy` Android app" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:118 -msgid "To receive push notifications with UnifiedPush from the ntfy server, you need to **install [the ntfy Android app](https://docs.ntfy.sh/subscribe/phone/)** which works as the Distributor, **log in to the account on the ntfy app** if you have enabled the access control, and then **configure a UnifiedPush-compatible Matrix client**. After setting up the ntfy Android app, the Matrix client listens to it, and push notifications are \"distributed\" from it." +#: ../../../docs/configuring-playbook-ntfy.md:74 +msgid "Install the [ntfy Android app](https://ntfy.sh/docs/subscribe/phone/) from F-droid or Google Play." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:120 -msgid "For details about installing and configuring the ntfy Android app, take a look at [this section](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/docs/configuring-ntfy.md#install-the-ntfy-androidios-app) on the role's documentation." +#: ../../../docs/configuring-playbook-ntfy.md:75 +msgid "In its Settings -> `General: Default server`, enter your ntfy server URL, such as `https://ntfy.example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:76 +msgid "In its Settings -> `Advanced: Connection protocol`, choose `WebSockets`." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:78 +msgid "That is all you need to do in the ntfy app. It has many other features, but for our purposes you can ignore them. In particular you do not need to follow any instructions about subscribing to a notification topic as UnifiedPush will do that automatically." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:122 -msgid "⚠️ Though the ntfy app is available for iOS ([App Store](https://apps.apple.com/us/app/ntfy/id1625396347); the app's source code can be retrieved from [here](https://github.com/binwiederhier/ntfy-ios)), **any Matrix clients for iOS currently do not support ntfy** due to [technical limitations of the iOS platform](https://github.com/binwiederhier/ntfy-ios/blob/main/docs/TECHNICAL_LIMITATIONS.md). If you develop your own Matrix client app for iOS, you may need to use the [Sygnal](configuring-playbook-sygnal.md) push gateway service to deliver push notifications to it." +#: ../../../docs/configuring-playbook-ntfy.md:80 +msgid "Setting up a UnifiedPush-compatible Matrix app" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:124 -msgid "Setting up a UnifiedPush-compatible Matrix client" +#: ../../../docs/configuring-playbook-ntfy.md:82 +msgid "Install any UnifiedPush-enabled Matrix app on that same device. The Matrix app will learn from the `ntfy` app that you have configured UnifiedPush on this device, and then it will tell your Matrix server to use it." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:126 -msgid "Having configured the ntfy Android app, you can configure a UnifiedPush-compatible Matrix client on the same device." +#: ../../../docs/configuring-playbook-ntfy.md:84 +msgid "Steps needed for specific Matrix apps:" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:128 -msgid "Steps needed for specific Matrix clients:" +#: ../../../docs/configuring-playbook-ntfy.md:86 +msgid "FluffyChat-android:" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:130 -msgid "FluffyChat-Android: this should auto-detect and use the app. No manual settings required." +#: ../../../docs/configuring-playbook-ntfy.md:87 +msgid "Should auto-detect and use it. No manual settings." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:132 -msgid "SchildiChat-Android:" +#: ../../../docs/configuring-playbook-ntfy.md:89 +msgid "SchildiChat-android:" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:133 +#: ../../../docs/configuring-playbook-ntfy.md:90 msgid "enable `Settings` -> `Notifications` -> `UnifiedPush: Force custom push gateway`." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:134 -msgid "choose `Settings` -> `Notifications` -> `UnifiedPush: Re-register push distributor`. *(For info, a more complex alternative to achieve the same is: delete the relevant unifiedpush registration in the ntfy Android app, force-close SchildiChat, re-open it.)*" +#: ../../../docs/configuring-playbook-ntfy.md:91 +msgid "choose `Settings` -> `Notifications` -> `UnifiedPush: Re-register push distributor`. *(For info, a more complex alternative to achieve the same is: delete the relevant unifiedpush registration in `ntfy` app, force-close SchildiChat, re-open it.)*" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:135 +#: ../../../docs/configuring-playbook-ntfy.md:92 msgid "verify `Settings` -> `Notifications` -> `UnifiedPush: Notification targets` as described below in the \"Troubleshooting\" section." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:137 -msgid "Element-Android v1.4.26+:" +#: ../../../docs/configuring-playbook-ntfy.md:94 +msgid "Element-android v1.4.26+:" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:138 +#: ../../../docs/configuring-playbook-ntfy.md:95 msgid "choose `Settings` -> `Notifications` -> `Notification method` -> `ntfy`" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:139 +#: ../../../docs/configuring-playbook-ntfy.md:96 msgid "verify `Settings` -> `Troubleshoot` -> `Troubleshoot notification settings`" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:141 -msgid "If the Matrix client asks, \"Choose a distributor: FCM Fallback or ntfy\", then choose \"ntfy\"." +#: ../../../docs/configuring-playbook-ntfy.md:98 +msgid "If the Matrix app asks, \"Choose a distributor: FCM Fallback or ntfy\", then choose \"ntfy\"." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:143 -msgid "If the Matrix client doesn't seem to pick it up, try restarting it and try the Troubleshooting section below." +#: ../../../docs/configuring-playbook-ntfy.md:100 +msgid "If the Matrix app doesn't seem to pick it up, try restarting it and try the Troubleshooting section below." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:145 -msgid "Troubleshooting" +#: ../../../docs/configuring-playbook-ntfy.md:102 +msgid "Web App" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:147 -msgid "The simple [UnifiedPush troubleshooting](https://unifiedpush.org/users/troubleshooting/) app [UP-Example](https://f-droid.org/en/packages/org.unifiedpush.example/) can be used to manually test UnifiedPush registration and operation on an Android device." +#: ../../../docs/configuring-playbook-ntfy.md:104 +msgid "ntfy also has a web app to subscribe to and push to topics from the browser. This may be helpful to further troubleshoot UnifiedPush problems or to use ntfy for other purposes. The web app only runs in the browser locally (after downloading the JavaScript)." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:149 -msgid "Check the Matrix client" +#: ../../../docs/configuring-playbook-ntfy.md:106 +msgid "The web app is disabled in this playbook by default as the expectation is that most users won't use it. You can either use the [official hosted one](https://ntfy.sh/app) (it supports using other public reachable ntfy instances) or host it yourself by setting `ntfy_web_root: \"app\"` and re-running Ansible." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:151 -msgid "Make sure that the Matrix client you are using supports UnifiedPush. There may well be different variants of the app." +#: ../../../docs/configuring-playbook-ntfy.md:108 +msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:153 -msgid "To check if UnifiedPush is correctly configured on the client device, look at \"Settings -> Notifications -> Notification Targets\" in Element Android or SchildiChat Android, or \"Settings -> Notifications -> Devices\" in FluffyChat. There should be one entry for each Matrix client that has enabled push notifications, and when that client is using UnifiedPush you should see a URL that begins with your ntfy server's URL." +#: ../../../docs/configuring-playbook-ntfy.md:110 +msgid "First check that the Matrix client app you are using supports UnifiedPush. There may well be different variants of the app." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:155 -msgid "In the \"Notification Targets\" screen in Element Android or SchildiChat Android, two relevant URLs are shown, \"push\\_key\" and \"Url\", and both should begin with your ntfy server's URL. If \"push\\_key\" shows your server but \"Url\" shows an external server such as `up.schildi.chat` then push notifications will still work but are being routed through that external server before they reach your ntfy server. To rectify that, in SchildiChat (at least around version 1.4.20.sc55) you must enable the `Force custom push gateway` setting as described in the \"Usage\" section above." +#: ../../../docs/configuring-playbook-ntfy.md:112 +msgid "Set the ntfy server's log level to 'DEBUG', as shown in the example settings above, and watch the server's logs with `sudo journalctl -fu matrix-ntfy`." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:157 -msgid "If it is not working, useful tools are \"Settings -> Notifications -> Re-register push distributor\" and \"Settings -> Notifications -> Troubleshoot Notifications\" in SchildiChat Android (possibly also Element Android). In particular the \"Endpoint/FCM\" step of that troubleshooter should display your ntfy server's URL that it has discovered from the ntfy client app." +#: ../../../docs/configuring-playbook-ntfy.md:114 +msgid "To check if UnifiedPush is correctly configured on the client device, look at \"Settings -> Notifications -> Notification Targets\" in Element Android or SchildiChat Android, or \"Settings -> Notifications -> Devices\" in FluffyChat. There should be one entry for each Matrix client app that has enabled push notifications, and when that client is using UnifiedPush you should see a URL that begins with your ntfy server's URL." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:116 +msgid "In the \"Notification Targets\" screen in Element Android or SchildiChat Android, two relevant URLs are shown, \"push\\_key\" and \"Url\", and both should begin with your ntfy server's URL. If \"push\\_key\" shows your server but \"Url\" shows an external server such as `up.schildi.chat` then push notifications will still work but are being routed through that external server before they reach your ntfy server. To rectify that, in SchildiChat (at least around version 1.4.20.sc55) you must enable the `Force custom push gateway` setting as described in the \"Usage\" section above." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:159 -msgid "Check the service's logs" +#: ../../../docs/configuring-playbook-ntfy.md:118 +msgid "If it is not working, useful tools are \"Settings -> Notifications -> Re-register push distributor\" and \"Settings -> Notifications -> Troubleshoot Notifications\" in SchildiChat Android (possibly also Element Android). In particular the \"Endpoint/FCM\" step of that troubleshooter should display your ntfy server's URL that it has discovered from the ntfy client app." msgstr "" -#: ../../../docs/configuring-playbook-ntfy.md:161 -msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/docs/configuring-ntfy.md#check-the-services-logs) on the role's documentation for details." +#: ../../../docs/configuring-playbook-ntfy.md:120 +msgid "The simple [UnifiedPush troubleshooting](https://unifiedpush.org/users/troubleshooting/) app [UP-Example](https://f-droid.org/en/packages/org.unifiedpush.example/) can be used to manually test UnifiedPush registration and operation on an Android device." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-own-webserver.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-own-webserver.po index 64489912a..1ed7a0be1 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-own-webserver.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-own-webserver.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,176 +18,176 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-own-webserver.md:19 +#: ../../../docs/configuring-playbook-own-webserver.md:1 msgid "Using your own webserver, instead of this playbook's Traefik reverse-proxy (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:21 +#: ../../../docs/configuring-playbook-own-webserver.md:3 msgid "By default, this playbook installs its own [Traefik](https://traefik.io/) reverse-proxy server (in a Docker container) which listens on ports 80 and 443. If that's okay, you can skip this document." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:23 +#: ../../../docs/configuring-playbook-own-webserver.md:5 msgid "Traefik" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:25 +#: ../../../docs/configuring-playbook-own-webserver.md:7 msgid "[Traefik](https://traefik.io/) is the default reverse-proxy for the playbook since [2023-02-26](../CHANGELOG.md/#2023-02-26) and serves **2 purposes**:" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:27 +#: ../../../docs/configuring-playbook-own-webserver.md:9 msgid "serving public traffic and providing SSL-termination with certificates obtained from [Let's Encrypt](https://letsencrypt.org/). See [Adjusting SSL certificate retrieval](./configuring-playbook-ssl-certificates.md)." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:29 -msgid "assists internal communication between addon services (bridges, bots, etc.) and the homeserver via an internal entrypoint (`matrix-internal-matrix-client-api`)." +#: ../../../docs/configuring-playbook-own-webserver.md:11 +msgid "assists internal communication between addon services (briges, bots, etc.) and the homeserver via an internal entrypoint (`matrix-internal-matrix-client-api`)." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:31 +#: ../../../docs/configuring-playbook-own-webserver.md:13 msgid "There are 2 ways to use Traefik with this playbook, as described below." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:33 +#: ../../../docs/configuring-playbook-own-webserver.md:15 msgid "Traefik managed by the playbook" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:35 +#: ../../../docs/configuring-playbook-own-webserver.md:17 msgid "To have the playbook install and use Traefik, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:41 +#: ../../../docs/configuring-playbook-own-webserver.md:25 msgid "Traefik will manage SSL certificates for all services seamlessly." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:43 +#: ../../../docs/configuring-playbook-own-webserver.md:27 msgid "Traefik managed by you" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:69 +#: ../../../docs/configuring-playbook-own-webserver.md:53 msgid "In this mode all roles will still have Traefik labels attached. You will, however, need to configure your Traefik instance and its entrypoints." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:71 +#: ../../../docs/configuring-playbook-own-webserver.md:55 msgid "By default, the playbook configured a `default` certificate resolver and multiple entrypoints." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:73 +#: ../../../docs/configuring-playbook-own-webserver.md:57 msgid "You need to configure 4 entrypoints for your Traefik server:" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:75 +#: ../../../docs/configuring-playbook-own-webserver.md:59 msgid "`web` (TCP port `80`) — used for redirecting to HTTPS (`web-secure`)" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:76 +#: ../../../docs/configuring-playbook-own-webserver.md:60 msgid "`web-secure` (TCP port `443`) — used for exposing the Matrix Client-Server API and all other services" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:77 +#: ../../../docs/configuring-playbook-own-webserver.md:61 msgid "`matrix-federation` (TCP port `8448`) — used for exposing the Matrix Federation API" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:78 +#: ../../../docs/configuring-playbook-own-webserver.md:62 msgid "`matrix-internal-matrix-client-api` (TCP port `8008`) — used internally for addon services (bridges, bots) to communicate with the homserver" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:80 +#: ../../../docs/configuring-playbook-own-webserver.md:64 msgid "Below is some configuration for running Traefik yourself, although we recommend using [Traefik managed by the playbook](#traefik-managed-by-the-playbook)." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:82 +#: ../../../docs/configuring-playbook-own-webserver.md:66 msgid "Note that this configuration on its own does **not** redirect traffic on port 80 (plain HTTP) to port 443 for HTTPS. If you are not already doing this in Traefik, it can be added to Traefik in a [file provider](https://docs.traefik.io/v2.0/providers/file/) as follows:" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:102 +#: ../../../docs/configuring-playbook-own-webserver.md:86 msgid "You can use the following `docker-compose.yml` as example to launch Traefik." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:138 +#: ../../../docs/configuring-playbook-own-webserver.md:122 msgid "Another webserver" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:140 +#: ../../../docs/configuring-playbook-own-webserver.md:124 msgid "If you don't wish to use Traefik, you can also use your own webserver." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:142 +#: ../../../docs/configuring-playbook-own-webserver.md:126 msgid "Doing this is possible, but requires manual work." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:144 +#: ../../../docs/configuring-playbook-own-webserver.md:128 msgid "There are 2 ways to go about it:" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:146 +#: ../../../docs/configuring-playbook-own-webserver.md:130 msgid "(recommended) [Fronting the integrated reverse-proxy webserver with another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) — using the playbook-managed reverse-proxy (Traefik), but disabling SSL termination for it, exposing this reverse-proxy on a few local ports (e.g. `127.0.0.1:81`, etc.) and forwarding traffic from your own webserver to those few ports" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:148 +#: ../../../docs/configuring-playbook-own-webserver.md:132 msgid "(difficult) [Using no reverse-proxy on the Matrix side at all](#using-no-reverse-proxy-on-the-matrix-side-at-all) disabling the playbook-managed reverse-proxy (Traefik), exposing services one by one using `_host_bind_port` variables and forwarding traffic from your own webserver to those ports" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:150 +#: ../../../docs/configuring-playbook-own-webserver.md:134 msgid "Fronting the integrated reverse-proxy webserver with another reverse-proxy" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:152 +#: ../../../docs/configuring-playbook-own-webserver.md:136 msgid "This method is about leaving the integrated reverse-proxy webserver be, but making it not get in the way (using up important ports, trying to retrieve SSL certificates, etc.)." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:154 +#: ../../../docs/configuring-playbook-own-webserver.md:138 msgid "If you wish to use another webserver, the integrated reverse-proxy webserver usually gets in the way because it attempts to fetch SSL certificates and binds to ports 80, 443 and 8448 (if Matrix Federation is enabled)." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:156 +#: ../../../docs/configuring-playbook-own-webserver.md:140 msgid "You can disable such behavior and make the integrated reverse-proxy webserver only serve traffic locally on the host itself (or over a local network)." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:158 +#: ../../../docs/configuring-playbook-own-webserver.md:142 msgid "This is the recommended way for using another reverse-proxy, because the integrated one would act as a black box and wire all Matrix services correctly. You would then only need to reverse-proxy a few individual domains and ports over to it." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:160 +#: ../../../docs/configuring-playbook-own-webserver.md:144 msgid "To front Traefik with another reverse-proxy, you would need some configuration like this:" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:210 +#: ../../../docs/configuring-playbook-own-webserver.md:194 msgid "Such a configuration would expose all services on a local port `81` and Matrix Federation on a local port `8449`. Your reverse-proxy configuration needs to send traffic to these ports. [`examples/reverse-proxies`](../examples/reverse-proxies/) contains examples for various webservers such as Apache2, Caddy, HAproxy, nginx and Nginx Proxy Manager." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:212 +#: ../../../docs/configuring-playbook-own-webserver.md:196 msgid "It's important that these webservers proxy-pass requests to the correct `ip:port` and also set the `Host` HTTP header appropriately. If you don't pass the `Host` header correctly, Traefik will return a `404 - not found` error." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:214 +#: ../../../docs/configuring-playbook-own-webserver.md:198 msgid "To put it another way:" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:215 +#: ../../../docs/configuring-playbook-own-webserver.md:199 msgid "`curl http://127.0.0.1:81` will result in a `404 - not found` error" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:216 +#: ../../../docs/configuring-playbook-own-webserver.md:200 msgid "but `curl -H 'Host: matrix.example.com' http://127.0.0.1:81` should work." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:218 +#: ../../../docs/configuring-playbook-own-webserver.md:202 msgid "Using no reverse-proxy on the Matrix side at all" msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:220 +#: ../../../docs/configuring-playbook-own-webserver.md:204 msgid "Instead of [Fronting the integrated reverse-proxy webserver with another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy), you can also go another way — completely disabling the playbook-managed Traefik reverse-proxy. You would then need to reverse-proxy from your own webserver directly to each individual Matrix service." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:222 +#: ../../../docs/configuring-playbook-own-webserver.md:206 msgid "This is more difficult, as you would need to handle the configuration for each service manually. Enabling additional services would come with extra manual work you need to do." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:224 +#: ../../../docs/configuring-playbook-own-webserver.md:208 msgid "Also, the Traefik reverse-proxy, besides fronting everything is also serving a 2nd purpose of allowing addons services to communicate with the Matrix homeserver thanks to its `matrix-internal-matrix-client-api` entrypoint (read more about it above). Disabling Traefik completely means the playbook would wire services to directly talk to the homeserver. This can work for basic setups, but not for more complex setups involving [matrix-media-repo](./configuring-playbook-matrix-media-repo.md), [matrix-corporal](./configuring-playbook-matrix-corporal.md) or other such services that need to \"steal routes\" from the homeserver." msgstr "" -#: ../../../docs/configuring-playbook-own-webserver.md:226 +#: ../../../docs/configuring-playbook-own-webserver.md:210 msgid "If your webserver is on the same machine, ensure your web server user (something like `http`, `apache`, `www-data`, `nginx`) is part of the `matrix` group. You should run something like this: `usermod -a -G matrix nginx`. This allows your webserver user to access files owned by the `matrix` group, so that it can serve static files from `/matrix/static-files`." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po index b22d6c482..b5aa2c366 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,28 +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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-postgres-backup.md:9 -msgid "Setting up Postgres backup (optional)" +#: ../../../docs/configuring-playbook-postgres-backup.md:1 +msgid "Setting up postgres backup (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:3 +msgid "The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you via the [ansible-role-postgres-backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup) Ansible role." msgstr "" -#: ../../../docs/configuring-playbook-postgres-backup.md:11 -msgid "The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you." +#: ../../../docs/configuring-playbook-postgres-backup.md:5 +msgid "For a more complete backup solution (one that includes not only Postgres, but also other configuration/data files), you may wish to look into [BorgBackup](configuring-playbook-backup-borg.md) instead." msgstr "" -#: ../../../docs/configuring-playbook-postgres-backup.md:13 -msgid "The [Ansible role for docker-postgres-backup-local](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring docker-postgres-backup-local, you can check them via:" +#: ../../../docs/configuring-playbook-postgres-backup.md:7 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-postgres-backup.md:14 -msgid "🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup/blob/main/docs/configuring-postgres-backup.md) online" +#: ../../../docs/configuring-playbook-postgres-backup.md:9 +msgid "To enable Postgres backup, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-postgres-backup.md:15 -msgid "📁 `roles/galaxy/postgres_backup/docs/configuring-postgres-backup.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" +msgid "Refer to the table below for additional configuration variables and their default values." +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Name" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Default value" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Description" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`false`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Set to true to use [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) to create automatic database backups" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_schedule`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`'@daily'`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Cron-schedule specifying the interval between postgres backups." +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_keep_days`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`7`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Number of daily backups to keep" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_keep_weeks`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`4`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Number of weekly backups to keep" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_keep_months`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`12`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Number of monthly backups to keep" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_base_path`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`\"{{ matrix_base_data_path }}/postgres-backup\"`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Base path for postgres-backup. Also see `postgres_backup_data_path`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_data_path`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`\"{{ postgres_backup_base_path }}/data\"`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Storage path for postgres-backup database backups" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:27 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:29 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:36 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-postgres-backup.md:17 -msgid "**Note**: for a more complete backup solution (one that includes not only Postgres, but also other configuration/data files), you may wish to look into [BorgBackup](configuring-playbook-backup-borg.md) instead." +#: ../../../docs/configuring-playbook-postgres-backup.md:38 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po index 67b5fd6e4..602410466 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,180 +18,126 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:14 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:1 msgid "Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server (optional)" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:16 -msgid "The playbook can install [Prometheus](https://prometheus.io/) with [Grafana](https://grafana.com/) and configure performance metrics of your homeserver with graphs for you." +#: ../../../docs/configuring-playbook-prometheus-grafana.md:3 +msgid "The playbook can install [Grafana](https://grafana.com/) with [Prometheus](https://prometheus.io/) and configure performance metrics of your homeserver with graphs for you." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:18 -msgid "[!WARNING] Metrics and graphs contain a lot of information, and anyone who has access to them can make an educated guess about your server usage patterns. This especially applies to small personal/family scale homeservers, where the number of samples is fairly limited. Analyzing the metrics over time, one might be able to figure out your life cycle, such as when you wake up, go to bed, etc. Before enabling (anonymous) access, you should carefully evaluate the risk, and if you do enable it, it is highly recommended to change your Grafana password from the default one." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:21 -msgid "Most of our Docker containers run with limited system access, but the `prometheus-node-exporter` can access the host network stack and (readonly) root filesystem. If it is fine, you can enable it and have it capture metrics about them (see [below](#enable-metrics-and-graphs-for-generic-system-information-optional) for the instruction). Even if `prometheus-node-exporter` is not enabled, you will still get Synapse homeserver metrics. Note that both of these dashboards are always be enabled, so you can still see historical data even after disabling either source." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:23 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:5 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:25 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:7 msgid "By default, this playbook installs Grafana web user-interface on the `stats.` subdomain (`stats.example.com`) and requires you to create a CNAME record for `stats`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:27 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:9 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:29 -msgid "**Note**: It is possible to install Prometheus without installing Grafana. In this case it is not required to create the CNAME record." +#: ../../../docs/configuring-playbook-prometheus-grafana.md:11 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:31 -msgid "Adjusting the playbook configuration — Prometheus" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:13 +msgid "To enable Grafana and/or Prometheus, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:33 -msgid "Prometheus is an open-source systems monitoring and alerting toolkit. It is a time series database, which holds all the data we're going to talk about." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:35 -msgid "To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:39 +msgid "The retention policy of Prometheus metrics is [15 days by default](https://prometheus.io/docs/prometheus/latest/storage/#operational-aspects). Older data gets deleted automatically." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:41 -msgid "**Note**: the retention policy of Prometheus metrics is [15 days by default](https://prometheus.io/docs/prometheus/latest/storage/#operational-aspects). Older data gets deleted automatically." +msgid "Adjusting the Grafana URL (optional)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:43 -msgid "Enable metrics and graphs for generic system information (optional)" +msgid "By tweaking the `grafana_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:45 -msgid "You can enable the [Node Exporter](https://prometheus.io/docs/guides/node-exporter/), an addon of sorts to Prometheus that collects generic system information such as CPU, memory, filesystem, and even system temperatures." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:47 -#: ../../../docs/configuring-playbook-prometheus-grafana.md:59 -#: ../../../docs/configuring-playbook-prometheus-grafana.md:83 -msgid "To enable it, add the following configuration to your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:53 -msgid "Enable metrics and graphs for Postgres (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:55 -msgid "Expanding on the metrics exposed by the Synapse exporter and the Node exporter, the playbook can also install and configure the [PostgreSQL Server Exporter](https://github.com/prometheus-community/postgres_exporter) that exposes more detailed information about what's happening on your Postgres database." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:57 -msgid "Enabling the exporter sets up the docker container, connects it to the database and adds a 'job' to the Prometheus config which tells Prometheus about this new exporter." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:61 -msgid "**Note**: `prometheus_postgres_exporter_database_username` has nothing to do with your Matrix user ID. It can be any string you'd like." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:75 -msgid "Enable metrics and graphs for nginx logs (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:77 -msgid "The playbook can also install and configure the [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) service for you." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:79 -msgid "It is an addon of sorts to expose nginx logs to Prometheus. The exporter will collect access logs from various nginx reverse-proxies which may be used internally (e.g. `matrix-synapse-reverse-proxy-companion`, if Synapse workers are enabled) and will make them available at a Prometheus-compatible `/metrics` endpoint." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:81 -msgid "See the project's [documentation](https://github.com/martin-helmich/prometheus-nginxlog-exporter/blob/master/README.adoc) to learn what it does and why it might be useful to you." +msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:89 -msgid "If you enable Grafana, a dedicated `NGINX PROXY` Grafana dashboard will be created." +#: ../../../docs/configuring-playbook-prometheus-grafana.md:52 +msgid "After changing the domain, **you may need to adjust your DNS** records to point the Grafana domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:91 -msgid "**Note**: nginx is only used internally by this Ansible playbook. With Traefik being our default reverse-proxy, collecting nginx metrics is less relevant." +#: ../../../docs/configuring-playbook-prometheus-grafana.md:54 +msgid "**Note**: It is possible to install Prometheus without installing Grafana. This case it is not required to create the CNAME record." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:93 -msgid "Docker image compatibility (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:95 -msgid "At the moment of writing only images for `amd64` and `arm64` architectures are available. The playbook currently does not support [self-building](./self-building.md) a container image on other architectures. You can however use a custom-build image by setting:" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:56 +msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:102 -msgid "Extending the configuration" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:58 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:104 -msgid "There are some additional things you may wish to configure about Prometheus and its add-on." +#: ../../../docs/configuring-playbook-prometheus-grafana.md:65 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:106 -msgid "Take a look at:" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:67 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:108 -msgid "[Prometheus role](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus/blob/main/defaults/main.yml) for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `prometheus_configuration_extension_yaml` variable" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:69 +msgid "What does it do?" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:109 -msgid "`roles/galaxy/prometheus_nginxlog_exporter/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Name" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:111 -msgid "Adjusting the playbook configuration — Grafana" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Description" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:113 -msgid "Grafana is an open source visualization and analytics software. To enable it, add the following configuration to your `vars.yml` file. Make sure to replace `USERNAME_HERE` and `PASSWORD_HERE`." +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`prometheus_enabled`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:115 -msgid "**Notes**:" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:116 -msgid "`grafana_default_admin_user` has nothing to do with your Matrix user ID. It can be any string you'd like." +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`prometheus_node_exporter_enabled`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:117 -msgid "Changing the username/password subsequently won't work." +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "[Node Exporter](https://prometheus.io/docs/guides/node-exporter/) is an addon of sorts to Prometheus that collects generic system information such as CPU, memory, filesystem, and even system temperatures" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Name" +msgid "`prometheus_postgres_exporter_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Description" +msgid "[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an addon of sorts to expose Postgres database metrics to Prometheus." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "`grafana_enabled`" +msgid "`matrix_prometheus_nginxlog_exporter_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "[Grafana](https://grafana.com/) is the visual component. It shows (on the `stats.example.com` subdomain) the dashboards with the graphs that we're interested in." +msgid "[NGINX Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose NGINX logs to Prometheus." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "`grafana_default_admin_user`
`grafana_default_admin_password`" +msgid "`grafana_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "By default Grafana creates a user with `admin` as the username and password. You are asked to change the credentials on first login. If you feel this is insecure and you want to change them beforehand, you can do that here." +msgid "[Grafana](https://grafana.com/) is the visual component. It shows (on the `stats.example.com` subdomain) the dashboards with the graphs that we're interested in" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md @@ -202,63 +148,47 @@ msgstr "" msgid "By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:135 -msgid "Adjusting the Grafana URL (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:137 -msgid "By tweaking the `grafana_hostname` variable, you can easily make the service available at a **different hostname** than the default one." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:139 -msgid "Example additional configuration for your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:146 -msgid "After changing the domain, **you may need to adjust your DNS** records to point the Grafana domain to the Matrix server." +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`grafana_default_admin_user`
`grafana_default_admin_password`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:148 -msgid "Installing" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "By default Grafana creates a user with `admin` as the username and password. If you feel this is insecure and you want to change it beforehand, you can do that here" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:150 -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:" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:81 +msgid "Security and privacy" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:157 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:83 +msgid "Metrics and resulting graphs can contain a lot of information. This includes system specs but also usage patterns. This applies especially to small personal/family scale homeservers. Someone might be able to figure out when you wake up and go to sleep by looking at the graphs over time. Think about this before enabling anonymous access. And you should really not forget to change your Grafana password." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:159 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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." +#: ../../../docs/configuring-playbook-prometheus-grafana.md:85 +msgid "Most of our docker containers run with limited system access, but the `prometheus-node-exporter` has access to the host network stack and (readonly) root filesystem. This is required to report on them. If you don't like that, you can set `prometheus_node_exporter_enabled: false` (which is actually the default). You will still get Synapse metrics with this container disabled. Both of the dashboards will always be enabled, so you can still look at historical data after disabling either source." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:161 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:87 msgid "Collecting metrics to an external Prometheus server" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:163 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:89 msgid "**If the integrated Prometheus server is enabled** (`prometheus_enabled: true`), metrics are collected by it from each service via communication that happens over the container network. Each service does not need to expose its metrics \"publicly\"." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:165 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:91 msgid "When you'd like **to collect metrics from an external Prometheus server**, you need to expose service metrics outside of the container network." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:167 -msgid "The playbook provides a single endpoint (`https://matrix.example.com/metrics/*`), under which various services may expose their metrics (e.g. `/metrics/node-exporter`, `/metrics/postgres-exporter`, `/metrics/nginxlog`, `/metrics/hookshot`, etc)." -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:169 -msgid "To expose all services on this `/metrics/*` feature, you can use `matrix_metrics_exposure_enabled`. When using it, you don't need to expose metrics for individual services one by one. If you think this is too much, refer [this section](#expose-metrics-of-other-services-roles) for details about exposing metrics on a per-service basis." +#: ../../../docs/configuring-playbook-prometheus-grafana.md:93 +msgid "The playbook provides a single endpoint (`https://matrix.example.com/metrics/*`), under which various services may expose their metrics (e.g. `/metrics/node-exporter`, `/metrics/postgres-exporter`, `/metrics/hookshot`, etc). To expose all services on this `/metrics/*` feature, use `matrix_metrics_exposure_enabled`. To protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication), see `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users` below." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:171 -msgid "To protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication), you can use `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`. When enabled, all endpoints beneath `/metrics` will be protected with the same credentials. Alternatively, you can protect each endpoint with dedicated credentials. Refer [the section](#expose-metrics-of-other-services-roles) below for details about it." +#: ../../../docs/configuring-playbook-prometheus-grafana.md:95 +msgid "When using `matrix_metrics_exposure_enabled`, you don't need to expose metrics for individual services one by one." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:173 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:97 msgid "The following variables may be of interest:" msgstr "" @@ -267,7 +197,7 @@ msgid "`matrix_metrics_exposure_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Set this to `true` to **enable metrics exposure for all services** on `https://matrix.example.com/metrics/*`." +msgid "Set this to `true` to **enable metrics exposure for all services** on `https://matrix.example.com/metrics/*`. If you think this is too much, refer to the helpful (but nonexhaustive) list of individual `matrix_SERVICE_metrics_proxying_enabled` (or similar) variables below for exposing metrics on a per-service basis." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md @@ -275,7 +205,7 @@ msgid "`matrix_metrics_exposure_http_basic_auth_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Set this to `true` to protect all `https://matrix.example.com/metrics/*` endpoints with [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) (see the other variables below for supplying the actual credentials)." +msgid "Set this to `true` to protect all `https://matrix.example.com/metrics/*` endpoints with [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) (see the other variables below for supplying the actual credentials). When enabled, all endpoints beneath `/metrics` will be protected with the same credentials" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md @@ -287,137 +217,129 @@ msgid "Set this to the Basic Authentication credentials (raw `htpasswd` file con msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "`prometheus_node_exporter_enabled`" +msgid "`matrix_synapse_metrics_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Set this to `true` to enable the node (general system stats) exporter (locally, on the container network)." +msgid "Set this to `true` to make Synapse expose metrics (locally, on the container network)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "`prometheus_node_exporter_container_labels_metrics_enabled`" +msgid "`matrix_synapse_metrics_proxying_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Set this to `true` to expose the node (general system stats) metrics on `https://matrix.example.com/metrics/node-exporter`." +msgid "Set this to `true` to expose Synapse's metrics on `https://matrix.example.com/metrics/synapse/main-process` and `https://matrix.example.com/metrics/synapse/worker/TYPE-ID`. Read [below](#collecting-synapse-worker-metrics-to-an-external-prometheus-server) if you're running a Synapse worker setup (`matrix_synapse_workers_enabled: true`). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "`prometheus_postgres_exporter_enabled`" +msgid "Set this to `true` to enable the node (general system stats) exporter (locally, on the container network)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Set this to `true` to enable the [Postgres exporter](#enable-metrics-and-graphs-for-postgres-optional) (locally, on the container network)." +msgid "`prometheus_node_exporter_container_labels_traefik_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "`prometheus_postgres_exporter_container_labels_metrics_enabled`" +msgid "Set this to `true` to expose the node (general system stats) metrics on `https://matrix.example.com/metrics/node-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Set this to `true` to expose the [Postgres exporter](#enable-metrics-and-graphs-for-postgres-optional) metrics on `https://matrix.example.com/metrics/postgres-exporter`." +msgid "Set this to `true` to enable the [Postgres exporter](configuring-playbook-prometheus-postgres.md) (locally, on the container network)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "`prometheus_nginxlog_exporter_enabled`" +msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Set this to `true` to enable the [prometheus-nginxlog-exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) (locally, on the container network)." +msgid "Set this to `true` to expose the [Postgres exporter](configuring-playbook-prometheus-postgres.md) metrics on `https://matrix.example.com/metrics/postgres-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "`prometheus_nginxlog_exporter_container_labels_metrics_enabled`" +msgid "Set this to `true` to enable the [NGINX Log exporter](configuring-playbook-prometheus-nginxlog.md) (locally, on the container network)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "Set this to `true` to expose the [prometheus-nginxlog-exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) metrics on `https://matrix.example.com/metrics/nginxlog`." +msgid "`matrix_sliding_sync_metrics_enabled`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:187 -msgid "Expose metrics of other services/roles" -msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:189 -msgid "Various other services/roles may provide similar `_metrics_enabled` and `_metrics_proxying_enabled` variables for exposing their metrics. Refer to each role for details." +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) expose metrics (locally, on the container network)" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:191 -msgid "To password-protect the metrics of a specific role, you can use `matrix_SERVICE_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_SERVICE_container_labels_metrics_middleware_basic_auth_users` variables provided by the role." +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_sliding_sync_metrics_proxying_enabled`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:193 -msgid "**Note**: alternatively you can use `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users` in order to password-protect the metrics of all services." +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Set this to `true` to expose the [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) metrics on `https://matrix.example.com/metrics/sliding-sync`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:195 -msgid "For example, you can enable and expose metrics for Synapse protecting them with dedicated credentials by adding the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_bridge_hookshot_metrics_enabled`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:213 -msgid "Collecting Synapse worker metrics to an external Prometheus server" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Set this to `true` to make [Hookshot](configuring-playbook-bridge-hookshot.md) expose metrics (locally, on the container network)" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:215 -msgid "If you are using workers (`matrix_synapse_workers_enabled: true`) and have enabled `matrix_synapse_metrics_proxying_enabled` as described above, the playbook will also automatically expose all Synapse worker threads' metrics to `https://matrix.example.com/metrics/synapse/worker/ID`, where `ID` corresponds to the worker `id` as exemplified in `matrix_synapse_workers_enabled_list`." +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_bridge_hookshot_metrics_proxying_enabled`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:217 -msgid "The playbook also generates an exemplary config file (`/matrix/synapse/external_prometheus.yml.template`) with all the correct paths which you can copy to your Prometheus server and adapt to your needs. Make sure to edit the specified `password_file` path and contents and path to your `synapse-v2.rules`. It will look a bit like this:" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Set this to `true` to expose the [Hookshot](configuring-playbook-bridge-hookshot.md) metrics on `https://matrix.example.com/metrics/hookshot`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:245 -msgid "Troubleshooting" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_SERVICE_metrics_proxying_enabled`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:247 -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 the commands below:" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Various other services/roles may provide similar `_metrics_enabled` and `_metrics_proxying_enabled` variables for exposing their metrics. Refer to each role for details. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above or `matrix_SERVICE_container_labels_metrics_middleware_basic_auth_enabled`/`matrix_SERVICE_container_labels_metrics_middleware_basic_auth_users` variables provided by each role." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:248 -msgid "`journalctl -fu matrix-prometheus` for Prometheus" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_media_repo_metrics_enabled`" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:249 -msgid "`journalctl -fu matrix-prometheus-node-exporter` for Node Exporter" +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Set this to `true` to make media-repo expose metrics (locally, on the container network)" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:250 -msgid "`journalctl -fu matrix-prometheus-postgres-exporter` for PostgreSQL Server Exporter" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:118 +msgid "Collecting Synapse worker metrics to an external Prometheus server" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:251 -msgid "`journalctl -fu matrix-prometheus-nginxlog-exporter` for prometheus-nginxlog-exporter" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:120 +msgid "If you are using workers (`matrix_synapse_workers_enabled: true`) and have enabled `matrix_synapse_metrics_proxying_enabled` as described above, the playbook will also automatically expose all Synapse worker threads' metrics to `https://matrix.example.com/metrics/synapse/worker/ID`, where `ID` corresponds to the worker `id` as exemplified in `matrix_synapse_workers_enabled_list`." msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:252 -msgid "`journalctl -fu matrix-grafana` for Grafana" +#: ../../../docs/configuring-playbook-prometheus-grafana.md:122 +msgid "The playbook also generates an exemplary config file (`/matrix/synapse/external_prometheus.yml.template`) with all the correct paths which you can copy to your Prometheus server and adapt to your needs. Make sure to edit the specified `password_file` path and contents and path to your `synapse-v2.rules`. It will look a bit like this:" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:254 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:150 msgid "More information" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:256 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:152 msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:257 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:153 msgid "[Understanding Synapse Performance Issues Through Grafana Graphs](https://element-hq.github.io/synapse/latest/usage/administration/understanding_synapse_through_grafana_graphs.html) at the Synapse Github Wiki" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:258 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:154 msgid "[The Prometheus scraping rules](https://github.com/element-hq/synapse/tree/master/contrib/prometheus) (we use v2)" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:259 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:155 msgid "[The Synapse Grafana dashboard](https://github.com/element-hq/synapse/tree/master/contrib/grafana)" msgstr "" -#: ../../../docs/configuring-playbook-prometheus-grafana.md:260 +#: ../../../docs/configuring-playbook-prometheus-grafana.md:156 msgid "[The Node Exporter dashboard](https://github.com/rfrail3/grafana-dashboards) (for generic non-synapse performance graphs)" msgstr "" - -#: ../../../docs/configuring-playbook-prometheus-grafana.md:261 -msgid "[The PostgreSQL dashboard](https://grafana.com/grafana/dashboards/9628) (generic Postgres dashboard)" -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rageshake.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rageshake.po index b58fd7e9f..e3c4f49f6 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rageshake.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rageshake.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,112 +18,92 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-rageshake.md:8 +#: ../../../docs/configuring-playbook-rageshake.md:1 msgid "Setting up the rageshake bug report server (optional)" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:10 +#: ../../../docs/configuring-playbook-rageshake.md:3 msgid "The playbook can install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server for you." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:12 +#: ../../../docs/configuring-playbook-rageshake.md:5 msgid "See the project's [documentation](https://github.com/matrix-org/rageshake/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:14 +#: ../../../docs/configuring-playbook-rageshake.md:7 msgid "**Note**: most people don't need to install rageshake to collect bug reports. This component is only useful to people who develop/build their own Matrix client applications themselves." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:16 +#: ../../../docs/configuring-playbook-rageshake.md:9 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:18 +#: ../../../docs/configuring-playbook-rageshake.md:11 msgid "By default, this playbook installs rageshake on the `rageshake.` subdomain (`rageshake.example.com`) and requires you to create a CNAME record for `rageshake`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:20 +#: ../../../docs/configuring-playbook-rageshake.md:13 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:22 +#: ../../../docs/configuring-playbook-rageshake.md:15 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:24 +#: ../../../docs/configuring-playbook-rageshake.md:17 msgid "To enable rageshake, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:30 +#: ../../../docs/configuring-playbook-rageshake.md:23 +msgid "rageshake has various options which don't have dedicated Ansible variables. You can see the full list of options in the [`rageshake.sample.yaml` file](https://github.com/matrix-org/rageshake/blob/master/rageshake.sample.yaml)." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:25 +msgid "To set these, you can make use of the `matrix_rageshake_configuration_extension_yaml` variable like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:35 msgid "Adjusting the rageshake URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:32 +#: ../../../docs/configuring-playbook-rageshake.md:37 msgid "By tweaking the `matrix_rageshake_hostname` and `matrix_rageshake_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:34 +#: ../../../docs/configuring-playbook-rageshake.md:39 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:45 +#: ../../../docs/configuring-playbook-rageshake.md:50 msgid "After changing the domain, **you may need to adjust your DNS** records to point the rageshake domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:47 +#: ../../../docs/configuring-playbook-rageshake.md:52 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:49 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-rageshake.md:51 -msgid "There are some additional things you may wish to configure about the server." -msgstr "" - -#: ../../../docs/configuring-playbook-rageshake.md:53 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-rageshake.md:55 -msgid "`roles/custom/matrix-rageshake/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-rageshake.md:56 -msgid "`roles/custom/matrix-rageshake/templates/config.yaml.j2` for the server's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_rageshake_configuration_extension_yaml` variable" -msgstr "" - -#: ../../../docs/configuring-playbook-rageshake.md:74 +#: ../../../docs/configuring-playbook-rageshake.md:54 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:76 +#: ../../../docs/configuring-playbook-rageshake.md:56 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:83 +#: ../../../docs/configuring-playbook-rageshake.md:63 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:85 +#: ../../../docs/configuring-playbook-rageshake.md:65 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:87 +#: ../../../docs/configuring-playbook-rageshake.md:67 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-rageshake.md:89 +#: ../../../docs/configuring-playbook-rageshake.md:69 msgid "Refer to the project's [documentation](https://github.com/matrix-org/rageshake/blob/main/README.md) for available APIs, etc." msgstr "" - -#: ../../../docs/configuring-playbook-rageshake.md:91 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-rageshake.md:93 -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-rageshake`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rest-auth.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rest-auth.po index de4b4a311..770a8ef1c 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rest-auth.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rest-auth.po @@ -10,7 +10,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: 2024-12-20 09:53+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,56 +18,48 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-rest-auth.md:9 +#: ../../../docs/configuring-playbook-rest-auth.md:1 msgid "Setting up the REST authentication password provider module (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:11 +#: ../../../docs/configuring-playbook-rest-auth.md:3 msgid "The playbook can install and configure [matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) for you." msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:13 +#: ../../../docs/configuring-playbook-rest-auth.md:5 msgid "See the project's [documentation](https://github.com/ma1uta/matrix-synapse-rest-password-provider/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:15 +#: ../../../docs/configuring-playbook-rest-auth.md:7 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:17 +#: ../../../docs/configuring-playbook-rest-auth.md:9 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:27 +#: ../../../docs/configuring-playbook-rest-auth.md:19 msgid "Authenticating only using a password provider" msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:29 -msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, you can disable it by adding the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-rest-auth.md:21 +msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:" msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:35 +#: ../../../docs/configuring-playbook-rest-auth.md:27 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:37 +#: ../../../docs/configuring-playbook-rest-auth.md:29 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:44 +#: ../../../docs/configuring-playbook-rest-auth.md:36 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-rest-auth.md:46 +#: ../../../docs/configuring-playbook-rest-auth.md:38 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-rest-auth.md:48 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-rest-auth.md:50 -msgid "This module does not provide direct integration with any backend. Please prepare one by yourself for it." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po index 786c446e8..17fd21dbe 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,177 +18,165 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-s3-goofys.md:8 -msgid "Storing Synapse media files on Amazon S3 with Goofys (optional)" +#: ../../../docs/configuring-playbook-s3-goofys.md:1 +msgid "Storing Matrix media files on Amazon S3 with Goofys (optional)" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:10 -msgid "The playbook can install and configure [Goofys](https://github.com/kahing/goofys) for you." +#: ../../../docs/configuring-playbook-s3-goofys.md:3 +msgid "If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service), you can let this playbook configure [Goofys](https://github.com/kahing/goofys) for you." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:12 -msgid "Goofys makes it possible to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service) object storage." +#: ../../../docs/configuring-playbook-s3-goofys.md:5 +msgid "Another (and better performing) way to use S3 storage with Synapse is [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md)." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:14 -msgid "See the project's [documentation](https://github.com/kahing/goofys/blob/master/README.md) to learn what it does and why it might be useful to you." +#: ../../../docs/configuring-playbook-s3-goofys.md:7 +msgid "Using a Goofys-backed media store works, but performance may not be ideal. If possible, try to use a region which is close to your Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:16 -msgid "**Note**: as performance of a Goofys-backed media store may not be ideal, you may wish to use [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) instead, another (and better performing) way to mount a S3 bucket for Synapse." +#: ../../../docs/configuring-playbook-s3-goofys.md:9 +msgid "If you'd like to move your locally-stored media store data to Amazon S3 (or another S3-compatible object store), we also provide some migration instructions below." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:18 -msgid "If you'd like to move your locally-stored media store data to Amazon S3 (or another S3-compatible object store), you can refer our migration instructions below." -msgstr "" - -#: ../../../docs/configuring-playbook-s3-goofys.md:20 +#: ../../../docs/configuring-playbook-s3-goofys.md:11 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:22 +#: ../../../docs/configuring-playbook-s3-goofys.md:13 msgid "After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:32 +#: ../../../docs/configuring-playbook-s3-goofys.md:23 msgid "You can use any S3-compatible object store by **additionally** configuring these variables:" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:39 +#: ../../../docs/configuring-playbook-s3-goofys.md:30 msgid "If you have local media store files and wish to migrate to Backblaze B2 subsequently, follow our [migration guide to Backblaze B2](#migrating-to-backblaze-b2) below instead of applying this configuration as-is." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:41 +#: ../../../docs/configuring-playbook-s3-goofys.md:32 msgid "Migrating from local filesystem storage to S3" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:43 +#: ../../../docs/configuring-playbook-s3-goofys.md:34 msgid "It's a good idea to [make a complete server backup](faq.md#how-do-i-back-up-the-data-on-my-server) before migrating your local media store to an S3-backed one." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:45 +#: ../../../docs/configuring-playbook-s3-goofys.md:36 msgid "After making the backup, follow one of the guides below for a migration path from a locally-stored media store to one stored on S3-compatible storage:" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:47 +#: ../../../docs/configuring-playbook-s3-goofys.md:38 msgid "[Migrating to any S3-compatible storage (universal, but likely slow)](#migrating-to-any-s3-compatible-storage-universal-but-likely-slow)" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:48 +#: ../../../docs/configuring-playbook-s3-goofys.md:39 msgid "[Migrating to Backblaze B2](#migrating-to-backblaze-b2)" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:50 +#: ../../../docs/configuring-playbook-s3-goofys.md:41 msgid "Migrating to any S3-compatible storage (universal, but likely slow)" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:52 +#: ../../../docs/configuring-playbook-s3-goofys.md:43 msgid "Proceed with the steps below without stopping Matrix services" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:54 +#: ../../../docs/configuring-playbook-s3-goofys.md:45 msgid "Start by adding the base S3 configuration in your `vars.yml` file (seen above, may be different depending on the S3 provider of your choice)" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:56 +#: ../../../docs/configuring-playbook-s3-goofys.md:47 msgid "In addition to the base configuration you see above, add this to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:62 +#: ../../../docs/configuring-playbook-s3-goofys.md:53 msgid "This enables S3 support, but mounts the S3 storage bucket to `/matrix/s3-media-store` without hooking it to your homeserver yet. Your homeserver will still continue using your local filesystem for its media store." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:64 +#: ../../../docs/configuring-playbook-s3-goofys.md:55 msgid "Run the playbook to apply the changes: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:66 +#: ../../../docs/configuring-playbook-s3-goofys.md:57 msgid "Do an **initial sync of your files** by running this **on the server** (it may take a very long time):" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:72 +#: ../../../docs/configuring-playbook-s3-goofys.md:63 msgid "You may need to install `rsync` manually." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:74 -#: ../../../docs/configuring-playbook-s3-goofys.md:115 +#: ../../../docs/configuring-playbook-s3-goofys.md:65 +#: ../../../docs/configuring-playbook-s3-goofys.md:106 msgid "Stop all Matrix services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:76 +#: ../../../docs/configuring-playbook-s3-goofys.md:67 msgid "Start the S3 service by running this **on the server**: `systemctl start matrix-goofys`" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:78 +#: ../../../docs/configuring-playbook-s3-goofys.md:69 msgid "Sync the files again by re-running the `rsync` command you see in step #5" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:80 +#: ../../../docs/configuring-playbook-s3-goofys.md:71 msgid "Stop the S3 service by running this **on the server**: `systemctl stop matrix-goofys`" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:82 -#: ../../../docs/configuring-playbook-s3-goofys.md:123 +#: ../../../docs/configuring-playbook-s3-goofys.md:73 +#: ../../../docs/configuring-playbook-s3-goofys.md:114 msgid "Get the old media store out of the way by running this command on the server:" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:88 +#: ../../../docs/configuring-playbook-s3-goofys.md:79 msgid "Remove the `matrix_s3_media_store_path` configuration from your `vars.yml` file (undoing step #3 above)" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:90 -#: ../../../docs/configuring-playbook-s3-goofys.md:131 +#: ../../../docs/configuring-playbook-s3-goofys.md:81 +#: ../../../docs/configuring-playbook-s3-goofys.md:122 msgid "Run the playbook: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:92 -#: ../../../docs/configuring-playbook-s3-goofys.md:133 +#: ../../../docs/configuring-playbook-s3-goofys.md:83 +#: ../../../docs/configuring-playbook-s3-goofys.md:124 msgid "You're done! Verify that loading existing (old) media files works and that you can upload new ones." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:94 -#: ../../../docs/configuring-playbook-s3-goofys.md:135 +#: ../../../docs/configuring-playbook-s3-goofys.md:85 +#: ../../../docs/configuring-playbook-s3-goofys.md:126 msgid "When confident that it all works, get rid of the local media store directory: `rm -rf /matrix/synapse/storage/media-store-local-backup`" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:96 +#: ../../../docs/configuring-playbook-s3-goofys.md:87 msgid "Migrating to Backblaze B2" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:98 +#: ../../../docs/configuring-playbook-s3-goofys.md:89 msgid "While all Matrix services are running, run the following command on the server:" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:100 +#: ../../../docs/configuring-playbook-s3-goofys.md:91 msgid "(you need to adjust the 3 `--env` line below with your own data)" msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:113 +#: ../../../docs/configuring-playbook-s3-goofys.md:104 msgid "This is some initial file sync, which may take a very long time." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:117 +#: ../../../docs/configuring-playbook-s3-goofys.md:108 msgid "Run the command from step #1 again." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:119 +#: ../../../docs/configuring-playbook-s3-goofys.md:110 msgid "Doing this will sync any new files that may have been created locally in the meantime." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:121 +#: ../../../docs/configuring-playbook-s3-goofys.md:112 msgid "Now that Matrix services aren't running, we're sure to get Backblaze B2 and your local media store fully in sync." msgstr "" -#: ../../../docs/configuring-playbook-s3-goofys.md:129 +#: ../../../docs/configuring-playbook-s3-goofys.md:120 msgid "Put the [Backblaze B2 settings](configuring-playbook-s3.md#backblaze-b2) in your `vars.yml` file" msgstr "" - -#: ../../../docs/configuring-playbook-s3-goofys.md:137 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-s3-goofys.md:139 -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-goofys`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3.po index 18451448f..cb165f737 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,196 +18,200 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-s3.md:9 +#: ../../../docs/configuring-playbook-s3.md:1 msgid "Storing Synapse media files on Amazon S3 or another compatible Object Storage (optional)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:11 +#: ../../../docs/configuring-playbook-s3.md:3 msgid "By default, this playbook configures your server to store Synapse's content repository (`media_store`) files on the local filesystem. If that's okay, you can skip this document." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:13 +#: ../../../docs/configuring-playbook-s3.md:5 msgid "As an alternative to storing media files on the local filesystem, you can store them on [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object store." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:15 +#: ../../../docs/configuring-playbook-s3.md:7 msgid "You can do this either by sticking to Synapse's media repository and making that use S3 (read below for this method), or by switching to an external media storage implementation like [matrix-media-repo](configuring-playbook-matrix-media-repo.md)." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:17 +#: ../../../docs/configuring-playbook-s3.md:9 msgid "First, [choose an Object Storage provider](#choosing-an-object-storage-provider)." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:19 +#: ../../../docs/configuring-playbook-s3.md:11 msgid "Then, [create the S3 bucket](#bucket-creation-and-security-configuration)." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:21 +#: ../../../docs/configuring-playbook-s3.md:13 msgid "Finally, [set up S3 storage for Synapse](#setting-up) (with [Goofys](configuring-playbook-s3-goofys.md), [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md), or use s3 datastore with the [matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/configuration/s3-datastore.html))." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:23 +#: ../../../docs/configuring-playbook-s3.md:15 msgid "Choosing an Object Storage provider" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:25 -msgid "You can create [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object storage like [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html), [Wasabi](https://wasabi.com), [Digital Ocean Spaces](https://www.digitalocean.com/products/spaces), [Storj](https://storj.io), etc." +#: ../../../docs/configuring-playbook-s3.md:17 +msgid "You can create [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object storage like [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html), [Storj](https://storj.io), [Wasabi](https://wasabi.com), [Digital Ocean Spaces](https://www.digitalocean.com/products/spaces), etc." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:27 -msgid "Amazon S3 and Backblaze B2 are pay-as-you with no minimum charges for storing too little data. Note that Backblaze egress is free, but for only certain users for up to 3x the amount of data stored. Beyond that you will pay $0.01/GB of egress." +#: ../../../docs/configuring-playbook-s3.md:19 +msgid "Amazon S3, Backblaze B2, and Storj are pay-as-you with no minimum charges for storing too little data." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:29 -msgid "Wasabi has a minimum charge of 1TB if you're storing less than 1TB, which becomes expensive if you need to store less data than that. Likewise, Digital Ocean Spaces has also a minimum charge of 250GB ($5/month as of 2022-10). Though Storj does not set minimum amount of data to be stored, it also charges $5 minimum monthly usage fee since July 1, 2025, if your monthly usage (storage, bandwidth, and segments) totals less than $5." +#: ../../../docs/configuring-playbook-s3.md:21 +msgid "All these providers have different prices, with Storj appearing to be the cheapest (as of 2024-10, storage fee is $0.004 per GB/month, and egress fee is $0.007 per GB). Backblaze egress is free, but for only certain users for up to 3x the amount of data stored. Beyond that you will pay $0.01/GB of egress." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:31 +#: ../../../docs/configuring-playbook-s3.md:23 +msgid "Wasabi has a minimum charge of 1TB if you're storing less than 1TB, which becomes expensive if you need to store less data than that. Likewise, Digital Ocean Spaces has also a minimum charge of 250GB ($5/month as of 2022-10)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:25 msgid "Here are some of the important aspects of choosing the right provider:" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:33 +#: ../../../docs/configuring-playbook-s3.md:27 msgid "if a provider is a company you like and trust (or dislike less than the others)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:34 +#: ../../../docs/configuring-playbook-s3.md:28 msgid "if a provider implements end-to-end encryption of your data" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:35 +#: ../../../docs/configuring-playbook-s3.md:29 msgid "if a provider has a data region close to your Matrix server (if it's farther away, high latency may cause slowdowns)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:36 +#: ../../../docs/configuring-playbook-s3.md:30 msgid "if a provider's infrastructure such as data center is centralized or distributed" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:37 +#: ../../../docs/configuring-playbook-s3.md:31 msgid "if a provider's price model is transparent (whether it includes hidden costs like minimum charge, minimum storage term, etc.)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:38 +#: ../../../docs/configuring-playbook-s3.md:32 msgid "if a provider has free or cheap egress fee (in case you need to get the data out often, for some reason) — likely not too important for the common use-case" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:40 +#: ../../../docs/configuring-playbook-s3.md:34 msgid "Bucket creation and Security Configuration" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:42 +#: ../../../docs/configuring-playbook-s3.md:36 msgid "Now that you've [chosen an Object Storage provider](#choosing-an-object-storage-provider), you need to create a storage bucket." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:44 +#: ../../../docs/configuring-playbook-s3.md:38 msgid "How you do this varies from provider to provider, with Amazon S3 being the most complicated due to its vast number of services and complicated security policies." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:46 +#: ../../../docs/configuring-playbook-s3.md:40 msgid "Below, we provider some guides for common providers. If you don't see yours, look at the others for inspiration or read some guides online about how to create a bucket. Feel free to contribute to this documentation with an update!" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:48 +#: ../../../docs/configuring-playbook-s3.md:42 msgid "Amazon S3" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:50 +#: ../../../docs/configuring-playbook-s3.md:44 msgid "You'll need an Amazon S3 bucket and some IAM user credentials (access key + secret key) with full write access to the bucket. Example IAM security policy:" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:71 +#: ../../../docs/configuring-playbook-s3.md:65 msgid "**Note**: This policy needs to be attached to an IAM user created from the **Security Credentials** menu. This is not a **Bucket Policy**." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:73 +#: ../../../docs/configuring-playbook-s3.md:67 msgid "Backblaze B2" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:75 +#: ../../../docs/configuring-playbook-s3.md:69 msgid "To use [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html) you first need to sign up." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:77 +#: ../../../docs/configuring-playbook-s3.md:71 msgid "You [can't easily change which region (US, Europe) your Backblaze account stores files in](https://old.reddit.com/r/backblaze/comments/hi1v90/make_the_choice_for_the_b2_data_center_region/), so make sure to carefully choose the region when signing up (hint: it's a hard to see dropdown below the username/password fields in the signup form)." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:79 +#: ../../../docs/configuring-playbook-s3.md:73 msgid "After logging in to Backblaze:" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:81 +#: ../../../docs/configuring-playbook-s3.md:75 msgid "create a new **private** bucket through its user interface (you can call it something like `matrix-example-media-store`)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:82 +#: ../../../docs/configuring-playbook-s3.md:76 msgid "note the **Endpoint** for your bucket (something like `s3.us-west-002.backblazeb2.com`)." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:83 +#: ../../../docs/configuring-playbook-s3.md:77 msgid "adjust its Lifecycle Rules to: Keep only the last version of the file" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:84 +#: ../../../docs/configuring-playbook-s3.md:78 msgid "go to [App Keys](https://secure.backblaze.com/app_keys.htm) and use the **Add a New Application Key** to create a new one" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:85 +#: ../../../docs/configuring-playbook-s3.md:79 msgid "restrict it to the previously created bucket (e.g. `matrix-example-media-store`)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:86 +#: ../../../docs/configuring-playbook-s3.md:80 msgid "give it *Read & Write* access" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:88 +#: ../../../docs/configuring-playbook-s3.md:82 msgid "The `keyID` value is your **Access Key** and `applicationKey` is your **Secret Key**." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:90 +#: ../../../docs/configuring-playbook-s3.md:84 msgid "For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3-synapse-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) you will need:" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:92 +#: ../../../docs/configuring-playbook-s3.md:86 msgid "**Endpoint URL** — this is the **Endpoint** value you saw above, but prefixed with `https://`" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:93 +#: ../../../docs/configuring-playbook-s3.md:88 msgid "**Region** — use the value you see in the Endpoint (e.g. `us-west-002`)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:94 +#: ../../../docs/configuring-playbook-s3.md:90 msgid "**Storage Class** — use `STANDARD`. Backblaze B2 does not have different storage classes, so it doesn't make sense to use any other value." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:96 +#: ../../../docs/configuring-playbook-s3.md:92 msgid "Other providers" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:98 -msgid "For other S3-compatible providers, you most likely just need to create an S3 bucket and get some credentials (access key and secret key) for accessing the bucket in a read/write manner. You may not need to configure security policies, etc." +#: ../../../docs/configuring-playbook-s3.md:94 +msgid "For other S3-compatible providers, you may not need to configure security policies, etc. (just like for [Backblaze B2](#backblaze-b2))." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:100 -msgid "For details about setting up a bucket at Storj, please see the instruction [here](https://storj.dev/dcs/getting-started) to get started." +#: ../../../docs/configuring-playbook-s3.md:96 +msgid "You most likely just need to create an S3 bucket and get some credentials (access key and secret key) for accessing the bucket in a read/write manner." msgstr "" -#: ../../../docs/configuring-playbook-s3.md:102 +#: ../../../docs/configuring-playbook-s3.md:98 msgid "Setting up" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:104 +#: ../../../docs/configuring-playbook-s3.md:100 msgid "To set up Synapse to store files in S3, follow the instructions for the method of your choice:" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:106 +#: ../../../docs/configuring-playbook-s3.md:102 msgid "using [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) (recommended)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:107 +#: ../../../docs/configuring-playbook-s3.md:103 msgid "using [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)" msgstr "" -#: ../../../docs/configuring-playbook-s3.md:108 +#: ../../../docs/configuring-playbook-s3.md:104 msgid "using [matrix-media-repo](configuring-playbook-matrix-media-repo.md)" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po index 8a3a28aff..05095e33e 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po @@ -10,7 +10,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: 2024-12-20 09:53+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,48 +18,48 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:9 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:1 msgid "Setting up the Shared Secret Auth password provider module (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:11 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:3 msgid "The playbook can install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you." msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:13 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:5 msgid "See the project's [documentation](https://github.com/devture/matrix-synapse-shared-secret-auth/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:15 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:7 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:17 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:9 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:26 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:18 msgid "Authenticating only using a password provider" msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:28 -msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, you can disable it by adding the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-shared-secret-auth.md:20 +msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:" msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:34 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:26 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:36 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:28 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:43 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:35 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-shared-secret-auth.md:45 +#: ../../../docs/configuring-playbook-shared-secret-auth.md:37 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po index 459d4a79e..b78bbaae1 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,20 +18,100 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:18 -msgid "Setting up the Sliding Sync proxy (optional, removed)" +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:1 +msgid "Setting up the Sliding Sync proxy (optional)" msgstr "" -#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:20 -msgid "🪦 The playbook used to be able to install and configure the [sliding-sync](https://github.com/matrix-org/sliding-sync) proxy, but no longer includes this component, as it's been replaced with a different method (called Simplified Sliding Sync) integrated to newer homeservers by default (**Conduit** homeserver from version `0.6.0` or **Synapse** from version `1.114`)." +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:3 +msgid "**Note**: The sliding-sync proxy is **not required** anymore as it's been replaced with a different method (called Simplified Sliding Sync) which is integrated into newer homeservers by default (**Conduit** homeserver from version `0.6.0` or **Synapse** from version `1.114`). This component and documentation remain here for historical purposes, but **installing this old sliding-sync proxy is generally not recommended anymore**." msgstr "" -#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:22 -msgid "Uninstalling the proxy manually" +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:5 +msgid "The playbook can install and configure [sliding-sync](https://github.com/matrix-org/sliding-sync) proxy for you." msgstr "" -#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:24 -msgid "If you still have the Sliding Sync proxy 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:" +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:7 +msgid "Sliding Sync is an implementation of [MSC3575](https://github.com/matrix-org/matrix-spec-proposals/blob/kegan/sync-v3/proposals/3575-sync.md) and a prerequisite for running Element X clients ([Element X iOS](https://github.com/element-hq/element-x-ios) and [Element X Android](https://github.com/element-hq/element-x-android)). See the project's [documentation](https://github.com/matrix-org/sliding-sync) to learn more." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:9 +msgid "Adjusting DNS records (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:11 +msgid "By default, this playbook installs the Sliding Sync proxy on the `matrix.` subdomain, at the `/sliding-sync` path (https://matrix.example.com/sliding-sync). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:13 +msgid "If you wish to adjust it, see the section [below](#adjusting-the-sliding-sync-proxy-url-optional) for details about DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:17 +msgid "To enable Sliding Sync proxy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:23 +msgid "Adjusting the Sliding Sync proxy URL (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:25 +msgid "By tweaking the `matrix_sliding_sync_hostname` and `matrix_sliding_sync_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:27 +msgid "Example additional configuration for your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:35 +msgid "If you've changed the default hostname, you may need to create a CNAME record for the Sliding Sync proxy domain (`ss.example.com`), which targets `matrix.example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:37 +msgid "When setting, replace `example.com` with your own." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:39 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:41 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:48 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:50 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:52 +msgid "External databases" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:54 +msgid "Please note that, if your setup utilizes an external database, you must also establish configuration for the sliding sync proxy. Alter the defaults below to suit your configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:64 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:66 +msgid "You **don't need to do anything special** to make use of the Sliding Sync proxy. Simply open your client which supports Sliding Sync (like Element X) and log in." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:68 +msgid "When the Sliding Sync proxy is [installed](#installing), your `/.well-known/matrix/client` file is also updated. A new `org.matrix.msc3575.proxy` section and `url` property are added there and made to point to your Sliding Sync proxy's base URL (e.g. `https://matrix.example.com/sliding-sync`)." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:70 +msgid "This allows clients which support Sliding Sync to detect the Sliding Sync proxy's URL and make use of it." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po index bfe4cae37..9602f8e4f 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,120 +18,108 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-ssl-certificates.md:12 +#: ../../../docs/configuring-playbook-ssl-certificates.md:1 msgid "Adjusting SSL certificate retrieval (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:14 -msgid "By default, the playbook retrieves and automatically renews free SSL certificates from [Let's Encrypt](https://letsencrypt.org/) via [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) for the domains of the services it installs (e.g. `matrix.example.com` and others). Refer this guide if you want to modify settings about how it manages SSL certificates or have the Traefik server use yours." +#: ../../../docs/configuring-playbook-ssl-certificates.md:3 +msgid "By default, this playbook retrieves and auto-renews free SSL certificates from [Let's Encrypt](https://letsencrypt.org/) for the domains it needs (e.g. `matrix.example.com` and others)" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:16 -msgid "**Notes**:" +#: ../../../docs/configuring-playbook-ssl-certificates.md:5 +msgid "This guide is about using the integrated Traefik server and doesn't apply if you're using [your own webserver](configuring-playbook-own-webserver.md)." msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:17 -msgid "This guide is intended to be referred for configuring the integrated Traefik server with regard to SSL certificates retrieval. If you're using [your own webserver](configuring-playbook-own-webserver.md), consult its documentation about how to configure it." -msgstr "" - -#: ../../../docs/configuring-playbook-ssl-certificates.md:18 -msgid "Let's Encrypt ends the expiration notification email service on June 4, 2025 (see: [the official announcement](https://letsencrypt.org/2025/01/22/ending-expiration-emails/)), and it recommends using a third party service for those who want to receive expiration notifications. If you are looking for a self-hosting service, you may be interested in a monitoring tool such as [Update Kuma](https://github.com/louislam/uptime-kuma/)." -msgstr "" - -#: ../../../docs/configuring-playbook-ssl-certificates.md:20 -msgid "The [Mother-of-All-Self-Hosting (MASH)](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook can be used to install and manage an Uptime Kuma instance. See [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/uptime-kuma.md) for the instruction to install it with the playbook. If you are wondering how to use it for your Matrix server, refer to [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/setting-up-services-on-mdad-server.md) for the overview." +#: ../../../docs/configuring-playbook-ssl-certificates.md:7 +msgid "Using staging Let's Encrypt certificates instead of real ones" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:22 -msgid "Use staging Let's Encrypt certificates" +#: ../../../docs/configuring-playbook-ssl-certificates.md:9 +msgid "For testing purposes, you may wish to use staging certificates provide by Let's Encrypt." msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:24 -msgid "For testing purposes, you may wish to use staging certificates provided by Let's Encrypt to avoid hitting [its rate limits](https://letsencrypt.org/docs/rate-limits/)." +#: ../../../docs/configuring-playbook-ssl-certificates.md:11 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:26 -msgid "To use ones, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +#: ../../../docs/configuring-playbook-ssl-certificates.md:17 +msgid "Disabling SSL termination" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:32 -msgid "Disable SSL termination" +#: ../../../docs/configuring-playbook-ssl-certificates.md:19 +msgid "For testing or other purposes, you may wish to install services without SSL termination and have services exposed to `http://` instead of `https://`." msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:34 -msgid "For testing or other purposes, you may wish to install services without SSL termination and have services exposed to `http://` instead of `https://`." +#: ../../../docs/configuring-playbook-ssl-certificates.md:21 +msgid "Add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:36 -msgid "To do so, add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-ssl-certificates.md:27 +msgid "Using self-signed SSL certificates" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:42 -msgid "Use self-signed SSL certificates" +#: ../../../docs/configuring-playbook-ssl-certificates.md:29 +msgid "If you'd like to use your own SSL certificates, instead of the default (SSL certificates obtained automatically via [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) from [Let's Encrypt](https://letsencrypt.org/)):" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:44 -msgid "To use self-signed certificates, generate them and follow the documentation below about using your own certificates." +#: ../../../docs/configuring-playbook-ssl-certificates.md:31 +msgid "generate your self-signed certificate files" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:46 -msgid "Use your own SSL certificates" +#: ../../../docs/configuring-playbook-ssl-certificates.md:32 +msgid "follow the [Using your own SSL certificates](#using-your-own-ssl-certificates) documentation below" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:48 -msgid "To use your own certificates, prepare them and follow the steps below:" +#: ../../../docs/configuring-playbook-ssl-certificates.md:34 +msgid "Using your own SSL certificates" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:50 -msgid "Disable [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) / [Let's Encrypt](https://letsencrypt.org/) support" +#: ../../../docs/configuring-playbook-ssl-certificates.md:36 +msgid "To use your own SSL certificates with Traefik, you need to:" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:51 -msgid "Put a custom Traefik configuration file on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually" +#: ../../../docs/configuring-playbook-ssl-certificates.md:38 +msgid "disable [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) / [Let's Encrypt](https://letsencrypt.org/) support" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:52 -msgid "Register your custom configuration file with Traefik, by adding an extra provider of type [file](https://doc.traefik.io/traefik/providers/file/)" +#: ../../../docs/configuring-playbook-ssl-certificates.md:39 +msgid "put a custom Traefik configuration file on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:53 -msgid "Put the SSL files on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually" +#: ../../../docs/configuring-playbook-ssl-certificates.md:40 +msgid "register your custom configuration file with Traefik, by adding an extra provider of type [file](https://doc.traefik.io/traefik/providers/file/)" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:55 -msgid "For those steps, you can add the following configuration to your `vars.yml` file (adapt to your needs). If you will put the custom configuration files manually, make sure to remove the `aux_file_definitions` variable." +#: ../../../docs/configuring-playbook-ssl-certificates.md:41 +msgid "put the SSL files on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:103 -msgid "Use a DNS-01 ACME challenge type, instead of HTTP-01" +#: ../../../docs/configuring-playbook-ssl-certificates.md:89 +msgid "Using a DNS-01 ACME challenge type, instead of HTTP-01" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:105 -msgid "You can configure Traefik to use the [DNS-01 challenge type](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) for Let's Encrypt. This is less commonly used than the default [HTTP-01 challenge type](https://letsencrypt.org/docs/challenge-types/#http-01-challenge), but can be helpful to:" +#: ../../../docs/configuring-playbook-ssl-certificates.md:91 +msgid "You can configure Traefik to use the [DNS-01 challenge type](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) for Let's Encrypt. This is less commonly used than the default [HTTP-01 challenge type](https://letsencrypt.org/docs/challenge-types/#http-01-challenge), but it can be helpful to:" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:107 +#: ../../../docs/configuring-playbook-ssl-certificates.md:93 msgid "hide your public IP from Let's Encrypt logs" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:108 +#: ../../../docs/configuring-playbook-ssl-certificates.md:94 msgid "allow you to obtain SSL certificates for servers which are not accessible (via HTTP) from the public internet (and for which the HTTP-01 challenge would fail)" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:110 -msgid "Example: Cloudflare" -msgstr "" - -#: ../../../docs/configuring-playbook-ssl-certificates.md:112 -msgid "Here is an example for configurations on the `vars.yml` file for Cloudflare. Please adjust it as necessary before applying it." +#: ../../../docs/configuring-playbook-ssl-certificates.md:96 +msgid "This is an example for how to edit the `vars.yml` file if you're using Cloudflare:" msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:127 +#: ../../../docs/configuring-playbook-ssl-certificates.md:111 msgid "Make sure to change the value of \"provider\" to your particular DNS solution, and provide the appropriate environment variables. The full list of supported providers is available [here](https://doc.traefik.io/traefik/https/acme/#providers)." msgstr "" -#: ../../../docs/configuring-playbook-ssl-certificates.md:129 +#: ../../../docs/configuring-playbook-ssl-certificates.md:113 msgid "This example assumes you're using Cloudflare to manage your DNS zone. Note that it requires the use of two tokens: one for reading all zones (`CF_ZONE_API_TOKEN`) and another that must be able to edit the particular domain you're using (`CF_DNS_API_TOKEN`). For security, it's recommended that you create two fine-grained tokens for this purpose, but you might choose to use the same token for both." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sygnal.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sygnal.po index c3c6b73dd..7c9f6c6ac 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sygnal.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sygnal.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,140 +18,132 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-sygnal.md:8 +#: ../../../docs/configuring-playbook-sygnal.md:1 msgid "Setting up the Sygnal push gateway (optional)" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:10 +#: ../../../docs/configuring-playbook-sygnal.md:3 msgid "The playbook can install and configure the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:12 +#: ../../../docs/configuring-playbook-sygnal.md:5 msgid "See the project's [documentation](https://github.com/matrix-org/sygnal/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:14 +#: ../../../docs/configuring-playbook-sygnal.md:7 msgid "**Note**: most people don't need to install their own gateway. As Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) documentation says:" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:16 +#: ../../../docs/configuring-playbook-sygnal.md:9 msgid "It is not feasible to allow end-users to configure their own Sygnal instance, because the Sygnal instance needs the appropriate FCM or APNs secrets that belong to the application." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:18 +#: ../../../docs/configuring-playbook-sygnal.md:11 msgid "This optional playbook component is only useful to people who develop/build their own Matrix client applications themselves." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:20 +#: ../../../docs/configuring-playbook-sygnal.md:13 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:22 +#: ../../../docs/configuring-playbook-sygnal.md:15 msgid "By default, this playbook installs Sygnal on the `sygnal.` subdomain (`sygnal.example.com`) and requires you to create a CNAME record for `sygnal`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:24 +#: ../../../docs/configuring-playbook-sygnal.md:17 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:26 +#: ../../../docs/configuring-playbook-sygnal.md:19 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:28 +#: ../../../docs/configuring-playbook-sygnal.md:21 msgid "To enable Sygnal, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:56 +#: ../../../docs/configuring-playbook-sygnal.md:49 msgid "Configuring [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/) is easier, as it only requires that you provide some config values." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:58 +#: ../../../docs/configuring-playbook-sygnal.md:51 msgid "To configure [APNS](https://developer.apple.com/notifications/) (Apple Push Notification Service), you'd need to provide one or more certificate files. To do that, the above example configuration:" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:60 +#: ../../../docs/configuring-playbook-sygnal.md:53 msgid "makes use of the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) (and its `aux_file_definitions` variable) to make the playbook install files into `/matrix/sygnal/data` (the `matrix_sygnal_data_path` variable). See [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml) of the `aux` role for usage examples. It also makes sure the files are owned by `matrix:matrix`, so that Sygnal can read them. Of course, you can also install these files manually yourself, if you'd rather not use `aux`." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:62 +#: ../../../docs/configuring-playbook-sygnal.md:55 msgid "references these files in the Sygnal configuration (`matrix_sygnal_apps`) using a path like `/data/…` (the `/matrix/sygnal/data` directory on the host system is mounted into the `/data` directory inside the container)" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:64 +#: ../../../docs/configuring-playbook-sygnal.md:57 msgid "Adjusting the Sygnal URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:66 +#: ../../../docs/configuring-playbook-sygnal.md:59 msgid "By tweaking the `matrix_sygnal_hostname` and `matrix_sygnal_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:68 +#: ../../../docs/configuring-playbook-sygnal.md:61 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:79 +#: ../../../docs/configuring-playbook-sygnal.md:72 msgid "After changing the domain, **you may need to adjust your DNS** records to point the Sygnal domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:81 +#: ../../../docs/configuring-playbook-sygnal.md:74 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:83 +#: ../../../docs/configuring-playbook-sygnal.md:76 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:85 +#: ../../../docs/configuring-playbook-sygnal.md:78 msgid "There are some additional things you may wish to configure about the component." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:87 +#: ../../../docs/configuring-playbook-sygnal.md:80 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:89 +#: ../../../docs/configuring-playbook-sygnal.md:82 msgid "`roles/custom/matrix-sygnal/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:90 +#: ../../../docs/configuring-playbook-sygnal.md:83 msgid "`roles/custom/matrix-sygnal/templates/config.yaml.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_sygnal_configuration_extension_yaml` variable" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:92 +#: ../../../docs/configuring-playbook-sygnal.md:85 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:94 +#: ../../../docs/configuring-playbook-sygnal.md:87 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:101 +#: ../../../docs/configuring-playbook-sygnal.md:94 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:103 +#: ../../../docs/configuring-playbook-sygnal.md:96 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:105 +#: ../../../docs/configuring-playbook-sygnal.md:98 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:107 +#: ../../../docs/configuring-playbook-sygnal.md:100 msgid "To make use of your Sygnal installation, you'd need to build your own Matrix client application, which uses the same API keys (for [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/)) and certificates (for [APNS](https://developer.apple.com/notifications/)) and is to your Sygnal URL endpoint (e.g. `https://sygnal.example.com`)." msgstr "" -#: ../../../docs/configuring-playbook-sygnal.md:109 +#: ../../../docs/configuring-playbook-sygnal.md:102 msgid "Refer to Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) document." msgstr "" - -#: ../../../docs/configuring-playbook-sygnal.md:111 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-sygnal.md:113 -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-sygnal`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po new file mode 100644 index 000000000..36e8426b0 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po @@ -0,0 +1,125 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +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" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: jp\n" +"Language-Team: jp \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.16.0\n" + +#: ../../../docs/configuring-playbook-synapse-admin.md:1 +msgid "Setting up Synapse Admin (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:3 +msgid "The playbook can install and configure [etkecc/synapse-admin](https://github.com/etkecc/synapse-admin) (a [feature-rich](https://github.com/etkecc/synapse-admin#fork-differences) fork of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin), community room: [#synapse-admin:etke.cc](https://matrix.to/#/#synapse-admin:etke.cc)) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:5 +msgid "synapse-admin is a web UI tool you can use to **administrate users, rooms, media, etc. on your Matrix server**. It's designed to work with the Synapse homeserver implementation and WON'T work with Dendrite because [Dendrite Admin API](https://element-hq.github.io/dendrite/administration/adminapi) differs from [Synapse Admin API](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:7 +msgid "💡 **Note**: the latest version of synapse-admin is hosted by [etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). If you only need this service occasionally and trust giving your admin credentials to a 3rd party Single Page Application, you can consider using it from there and avoiding the (small) overhead of self-hosting." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:9 +msgid "Adjusting DNS records (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:11 +msgid "By default, this playbook installs Synapse Admin on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:13 +msgid "If you wish to adjust it, see the section [below](#adjusting-the-synapse-admin-url-optional) for details about DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:17 +msgid "To enable Synapse Admin, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:23 +msgid "**Note**: Synapse Admin requires Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to function. Access to them is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, for additional security, we normally leave them unexposed, following [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). Because Synapse Admin needs these APIs to function, when installing Synapse Admin, the playbook **automatically** exposes the Synapse Admin API publicly for you. Depending on the homeserver implementation you're using (Synapse, Dendrite), this is equivalent to:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:25 +msgid "for [Synapse](./configuring-playbook-synapse.md) (our default homeserver implementation): `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:26 +msgid "for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:28 +msgid "By default, synapse-admin installation will be [restricted to only work with one homeserver](https://github.com/etkecc/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) — the one managed by the playbook. To adjust these restrictions, tweak the `matrix_synapse_admin_config_restrictBaseUrl` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:30 +msgid "[!WARNING] If you're using [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS) for authentication, you will be able to [log into synapse-admin with an access token](https://github.com/etkecc/synapse-admin/pull/58), but certain synapse-admin features (especially those around user management) will be limited or not work at all." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:33 +msgid "Adjusting the Synapse Admin URL (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:35 +msgid "By tweaking the `matrix_synapse_admin_hostname` and `matrix_synapse_admin_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:37 +msgid "Example additional configuration for your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:45 +msgid "If you've changed the default hostname, you may need to create a CNAME record for the Synapse Admin domain (`admin.example.com`), which targets `matrix.example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:47 +msgid "When setting, replace `example.com` with your own." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:49 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:51 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:58 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:60 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:62 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:64 +msgid "After installation, Synapse Admin will be accessible at: `https://matrix.example.com/synapse-admin/`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:66 +msgid "To use Synapse Admin, you need to have [registered at least one administrator account](registering-users.md) on your server." +msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po index 6c280e2de..4157b151a 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,20 +18,56 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:18 -msgid "Setting up Synapse Auto Invite Accept (optional, removed)" +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:1 +msgid "Setting up Synapse Auto Invite Accept (optional)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:20 -msgid "🪦 The playbook used to be able to install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite), but no longer includes this component, as the same functionality [has been integrated](https://github.com/element-hq/synapse/pull/17147) to Synapse since [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0)." +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:3 +msgid "The playbook can install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) for you." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:22 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:5 +msgid "In short, it automatically accepts room invites. You can specify that only 1:1 room invites are auto-accepted. Defaults to false if not specified." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:7 +msgid "See the project's [documentation](https://github.com/matrix-org/synapse-auto-accept-invite/blob/main/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:9 +msgid "**Note**: Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0), the same feature [has been merged](https://github.com/element-hq/synapse/pull/17147) into Synapse (see the [Native alternative](#native-alternative) section below). You'd better use the native feature, instead of the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) 3rd party module." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:13 +msgid "If you decide that you'd like to let this playbook install the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite module for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:21 +msgid "Synapse worker deployments" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:23 +msgid "In a [workerized Synapse deployment](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/c9a842147e09647c355799ca024d65a5de66b099/docs/configuring-playbook-synapse.md#load-balancing-with-workers) it is possible to run this module on a worker to reduce the load on the main process (Default is `null`). For example, add this to your configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:29 +msgid "There might be an [issue with federation](https://github.com/matrix-org/synapse-auto-accept-invite/issues/18)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:31 msgid "Native alternative" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:24 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:33 +msgid "Since Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0), the functionality provided by the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) 3rd party module [has been made](https://github.com/element-hq/synapse/pull/17147) part of Synapse." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:35 msgid "Here's example configuration for using the **native** Synapse feature:" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po index 4da719a02..345f28d0f 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,104 +18,68 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:9 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:1 msgid "Setting up synapse-auto-compressor (optional)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:11 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:3 msgid "The playbook can install and configure [synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) for you." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:13 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:5 msgid "It's a CLI tool that automatically compresses Synapse's `state_groups` database table in the background." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:15 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:7 msgid "See the project's [documentation](https://github.com/matrix-org/rust-synapse-compress-state/blob/master/README.md#automated-tool-synapse_auto_compressor) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:17 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:9 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:19 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:11 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:25 -msgid "Edit the schedule (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:27 -msgid "By default the task will around 0 a.m. every day based on the `matrix_synapse_auto_compressor_schedule` variable with a randomized delay of 6 hours (controlled by the `matrix_synapse_auto_compressor_schedule_randomized_delay_sec` variable). It is defined in the format of systemd timer calendar." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:29 -msgid "To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs):" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:38 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:40 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:42 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:44 -msgid "`roles/custom/matrix-synapse-auto-compressor/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:46 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:17 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:48 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:19 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:55 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:26 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:57 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:28 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:59 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:30 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:61 -msgid "After installation, `synapse_auto_compressor` will run automatically every day at `00:00:00` (as defined in `matrix_synapse_auto_compressor_schedule` by default)." +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:32 +msgid "After installation, `synapse_auto_compressor` will run automatically every day at `00:00:00` (as defined in `matrix_synapse_auto_compressor_calendar` by default)." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:63 -msgid "Manually start the task" +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:34 +msgid "Manually execute compression" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:65 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:36 msgid "Sometimes it can be helpful to execute compression as you'd like, avoiding to wait until 00:00, like when you test your configuration." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:67 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:38 msgid "If you want to execute it immediately, log in to the server with SSH and run `systemctl start matrix-synapse-auto-compressor`." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:69 +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:40 msgid "This will not return until the compression is done, so it can possibly take a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable." msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:71 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:73 -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-auto-compressor`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po index a99bd230d..0407996b6 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,292 +18,260 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:10 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:1 msgid "Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider (optional)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:12 -msgid "The playbook can install and configure the [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) for you." +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:3 +msgid "If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service), you can use the [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) media provider module for Synapse." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:14 -msgid "It is a media provider module for Synapse to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service) object storage." +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:5 +msgid "An alternative (which has worse performance) is to use [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:16 -msgid "See the project's [documentation](https://github.com/matrix-org/synapse-s3-storage-provider/blob/main/README.md) to learn what it does and why it might be useful to you." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:18 -msgid "**Note**: alternatively you can use [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md) despite worse performance." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:20 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:7 msgid "How it works?" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:22 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:9 msgid "Summarized writings here are inspired by [this article](https://quentin.dufour.io/blog/2021-09-14/matrix-synapse-s3-storage/)." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:24 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:11 msgid "The way media storage providers in Synapse work has some caveats:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:26 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:13 msgid "Synapse still continues to use locally-stored files (for creating thumbnails, serving files, etc)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:27 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:14 msgid "the media storage provider is just an extra storage mechanism (in addition to the local filesystem)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:28 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:15 msgid "all files are stored locally at first, and then copied to the media storage provider (either synchronously or asynchronously)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:29 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:16 msgid "if a file is not available on the local filesystem, it's pulled from a media storage provider" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:31 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:18 msgid "You may be thinking **if all files are stored locally as well, what's the point**?" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:33 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:20 msgid "You can run some scripts to delete the local files once in a while (which we do automatically by default — see [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem)), thus freeing up local disk space. If these files are needed in the future (for serving them to users, etc.), Synapse will pull them from the media storage provider on demand." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:35 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:22 msgid "While you will need some local disk space around, it's only to accommodate usage, etc., and won't grow as large as your S3 store." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:37 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:24 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:39 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:26 msgid "After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:61 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:48 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:63 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:50 msgid "There are some additional things you may wish to configure about the server." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:65 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:52 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:67 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:54 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-s3-storage-provider.md:69 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:71 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:78 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:80 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:82 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:56 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:84 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:58 msgid "If you have existing files in Synapse's media repository (`/matrix/synapse/storage/media-store/…`):" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:86 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:60 msgid "new files will start being stored both locally and on the S3 store" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:87 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:61 msgid "the existing files will remain on the local filesystem only until [migrating them to the S3 store](#migrating-your-existing-media-files-to-the-s3-store)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:88 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:62 msgid "at some point (and periodically in the future), you can delete local files which have been uploaded to the S3 store already" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:90 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:64 msgid "Regardless of whether you need to [Migrate your existing files to the S3 store](#migrating-your-existing-media-files-to-the-s3-store) or not, make sure you've familiarized yourself with [How it works?](#how-it-works) above and [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem) below." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:92 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:66 msgid "Migrating your existing media files to the S3 store" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:94 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:68 msgid "Migrating your existing data can happen in multiple ways:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:96 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:70 msgid "[using the `s3_media_upload` script from `synapse-s3-storage-provider`](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (very slow when dealing with lots of data)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:97 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:71 msgid "[using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload) (quicker when dealing with lots of data)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:99 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:73 msgid "💡 **Note**: instead of using `s3_media_upload` directly, which is very slow and painful for an initial data migration, we recommend [using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload)." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:101 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:75 msgid "Using the `s3_media_upload` script from `synapse-s3-storage-provider`" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:103 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:77 msgid "To copy your existing files, SSH into the server and run `/matrix/synapse/ext/s3-storage-provider/bin/shell`." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:105 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:79 msgid "This launches a Synapse container, which has access to the local media store, Postgres database, S3 store and has some convenient environment variables configured for you to use (`MEDIA_PATH`, `BUCKET`, `ENDPOINT`, `UPDATE_DB_DAYS`, etc)." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:107 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:81 msgid "Then use the following commands (`$` values come from environment variables — they're **not placeholders** that you need to substitute):" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:109 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:83 msgid "`s3_media_upload update-db $UPDATE_DB_DURATION` — create a local SQLite database (`cache.db`) with a list of media repository files (from the `synapse` Postgres database) eligible for operating on" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:110 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:84 msgid "`$UPDATE_DB_DURATION` is influenced by the `matrix_synapse_ext_synapse_s3_storage_provider_update_db_day_count` variable (defaults to `0`)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:111 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:85 msgid "`$UPDATE_DB_DURATION` defaults to `0d` (0 days), which means **include files which haven't been accessed for more than 0 days** (that is, **all files will be included**)." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:112 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:86 msgid "`s3_media_upload check-deleted $MEDIA_PATH` — check whether files in the local cache still exist in the local media repository directory" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:113 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:87 msgid "`s3_media_upload upload $MEDIA_PATH $BUCKET --delete --storage-class $STORAGE_CLASS --endpoint-url $ENDPOINT` — uploads locally-stored files to S3 and deletes them from the local media repository directory" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:115 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:89 msgid "The `s3_media_upload upload` command may take a lot of time to complete." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:117 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:91 msgid "Instead of running the above commands manually in the shell, you can also run the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script which will run the same commands automatically. We demonstrate how to do it manually, because:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:119 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:93 msgid "it's what the upstream project demonstrates and it teaches you how to use the `s3_media_upload` tool" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:120 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:94 msgid "allows you to check and verify the output of each command, to catch mistakes" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:121 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:95 msgid "includes progress bars and detailed output for each command" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:122 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:96 msgid "allows you to easily interrupt slow-running commands, etc. (the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container without interactive TTY support, so `Ctrl+C` may not work and you and require killing via `docker kill …`)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:124 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:98 msgid "Using another tool in combination with `s3_media_upload`" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:126 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:100 msgid "To migrate your existing local data to S3, we recommend to:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:128 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:102 msgid "**first** use another tool ([`aws s3`](#copying-data-to-amazon-s3) or [`b2 sync`](#copying-data-to-backblaze-b2), etc.) to copy the local files to the S3 bucket" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:130 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:104 msgid "**only then** [use the `s3_media_upload` tool to finish the migration](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (this checks to ensure all files are uploaded and then deletes the local files)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:132 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:106 msgid "Copying data to Amazon S3" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:134 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:108 msgid "To copy to AWS S3, start a container on the Matrix server like this:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:146 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:120 msgid "Copying data to an S3 alternative using the aws-s3 tool" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:148 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:122 msgid "To copy to a provider other than AWS S3 (e.g. Storj, Wasabi, Digital Ocean Spaces, etc.), you can use the command for [Copying data to Amazon S3](#copying-data-to-amazon-s3) with an added `--endpoint-url=$ENDPOINT` argument." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:150 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:124 msgid "Add this argument to the command **as-is** (`$ENDPOINT` is an environment variable corresponding to `matrix_synapse_ext_synapse_s3_storage_provider_config_endpoint_url`, so you don't need to touch it). Make sure to add the argument **before** the final quote (`'`) of the command." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:152 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:126 msgid "Copying data to Backblaze B2" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:154 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:128 msgid "You can copy files to Backblaze B2 either by following the [Copying data to an S3 alternative using the aws-s3 tool](#copying-data-to-an-s3-alternative-using-the-aws-s3-tool) or by using the B2-specific [b2 command-line tool](https://www.backblaze.com/b2/docs/quick_command_line.html) as described below." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:156 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:130 msgid "To copy the data using the `b2` tool, start a container on the Matrix server like this:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:170 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:144 msgid "Periodically cleaning up the local filesystem" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:172 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:146 msgid "As described in [How it works?](#how-it-works) above, when new media is uploaded to the Synapse homeserver, it's first stored locally and then also stored on the remote S3 storage." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:174 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:148 msgid "By default, we periodically ensure that all local files are uploaded to S3 and are then removed from the local filesystem. This is done automatically using:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:176 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:150 msgid "the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:177 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:151 msgid "… invoked via the `matrix-synapse-s3-storage-provider-migrate.service` service" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:178 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:152 msgid "… triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` timer, every day at 05:00" msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:180 -msgid "The same `migrate` script also prunes empty directories in the local media repository (`remote_content` and `remote_thumbnail`) after upload/delete operations." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:182 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:154 msgid "So… you don't need to perform any maintenance yourself." msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:184 -msgid "The schedule is defined in the format of systemd timer calendar. To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs):" -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po index e93825e19..32fbdb473 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po @@ -10,7 +10,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: 2024-12-20 09:53+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,44 +18,28 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:8 +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:1 msgid "Setting up Synapse Simple Antispam (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:10 +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:3 msgid "The playbook can install and configure [synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) for you." msgstr "" -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:12 -msgid "It lets you fight invite-spam by automatically blocking invitations from a list of servers specified by you (blacklisting)." +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:5 +msgid "It lets you fight invite-spam by automatically blocking invitiations from a list of servers specified by you (blacklisting)." msgstr "" -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:14 +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:7 msgid "See the project's [documentation](https://github.com/t2bot/synapse-simple-antispam/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:16 +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:9 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:18 +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:11 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" - -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:28 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:30 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:37 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:39 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po index e31065e67..024aaf248 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,128 +18,92 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:9 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:1 msgid "Enabling synapse-usage-exporter for Synapse usage statistics (optional)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:11 -msgid "The playbook can install and configure [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) for you." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:13 -msgid "It allows you to export the usage statistics of a Synapse homeserver to this container service and for the collected metrics to later be scraped by Prometheus." +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:3 +msgid "[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) allows you to export the usage statistics of a Synapse homeserver to this container service and for the collected metrics to later be scraped by Prometheus." msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:15 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:5 msgid "Synapse does not include usage statistics in its Prometheus metrics. They can be reported to an HTTP `PUT` endpoint 5 minutes after startup and from then on at a fixed interval of once every three hours. This role integrates a simple [Flask](https://flask.palletsprojects.com) project that offers an HTTP `PUT` endpoint and holds the most recent received record available to be scraped by Prometheus." msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:17 -msgid "See the project's [documentation](https://github.com/loelkes/synapse-usage-exporter/blob/main/README.md) to learn what it does and why it might be useful to you." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:19 -msgid "What does it do?" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:21 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:7 msgid "Enabling this service will automatically:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:23 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:9 msgid "install the synapse-usage-exporter service" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:24 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:10 msgid "re-configure Synapse to push (via HTTP `PUT`) usage statistics information to synapse-usage-exporter" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:25 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:11 msgid "re-configure [Prometheus](./configuring-playbook-prometheus-grafana.md) (if Prometheus is enabled), to periodically scrape metrics from synapse-usage-exporter" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:26 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:12 msgid "add a new [Grafana](./configuring-playbook-prometheus-grafana.md) dashboard (if Grafana is enabled) containing Synapse usage statistics" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:28 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:14 msgid "Adjusting DNS records (optional)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:30 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:16 msgid "By default, this playbook installs synapse-usage-exporter on the `matrix.` subdomain, at the `/report-usage-stats/push` path (https://matrix.example.com/report-usage-stats/push). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:32 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:18 msgid "If you wish to adjust it, see the section [below](#adjusting-the-synapse-usage-exporter-url-optional) for details about DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:34 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:20 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:36 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:22 msgid "To enable synapse-usage-exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:48 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:34 msgid "Adjusting the synapse-usage-exporter URL (optional)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:50 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:36 msgid "By tweaking the `matrix_synapse_usage_exporter_hostname` and `matrix_synapse_usage_exporter_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:52 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:38 msgid "Example additional configuration for your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:61 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:47 msgid "If you've changed the default hostname, you may need to create a CNAME record for the synapse-usage-exporter domain (`sue.example.com`), which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:63 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:49 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:65 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:67 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:69 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:71 -msgid "`roles/custom/matrix-synapse-usage-exporter/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:73 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:51 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:75 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:53 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:82 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:60 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:84 +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:62 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:86 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:88 -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-usage-exporter`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-traefik.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-traefik.po index 52575f57b..5fbbcbac9 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-traefik.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-traefik.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,181 +18,121 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-traefik.md:10 +#: ../../../docs/configuring-playbook-traefik.md:1 msgid "Configuring the Traefik reverse-proxy (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:12 -msgid "By default, this playbook installs and manages a [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered by the [ansible-role-traefik](https://github.com/mother-of-all-self-hosting/ansible-role-traefik) Ansible role for you. If that's okay, you can skip this document." +#: ../../../docs/configuring-playbook-traefik.md:3 +msgid "By default, this playbook installs and manages a [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered by the [ansible-role-traefik](https://github.com/mother-of-all-self-hosting/ansible-role-traefik) Ansible role." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:14 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:16 +#: ../../../docs/configuring-playbook-traefik.md:5 msgid "This Ansible role support various configuration options. Feel free to consult its `default/main.yml` variables file." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:18 -msgid "Disable access logs" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:20 -msgid "To disable access logging, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +#: ../../../docs/configuring-playbook-traefik.md:7 +msgid "Adjusting SSL certificate retrieval" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:26 -msgid "Enable Traefik Dashboard" +#: ../../../docs/configuring-playbook-traefik.md:9 +msgid "See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:28 -msgid "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:" +#: ../../../docs/configuring-playbook-traefik.md:11 +msgid "Increase logging verbosity" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:37 -msgid "Generate the `traefik_dashboard_basicauth_htpasswd` value on your local machine with a command like `htpasswd -nb YOUR_USERNAME_HERE YOUR_PASSWORD_HERE`." +#: ../../../docs/configuring-playbook-traefik.md:17 +msgid "Disable access logs" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:39 -msgid "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." +#: ../../../docs/configuring-playbook-traefik.md:19 +msgid "This will disable access logging." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:41 -msgid "[!WARNING] Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts." +#: ../../../docs/configuring-playbook-traefik.md:25 +msgid "Enable Traefik Dashboard" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:44 -msgid "Extending the configuration" +#: ../../../docs/configuring-playbook-traefik.md:27 +msgid "This will enable a Traefik [Dashboard](https://doc.traefik.io/traefik/operations/dashboard/) UI at `https://matrix.example.com/dashboard/` (note the trailing `/`)." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:46 -msgid "There are some additional things you may wish to configure about the component." +#: ../../../docs/configuring-playbook-traefik.md:37 +msgid "[!WARNING] Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:48 -msgid "Take a look at:" +#: ../../../docs/configuring-playbook-traefik.md:40 +msgid "Additional configuration" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:50 -msgid "[Traefik role](https://github.com/mother-of-all-self-hosting/ansible-role-traefik)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-traefik/blob/main/defaults/main.yml) for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `traefik_configuration_extension_yaml` variable" +#: ../../../docs/configuring-playbook-traefik.md:42 +msgid "Use the `traefik_configuration_extension_yaml` variable provided by the Traefik Ansible role to override or inject additional settings, even when no dedicated variable exists." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:52 -msgid "For example, to enable and secure the Dashboard, you can add the following configuration to your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:54 -msgid "**Note**: this is a contrived example as you can enable and secure the Dashboard using the dedicated variables. See above for details." -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:72 msgid "Reverse-proxying another service behind Traefik" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:74 +#: ../../../docs/configuring-playbook-traefik.md:54 msgid "The preferred way to reverse-proxy additional services behind Traefik would be to start the service as another container, configure the container with the corresponding Traefik [container labels](https://docs.docker.com/config/labels-custom-metadata/) (see [Traefik & Docker](https://doc.traefik.io/traefik/routing/providers/docker/)), and connect the service to the `traefik` network. Some services are also already available via the compatible [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook), but take a look at the minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md)." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:76 +#: ../../../docs/configuring-playbook-traefik.md:56 msgid "However, if your service does not run on a container or runs on another machine, the following configuration might be what you are looking for." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:78 +#: ../../../docs/configuring-playbook-traefik.md:58 msgid "Reverse-proxying a remote HTTP/HTTPS service behind Traefik" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:80 +#: ../../../docs/configuring-playbook-traefik.md:60 msgid "If you want to host another webserver would be reachable via `my-fancy-website.example.net` from the internet and via `https://:` from inside your network, you can make the playbook's integrated Traefik instance reverse-proxy the traffic to the correct host." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:82 +#: ../../../docs/configuring-playbook-traefik.md:62 msgid "Prerequisites: DNS and routing for the domain `my-fancy-website.example.net` need to be set up correctly. In this case, you'd be pointing the domain name to your Matrix server — `my-fancy-website.example.net` would be a CNAME going to `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:84 +#: ../../../docs/configuring-playbook-traefik.md:64 msgid "First, we have to adjust the static configuration of Traefik, so that we can add additional configuration files:" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:98 +#: ../../../docs/configuring-playbook-traefik.md:78 msgid "If you are using a self-signed certificate on your webserver, you can tell Traefik to trust your own backend servers by adding more configuration to the static configuration file. If you do so, bear in mind the security implications of disabling the certificate validity checks towards your back end." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:112 +#: ../../../docs/configuring-playbook-traefik.md:92 msgid "Next, you have to add a new dynamic configuration file for Traefik that contains the actual information of the server using the `aux_file_definitions` variable. In this example, we will terminate SSL at the Traefik instance and connect to the other server via HTTPS. Traefik will now take care of managing the certificates." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:131 -#: ../../../docs/configuring-playbook-traefik.md:154 +#: ../../../docs/configuring-playbook-traefik.md:111 +#: ../../../docs/configuring-playbook-traefik.md:134 msgid "Changing the `url` to one with an `http://` prefix would allow to connect to the server via HTTP." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:133 +#: ../../../docs/configuring-playbook-traefik.md:113 msgid "Reverse-proxying another service behind Traefik without terminating SSL" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:135 +#: ../../../docs/configuring-playbook-traefik.md:115 msgid "If you do not want to terminate SSL at the Traefik instance (for example, because you're already terminating SSL at other webserver), you need to adjust the static configuration in the same way as in the previous chapter in order to be able to add our own dynamic configuration files. Afterwards, you can add the following configuration to your `vars.yml` configuration file:" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:156 +#: ../../../docs/configuring-playbook-traefik.md:136 msgid "With these changes, all TCP traffic will be reverse-proxied to the target system." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:158 +#: ../../../docs/configuring-playbook-traefik.md:138 msgid "[!WARNING] This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:161 +#: ../../../docs/configuring-playbook-traefik.md:141 msgid "Traefik behind a `proxy_protocol` reverse-proxy" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:163 -msgid "If you run a reverse-proxy which speaks `proxy_protocol`, add the following configuration to your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:182 -msgid "Other configurations" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:184 -msgid "Adjusting SSL certificate retrieval" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:186 -msgid "See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page." -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:188 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:190 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.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-traefik.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. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:201 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:203 -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-traefik`." -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:205 -msgid "Increase logging verbosity" -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:207 -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:" +#: ../../../docs/configuring-playbook-traefik.md:143 +msgid "If you run a reverse-proxy which speaks `proxy_protocol`, add the following to your configuration file:" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-turn.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-turn.po index c455599c6..71519811d 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-turn.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-turn.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,220 +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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-playbook-turn.md:14 +#: ../../../docs/configuring-playbook-turn.md:1 msgid "Configuring a TURN server (optional, advanced)" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:16 -msgid "By default, the [coturn](https://github.com/coturn/coturn) TURN server component is enabled automatically only when [Jitsi](configuring-playbook-jitsi.md) is enabled. If you're not using Jitsi, coturn is not enabled by default." +#: ../../../docs/configuring-playbook-turn.md:3 +msgid "By default, this playbook installs and configures the [coturn](https://github.com/coturn/coturn) as a TURN server, through which clients can make audio/video calls even from [NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed networks. It also configures the Synapse chat server by default, so that it points to the coturn TURN server installed by the playbook. If that's okay, you can skip this document." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:18 -msgid "If you explicitly need coturn while not using Jitsi, enable it with:" +#: ../../../docs/configuring-playbook-turn.md:5 +msgid "If you'd like to stop the playbook installing the server, see the section [below](#disabling-coturn) to check the configuration for disabling it." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:24 -msgid "and configure its IP-related settings in the section below." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:26 -msgid "If you'd like coturn to stay disabled even when Jitsi is enabled, or if you prefer to use an external TURN provider, see [disabling coturn](#disabling-coturn) section below." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:28 -msgid "When Coturn is not enabled, homeservers (like Synapse) would not point to TURN servers and *legacy* audio/video call functionality may fail. If you're using [Matrix RTC](configuring-playbook-matrix-rtc.md) (for [Element Call](configuring-playbook-element-call.md)), you likely don't have a need to enable coturn." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:30 -msgid "Adjusting firewall rules" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:32 -msgid "To ensure Coturn functions correctly, the following firewall rules and port forwarding settings are required when coturn is enabled:" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:34 -msgid "`3478/tcp`: STUN/TURN over TCP" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:35 -msgid "`3478/udp`: STUN/TURN over UDP" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:36 -msgid "`5349/tcp`: TURN over TCP" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:37 -msgid "`5349/udp`: TURN over UDP" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:38 -msgid "`49152-49172/udp`: TURN/UDP relay range" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:40 -msgid "If LiveKit's embedded TURN is enabled at the same time (for MatrixRTC/Element Call), keep the Coturn relay range distinct from LiveKit's relay range (`livekit_server_config_turn_relay_range_start`/`livekit_server_config_turn_relay_range_end`)." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:42 -msgid "💡 Docker configures the server's internal firewall for you. In most cases, you don't need to do anything special on the host itself." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:44 +#: ../../../docs/configuring-playbook-turn.md:7 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:46 +#: ../../../docs/configuring-playbook-turn.md:9 msgid "Define public IP manually (optional)" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:48 -msgid "If you enable coturn (either via Jitsi or manually), we recommend that you configure the public IP addresses of your server in the `vars.yml` file:" +#: ../../../docs/configuring-playbook-turn.md:11 +msgid "In the `hosts` file we explicitly ask for your server's external IP address when defining `ansible_host`, because the same value is used for configuring coturn." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:55 -msgid "If you'd like to rely on external IP address auto-detection (not recommended unless you need it), avoid configuring this variable. The playbook will automatically contact an [echoip](https://github.com/mpolden/echoip)-compatible service (`https://ifconfig.co/json` by default) to determine your server's IP address. This API endpoint is configurable via the `coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable." +#: ../../../docs/configuring-playbook-turn.md:13 +msgid "If you'd rather use a local IP for `ansible_host`, add the following configuration to your `vars.yml` file. Make sure to replace `YOUR_PUBLIC_IP` with the pubic IP used by the server." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:57 -msgid "[!NOTE] You can self-host the echoip service by using the [Mother-of-All-Self-Hosting (MASH)](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook. See [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/echoip.md) for the instruction to install it with the playbook. If you are wondering how to use it for your Matrix server, refer to [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/setting-up-services-on-mdad-server.md) for the overview." +#: ../../../docs/configuring-playbook-turn.md:19 +msgid "If you'd like to rely on external IP address auto-detection (not recommended unless you need it), set an empty value to the variable. The playbook will automatically contact an [EchoIP](https://github.com/mpolden/echoip)-compatible service (`https://ifconfig.co/json` by default) to determine your server's IP address. This API endpoint is configurable via the `matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:60 +#: ../../../docs/configuring-playbook-turn.md:21 +msgid "If your server has multiple external IP addresses, the coturn role offers a different variable for specifying them:" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:28 msgid "Change the authentication mechanism (optional)" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:62 +#: ../../../docs/configuring-playbook-turn.md:30 msgid "The playbook uses the [`auth-secret` authentication method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L186-L199) by default, but you may switch to the [`lt-cred-mech` method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L178) which [some report](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3191) to be working better." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:64 +#: ../../../docs/configuring-playbook-turn.md:32 msgid "To do so, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:70 +#: ../../../docs/configuring-playbook-turn.md:38 msgid "Regardless of the selected authentication method, the playbook generates secrets automatically and passes them to the homeserver and coturn." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:72 +#: ../../../docs/configuring-playbook-turn.md:40 msgid "If [Jitsi](configuring-playbook-jitsi.md) is installed, note that switching to `lt-cred-mech` will disable the integration between Jitsi and your coturn server, as Jitsi seems to support the `auth-secret` authentication method only." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:74 -msgid "Customize the Coturn hostname (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:76 -msgid "By default, Coturn uses the same hostname as your Matrix homeserver (the value of `matrix_server_fqn_matrix`, which is typically `matrix.example.com`)." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:78 -msgid "If you'd like to use a custom subdomain for Coturn (e.g., `turn.example.com` or `t.matrix.example.com`), add the following configuration to your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:84 -msgid "The playbook will automatically:" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:85 -msgid "Configure Coturn to use this hostname" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:86 -msgid "Obtain an SSL certificate for the custom domain via Traefik" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:87 -msgid "Update all TURN URIs to point to the custom domain" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:89 -msgid "**Note**: Make sure the custom hostname resolves to your server's IP address via DNS before running the playbook." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:91 +#: ../../../docs/configuring-playbook-turn.md:42 msgid "Use your own external coturn server (optional)" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:93 +#: ../../../docs/configuring-playbook-turn.md:44 msgid "If you'd like to use another TURN server (be it coturn or some other one), add the following configuration to your `vars.yml` file. Make sure to replace `HOSTNAME_OR_IP` with your own." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:107 +#: ../../../docs/configuring-playbook-turn.md:58 msgid "If you have or want to enable Jitsi, you might want to enable the TURN server there too. If you do not do it, Jitsi will fall back to an upstream service." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:114 +#: ../../../docs/configuring-playbook-turn.md:65 msgid "You can put multiple host/port combinations if you'd like to." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:116 -msgid "Edit the reloading schedule (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:118 -msgid "By default the service is reloaded on 6:30 a.m. every day based on the `coturn_reload_schedule` variable so that new SSL certificates can kick in. It is defined in the format of systemd timer calendar." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:120 -msgid "To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs):" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:126 -msgid "**Note**: the actual job may run with a delay. See `coturn_reload_schedule_randomized_delay_sec` for its default value." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:128 +#: ../../../docs/configuring-playbook-turn.md:67 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:130 +#: ../../../docs/configuring-playbook-turn.md:69 msgid "There are some additional things you may wish to configure about the TURN server." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:132 +#: ../../../docs/configuring-playbook-turn.md:71 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:134 -msgid "`roles/galaxy/coturn/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +#: ../../../docs/configuring-playbook-turn.md:73 +msgid "`roles/custom/matrix-coturn/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:136 +#: ../../../docs/configuring-playbook-turn.md:75 msgid "Disabling coturn" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:138 -msgid "Coturn is only enabled by default when [Jitsi](configuring-playbook-jitsi.md) is enabled. In most instances, you don't need to explicitly disable it." +#: ../../../docs/configuring-playbook-turn.md:77 +msgid "If, for some reason, you'd like for the playbook to not install coturn (or to uninstall it if it was previously installed), add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:140 -msgid "To force the playbook to not install Coturn (even when Jitsi is enabled), add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-turn.md:83 +msgid "In that case, Synapse would not point to any coturn servers and audio/video call functionality may fail." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:146 +#: ../../../docs/configuring-playbook-turn.md:85 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:148 +#: ../../../docs/configuring-playbook-turn.md:87 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:155 +#: ../../../docs/configuring-playbook-turn.md:94 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:157 +#: ../../../docs/configuring-playbook-turn.md:96 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:159 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:161 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-coturn`." -msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-well-known.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-well-known.po index 742bd19be..5645eafca 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-well-known.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-well-known.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,240 +18,240 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/configuring-well-known.md:14 +#: ../../../docs/configuring-well-known.md:1 msgid "Configuring Service Discovery via .well-known" msgstr "" -#: ../../../docs/configuring-well-known.md:16 +#: ../../../docs/configuring-well-known.md:3 msgid "This documentation page explains how to configure Service discovery via `/.well-known/` files. Service discovery is a way for the Matrix network to discover where a Matrix server is." msgstr "" -#: ../../../docs/configuring-well-known.md:18 +#: ../../../docs/configuring-well-known.md:5 msgid "Types of well-known service discovery mechanism" msgstr "" -#: ../../../docs/configuring-well-known.md:20 +#: ../../../docs/configuring-well-known.md:7 msgid "There are 3 types of well-known service discovery mechanism that Matrix makes use of:" msgstr "" -#: ../../../docs/configuring-well-known.md:22 +#: ../../../docs/configuring-well-known.md:9 msgid "(important) **Federation Server discovery** (`/.well-known/matrix/server`) — assists other servers in the Matrix network with finding your server. With the default playbook configuration specified on the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), this is necessary for federation to work. Without a proper configuration, your server will effectively not be part of the Matrix network." msgstr "" -#: ../../../docs/configuring-well-known.md:24 +#: ../../../docs/configuring-well-known.md:11 msgid "(less important) **Client Server discovery** (`/.well-known/matrix/client`) — assists programs that you use to connect to your server (e.g. Element Web), so that they can make it more convenient for you by automatically configuring the \"Homeserver URL\" and \"Identity Server URL\" addresses." msgstr "" -#: ../../../docs/configuring-well-known.md:26 +#: ../../../docs/configuring-well-known.md:13 msgid "(optional) **Support service discovery** (`/.well-known/matrix/support`) — returns server admin contact and support page of the domain." msgstr "" -#: ../../../docs/configuring-well-known.md:28 +#: ../../../docs/configuring-well-known.md:15 msgid "Federation Server Discovery" msgstr "" -#: ../../../docs/configuring-well-known.md:30 +#: ../../../docs/configuring-well-known.md:17 msgid "All services created by this playbook are meant to be installed on their own server (such as `matrix.example.com`), instead of the base domain (`example.com`)." msgstr "" -#: ../../../docs/configuring-well-known.md:32 +#: ../../../docs/configuring-well-known.md:19 msgid "As [per the Server-Server specification](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), in order to use a short Matrix user ID like `@alice:example.com` instead of `@alice:matrix.example.com` while hosting services on a subdomain such as `matrix.example.com`, the Matrix network needs to be instructed of [server delegation](howto-server-delegation.md) / redirection." msgstr "" -#: ../../../docs/configuring-well-known.md:34 +#: ../../../docs/configuring-well-known.md:21 msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file." msgstr "" -#: ../../../docs/configuring-well-known.md:36 +#: ../../../docs/configuring-well-known.md:23 msgid "If you set up the DNS SRV record for server delegation instead, take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)" msgstr "" -#: ../../../docs/configuring-well-known.md:38 +#: ../../../docs/configuring-well-known.md:25 msgid "Client Server Discovery" msgstr "" -#: ../../../docs/configuring-well-known.md:40 +#: ../../../docs/configuring-well-known.md:27 msgid "Client Server Service discovery lets various client programs which support it, to receive a full user ID (e.g. `@alice:example.com`) and determine where the Matrix server is automatically (e.g. `https://matrix.example.com`)." msgstr "" -#: ../../../docs/configuring-well-known.md:42 +#: ../../../docs/configuring-well-known.md:29 msgid "This lets you (and your users) easily connect to your Matrix server without having to customize connection URLs. When using client programs that support it, you won't need to point them to `https://matrix.example.com` in Custom Server options manually anymore. The connection URL would be discovered automatically from your full username." msgstr "" -#: ../../../docs/configuring-well-known.md:44 +#: ../../../docs/configuring-well-known.md:31 msgid "Without /.well-known/matrix/client, the client will make the wrong \"homeserver URL\" assumption (it will default to using https://example.com, and users will need to notice and adjust it manually (changing it to https://matrix.example.com)." msgstr "" -#: ../../../docs/configuring-well-known.md:46 +#: ../../../docs/configuring-well-known.md:33 msgid "As [per the Client-Server specification](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery) Matrix does Client Server service discovery using a `/.well-known/matrix/client` file hosted on the base domain (e.g. `example.com`)." msgstr "" -#: ../../../docs/configuring-well-known.md:48 +#: ../../../docs/configuring-well-known.md:35 msgid "However, this playbook installs your Matrix server on another domain (e.g. `matrix.example.com`) and not on the base domain (e.g. `example.com`), so it takes a little extra manual effort to set up the file." msgstr "" -#: ../../../docs/configuring-well-known.md:50 +#: ../../../docs/configuring-well-known.md:37 msgid "Support Service Discovery (optional)" msgstr "" -#: ../../../docs/configuring-well-known.md:52 +#: ../../../docs/configuring-well-known.md:39 msgid "[MSC 1929](https://github.com/matrix-org/matrix-spec-proposals/pull/1929), which was added to [Matrix Specification version v1.10](https://spec.matrix.org/v1.10/client-server-api/#getwell-knownmatrixsupport), specifies a way to add contact details of admins, as well as a link to a support page for users who are having issues with the service. Automated services may also index this information and use it for abuse reports, etc." msgstr "" -#: ../../../docs/configuring-well-known.md:54 +#: ../../../docs/configuring-well-known.md:41 msgid "To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-well-known.md:75 +#: ../../../docs/configuring-well-known.md:62 msgid "Installing well-known files on the base domain's server" msgstr "" -#: ../../../docs/configuring-well-known.md:77 +#: ../../../docs/configuring-well-known.md:64 msgid "To implement the service discovery mechanisms, your base domain's server (e.g. `example.com`) needs to run an HTTPS-capable webserver." msgstr "" -#: ../../../docs/configuring-well-known.md:79 +#: ../../../docs/configuring-well-known.md:66 msgid "Serving the base domain from the Matrix server via the playbook" msgstr "" -#: ../../../docs/configuring-well-known.md:81 +#: ../../../docs/configuring-well-known.md:68 msgid "If you don't have a server for your base domain at all, you can use the Matrix server for this. If you don't need the base domain (e.g. `example.com`) for anything else (hosting a website, etc.), you can point it to the Matrix server's IP address and tell the playbook to configure it." msgstr "" -#: ../../../docs/configuring-well-known.md:83 +#: ../../../docs/configuring-well-known.md:70 msgid "**This is the easiest way to set up well-known serving** — letting the playbook handle the whole base domain for you (including SSL certificates, etc.) and take care to serve the appropriate well-known files automatically." msgstr "" -#: ../../../docs/configuring-well-known.md:85 +#: ../../../docs/configuring-well-known.md:72 msgid "If you decide to go this route, you don't need to read ahead in this document. Instead, go to [Serving the base domain](configuring-playbook-base-domain-serving.md) to learn how the playbook can help you set it up." msgstr "" -#: ../../../docs/configuring-well-known.md:87 +#: ../../../docs/configuring-well-known.md:74 msgid "However, if you need to use the base domain for other things, this method is less suitable than the one explained below." msgstr "" -#: ../../../docs/configuring-well-known.md:89 +#: ../../../docs/configuring-well-known.md:76 msgid "Manually installing well-known files on the base domain's server" msgstr "" -#: ../../../docs/configuring-well-known.md:91 +#: ../../../docs/configuring-well-known.md:78 msgid "If you're managing the base domain by yourself somehow, you'll need to set up serving of some `/.well-known/matrix/*` files from it via HTTPS." msgstr "" -#: ../../../docs/configuring-well-known.md:93 +#: ../../../docs/configuring-well-known.md:80 msgid "To make things easy for you to set up, this playbook generates and hosts a few well-known files on the Matrix domain's server. The files are generated at the `/matrix/static-files/public/.well-known/matrix/` path on the server and hosted at URLs like `https://matrix.example.com/.well-known/matrix/server` and `https://matrix.example.com/.well-known/matrix/client`, even though this is the wrong place to host them." msgstr "" -#: ../../../docs/configuring-well-known.md:95 +#: ../../../docs/configuring-well-known.md:82 msgid "You have two options when it comes to installing the files on the base domain's server:" msgstr "" -#: ../../../docs/configuring-well-known.md:97 +#: ../../../docs/configuring-well-known.md:84 msgid "(Option 1): **Copying the files manually** to your base domain's server" msgstr "" -#: ../../../docs/configuring-well-known.md:99 +#: ../../../docs/configuring-well-known.md:86 msgid "**Hint**: Option 2 is generally a better way to do this. Make sure to go with it, if possible." msgstr "" -#: ../../../docs/configuring-well-known.md:101 +#: ../../../docs/configuring-well-known.md:88 msgid "All you need to do is:" msgstr "" -#: ../../../docs/configuring-well-known.md:103 +#: ../../../docs/configuring-well-known.md:90 msgid "copy `/.well-known/matrix/server` and `/.well-known/matrix/client` from the Matrix server (e.g. `matrix.example.com`) to your base domain's server (`example.com`). You can find these files in the `/matrix/static-files/.well-known/matrix` directory on the Matrix server. They are also accessible on URLs like this: `https://matrix.example.com/.well-known/matrix/server` (same for `client`)." msgstr "" -#: ../../../docs/configuring-well-known.md:105 +#: ../../../docs/configuring-well-known.md:92 msgid "set up the server at your base domain (e.g. `example.com`) so that it adds an extra HTTP header when serving the `/.well-known/matrix/client` file. [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS), the `Access-Control-Allow-Origin` header should be set with a value of `*`. If you don't do this step, web-based Matrix clients (like Element Web) may fail to work. Setting up headers for the `/.well-known/matrix/server` file is not necessary, as this file is only consumed by non-browsers, which don't care about CORS." msgstr "" -#: ../../../docs/configuring-well-known.md:107 +#: ../../../docs/configuring-well-known.md:94 msgid "This is relatively easy to do and possibly your only choice if you can only host static files from the base domain's server. It is, however, **a little fragile**, as future updates performed by this playbook may regenerate the well-known files and you may need to notice that and copy them over again." msgstr "" -#: ../../../docs/configuring-well-known.md:109 +#: ../../../docs/configuring-well-known.md:96 msgid "(Option 2): **Setting up reverse-proxying** of the well-known files from the base domain's server to the Matrix server" msgstr "" -#: ../../../docs/configuring-well-known.md:111 +#: ../../../docs/configuring-well-known.md:98 msgid "This option is less fragile and generally better." msgstr "" -#: ../../../docs/configuring-well-known.md:113 -msgid "On the base domain's server (e.g. `example.com`), you can set up reverse-proxying (or simply a 302 redirect), so that any access for the `/.well-known/matrix` location prefix is forwarded to the Matrix domain's server (e.g. `matrix.example.com`)." +#: ../../../docs/configuring-well-known.md:100 +msgid "On the base domain's server (e.g. `example.com`), you can set up reverse-proxying, so that any access for the `/.well-known/matrix` location prefix is forwarded to the Matrix domain's server (e.g. `matrix.example.com`)." msgstr "" -#: ../../../docs/configuring-well-known.md:115 +#: ../../../docs/configuring-well-known.md:102 msgid "With this method, you **don't need** to add special HTTP headers for [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) reasons (like `Access-Control-Allow-Origin`), because your Matrix server (where requests ultimately go) will be configured by this playbook correctly." msgstr "" -#: ../../../docs/configuring-well-known.md:117 +#: ../../../docs/configuring-well-known.md:104 msgid "**For nginx**, it would be something like this:" msgstr "" -#: ../../../docs/configuring-well-known.md:134 +#: ../../../docs/configuring-well-known.md:121 msgid "**For Apache2**, it would be something like this:" msgstr "" -#: ../../../docs/configuring-well-known.md:148 +#: ../../../docs/configuring-well-known.md:135 msgid "**For Caddy 2**, it would be something like this:" msgstr "" -#: ../../../docs/configuring-well-known.md:158 +#: ../../../docs/configuring-well-known.md:145 msgid "**For HAProxy**, it would be something like this:" msgstr "" -#: ../../../docs/configuring-well-known.md:177 +#: ../../../docs/configuring-well-known.md:164 msgid "**For Netlify**, configure a [redirect](https://docs.netlify.com/routing/redirects/) using a `_redirects` file in the [publish directory](https://docs.netlify.com/configure-builds/overview/#definitions) with contents like this:" msgstr "" -#: ../../../docs/configuring-well-known.md:183 +#: ../../../docs/configuring-well-known.md:170 msgid "**For AWS CloudFront**" msgstr "" -#: ../../../docs/configuring-well-known.md:185 +#: ../../../docs/configuring-well-known.md:172 msgid "Add a custom origin with matrix.example.com to your distribution" msgstr "" -#: ../../../docs/configuring-well-known.md:186 +#: ../../../docs/configuring-well-known.md:173 msgid "Add two behaviors, one for `.well-known/matrix/client` and one for `.well-known/matrix/server` and point them to your new origin." msgstr "" -#: ../../../docs/configuring-well-known.md:188 +#: ../../../docs/configuring-well-known.md:175 msgid "Make sure to:" msgstr "" -#: ../../../docs/configuring-well-known.md:190 +#: ../../../docs/configuring-well-known.md:177 msgid "**replace `example.com`** in the server configuration with your actual domain name" msgstr "" -#: ../../../docs/configuring-well-known.md:191 +#: ../../../docs/configuring-well-known.md:178 msgid "and: to **do this for the HTTPS-enabled server block**, as that's where Matrix expects the file to be" msgstr "" -#: ../../../docs/configuring-well-known.md:193 +#: ../../../docs/configuring-well-known.md:180 msgid "Confirming it works" msgstr "" -#: ../../../docs/configuring-well-known.md:195 +#: ../../../docs/configuring-well-known.md:182 msgid "No matter which method you've used to set up the well-known files, if you've done it correctly you should be able to see a JSON file at these URLs:" msgstr "" -#: ../../../docs/configuring-well-known.md:197 +#: ../../../docs/configuring-well-known.md:184 msgid "`https://example.com/.well-known/matrix/server`" msgstr "" -#: ../../../docs/configuring-well-known.md:198 +#: ../../../docs/configuring-well-known.md:185 msgid "`https://example.com/.well-known/matrix/client`" msgstr "" -#: ../../../docs/configuring-well-known.md:199 +#: ../../../docs/configuring-well-known.md:186 msgid "`https://example.com/.well-known/matrix/support`" msgstr "" -#: ../../../docs/configuring-well-known.md:201 -msgid "You can also check if everything is configured correctly, by [checking if services work](maintenance-and-troubleshooting.md#how-to-check-if-services-work)." +#: ../../../docs/configuring-well-known.md:188 +msgid "You can also check if everything is configured correctly, by [checking if services work](maintenance-checking-services.md)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/faq.po b/i18n/locales/jp/LC_MESSAGES/docs/faq.po index 785cd316a..838d20149 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/faq.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/faq.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,824 +18,876 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/faq.md:13 +#: ../../../docs/faq.md:1 msgid "Frequently Asked Questions" msgstr "" -#: ../../../docs/faq.md:15 +#: ../../../docs/faq.md:3 msgid "This documentation page tries to answer various Frequently Asked Questions about all things [Matrix](https://matrix.org/), with a focus on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work))." msgstr "" -#: ../../../docs/faq.md:17 +#: ../../../docs/faq.md:5 msgid "This FAQ page does not intend to replace the [matrix.org FAQ](https://matrix.org/faq/) (please see that one too)." msgstr "" -#: ../../../docs/faq.md:19 +#: ../../../docs/faq.md:7 msgid "We've only started this FAQ recently, so it's still somewhat empty." msgstr "" -#: ../../../docs/faq.md:21 +#: ../../../docs/faq.md:9 msgid "Also, we encourage you to not dig yourself into a hole by reading way too much. When you've heard enough, proceed to installation. To get started, see [below](#how-do-i-run-the-installation) about our installation guides." msgstr "" -#: ../../../docs/faq.md:23 +#: ../../../docs/faq.md:11 msgid "Introductory" msgstr "" -#: ../../../docs/faq.md:25 +#: ../../../docs/faq.md:13 msgid "Where do I find more questions and answers about Matrix?" msgstr "" -#: ../../../docs/faq.md:27 +#: ../../../docs/faq.md:15 msgid "This is a Frequently Asked Questions page focused on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work)) for deploying a [Matrix](https://matrix.org/) server." msgstr "" -#: ../../../docs/faq.md:29 +#: ../../../docs/faq.md:17 msgid "For a lot more generic questions and answers, see the [matrix.org FAQ](https://matrix.org/faq/)." msgstr "" -#: ../../../docs/faq.md:31 +#: ../../../docs/faq.md:19 msgid "What is Matrix? What is Element? What is Synapse? Why are you confusing me with so many terms?" msgstr "" -#: ../../../docs/faq.md:33 +#: ../../../docs/faq.md:21 msgid "[Matrix](https://matrix.org/) is a new type of realtime communication (chat) network, the closest analogy to which is probably \"email\"." msgstr "" -#: ../../../docs/faq.md:35 +#: ../../../docs/faq.md:23 msgid "You don't just use the \"email\" protocols (SMTP, POP3, IMAP) directly though. There's a *server* somewhere which stores your data (`@gmail.com`, `@yahoo.com`, `@hotmail.com`, `@your-company.com`) and you access it by using these \"email\" protocols via some *client* program (Outlook, Thunderbird, some website, etc)." msgstr "" -#: ../../../docs/faq.md:37 +#: ../../../docs/faq.md:25 msgid "In the world of the Matrix chat protocol, there are various client programs. The first and currently most full-featured one is called [Element](https://element.io/) (used to be called Riot.im and Vector.im in the past). There are [many other clients](https://matrix.org/clients/). You can switch clients as much as you want until you find the one that is right for you on a given platform (you may use Element Desktop on your desktop, but Fluffychat on your phone, etc)." msgstr "" -#: ../../../docs/faq.md:39 +#: ../../../docs/faq.md:27 msgid "Matrix is also like email due to the fact that there are many servers around the world which can all talk to each other (you can send email from `@gmail.com` addresses to `@yahoo.com` and `@hotmail.com` addresses). It's the same with Matrix (`@bob:example.com` can talk to `@alice:example.org`)." msgstr "" -#: ../../../docs/faq.md:41 +#: ../../../docs/faq.md:29 msgid "If someone else is hosting your Matrix server (you being `@alice:matrix.org` or some other public server like this), all you need is a Matrix client program, like Element Web or Element X Android." msgstr "" -#: ../../../docs/faq.md:43 +#: ../../../docs/faq.md:31 msgid "If you'd like to host your own server (you being `@alice:example.com`), you'd need to set up a Matrix server program, like Synapse." msgstr "" -#: ../../../docs/faq.md:45 +#: ../../../docs/faq.md:33 msgid "In short:" msgstr "" -#: ../../../docs/faq.md:47 +#: ../../../docs/faq.md:35 msgid "Matrix is the protocol — a set of rules about how the chat network operates" msgstr "" -#: ../../../docs/faq.md:48 +#: ../../../docs/faq.md:36 msgid "Element is a client program you can use to participate on the Matrix chat network via some server (yours or someone else's). There are also [many other client programs](https://matrix.org/clients/)." msgstr "" -#: ../../../docs/faq.md:49 +#: ../../../docs/faq.md:37 msgid "Synapse is a server program you can use to host your very own Matrix server." msgstr "" -#: ../../../docs/faq.md:51 +#: ../../../docs/faq.md:39 msgid "This FAQ here mostly focuses on installing various Matrix services using the Ansible automation tool. You can learn much more about Matrix in the [matrix.org FAQ](https://matrix.org/faq/)." msgstr "" -#: ../../../docs/faq.md:53 +#: ../../../docs/faq.md:41 msgid "People I wish to talk to are not on Matrix. Can I talk to them?" msgstr "" -#: ../../../docs/faq.md:55 +#: ../../../docs/faq.md:43 msgid "You most likely can. Besides Matrix-native chats, Matrix also supports the concept of \"bridging\", which allows you to plug other networks into it." msgstr "" -#: ../../../docs/faq.md:57 +#: ../../../docs/faq.md:45 msgid "This Ansible playbook can help you install [tens of bridges for various networks](configuring-playbook.md#bridging-other-networks)." msgstr "" -#: ../../../docs/faq.md:59 +#: ../../../docs/faq.md:47 msgid "Besides setting up your own bridges (preferable), you can also use some [public bridges hosted by others](https://publiclist.anchel.nl/#bridges)." msgstr "" -#: ../../../docs/faq.md:61 +#: ../../../docs/faq.md:49 msgid "How do I get started with Matrix?" msgstr "" -#: ../../../docs/faq.md:63 +#: ../../../docs/faq.md:51 msgid "One of [Matrix](https://matrix.org/)'s distinguishing strengths (compared to other chat networks) is its decentralized nature. There's not just one entity (company, organization) controlling the servers. Rather there's thousands of servers operated by different people — one server being insecure, slow or disrespective toward its users does not affect the rest of the network. To participate in that decentralization in its fullest, consider hosting your own server or using some public server other than the largest/default one (`matrix.org`)." msgstr "" -#: ../../../docs/faq.md:65 +#: ../../../docs/faq.md:53 msgid "There are 3 ways to get into Matrix, depending on your technical ability and needs:" msgstr "" -#: ../../../docs/faq.md:67 +#: ../../../docs/faq.md:55 msgid "**using the existing default server** — the easiest way is to use an existing server. The largest public Matrix server is `matrix.org` and it's configured as a default server in clients such as [Element Web](https://app.element.io) and many others. Just use Element Web on the browser via that link (or [download client apps for your Desktop or smartphone](https://element.io/app-for-productivity)), create an account and start chatting." msgstr "" -#: ../../../docs/faq.md:69 +#: ../../../docs/faq.md:57 msgid "**using some other server** — instead of using the largest public server (`matrix.org`), you can use another public one. Here's a [list of public Matrix servers](https://joinmatrix.org/servers/) to choose from. Go to [Element Web](https://app.element.io) or download [some other client](https://matrix.org/clients/) of your choosing and adjust the homeserver URL during login." msgstr "" -#: ../../../docs/faq.md:71 +#: ../../../docs/faq.md:59 msgid "**using your own server** — running your own server puts you in ultimate control of your data. It also lets you have your own user IDs (e.g. `@bob:example.com`). See [How do I set up my own Matrix server](#how-do-i-set-up-my-own-matrix-server)." msgstr "" -#: ../../../docs/faq.md:73 +#: ../../../docs/faq.md:61 msgid "How do I set up my own Matrix server?" msgstr "" -#: ../../../docs/faq.md:75 +#: ../../../docs/faq.md:63 msgid "Normally, you'd first choose the [Matrix](https://matrix.org/) server software you'd like to run. At the time of this writing (January/2021), there's only one fully-featured server program, so there's only one reasonable choice. That's [Synapse](https://github.com/element-hq/synapse)." msgstr "" -#: ../../../docs/faq.md:77 +#: ../../../docs/faq.md:65 msgid "There are [many guides about installing Synapse](https://matrix.org/docs/guides/#installing-synapse). Using this Ansible playbook is just one way of doing it." msgstr "" -#: ../../../docs/faq.md:79 +#: ../../../docs/faq.md:67 msgid "Naturally, we're biased, so our usual recommendation is to go with this [Ansible](https://www.ansible.com/) playbook, instead of installing Synapse (and many many other things around it) manually." msgstr "" -#: ../../../docs/faq.md:81 +#: ../../../docs/faq.md:69 msgid "To get started with the playbook, check out the [Quick start](quick-start.md) or full installation guide (starting at the [Prerequisites](prerequisites.md) page)." msgstr "" -#: ../../../docs/faq.md:83 +#: ../../../docs/faq.md:71 msgid "What is Ansible? How does it work?" msgstr "" -#: ../../../docs/faq.md:85 +#: ../../../docs/faq.md:73 msgid "[Ansible](https://www.ansible.com/) is an automation program. This \"playbook\" is a collection of tasks/scripts that will set up a [Matrix](https://matrix.org/) server for you, so you don't have to perform these tasks manually." msgstr "" -#: ../../../docs/faq.md:87 +#: ../../../docs/faq.md:75 msgid "We have written these automated tasks for you and all you need to do is execute them using the Ansible program." msgstr "" -#: ../../../docs/faq.md:89 +#: ../../../docs/faq.md:77 msgid "You can install Ansible and this playbook code repository on your own computer and tell it to install Matrix services at the server living at `matrix.example.com`. We recommend installing Ansible on your own computer." msgstr "" -#: ../../../docs/faq.md:91 +#: ../../../docs/faq.md:79 msgid "Alternatively, you can download Ansible and the playbook itself directly on the `matrix.example.com` server." msgstr "" -#: ../../../docs/faq.md:93 +#: ../../../docs/faq.md:81 msgid "To learn more, see our [dedicated Ansible documentation page](ansible.md)." msgstr "" -#: ../../../docs/faq.md:95 +#: ../../../docs/faq.md:83 msgid "What is `just`?" msgstr "" -#: ../../../docs/faq.md:97 +#: ../../../docs/faq.md:85 msgid "[`just`](https://github.com/casey/just) is a modern command-runner alternative to [make](https://www.gnu.org/software/make/). It can be used to invoke commands with less typing." msgstr "" -#: ../../../docs/faq.md:99 +#: ../../../docs/faq.md:87 msgid "The `just` utility executes shortcut commands (called \"recipes\"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile)." msgstr "" -#: ../../../docs/faq.md:101 +#: ../../../docs/faq.md:89 msgid "For details about `just` commands, take a look at: [Running `just` commands](just.md)." msgstr "" -#: ../../../docs/faq.md:103 +#: ../../../docs/faq.md:91 msgid "The playbook also contains a `Makefile` for the `make` tool, but most of the just recipes are not available as targets in the `Makefile`." msgstr "" -#: ../../../docs/faq.md:105 +#: ../../../docs/faq.md:93 msgid "Why use this playbook and not install Synapse and other things manually?" msgstr "" -#: ../../../docs/faq.md:107 +#: ../../../docs/faq.md:95 msgid "There are various guides telling you how easy it is to install [Synapse](https://github.com/element-hq/synapse)." msgstr "" -#: ../../../docs/faq.md:109 +#: ../../../docs/faq.md:97 msgid "Reading the documentation of this Ansible playbook, you may also be thinking:" msgstr "" -#: ../../../docs/faq.md:111 +#: ../../../docs/faq.md:99 msgid "I don't know what [Ansible](https://www.ansible.com/) is. I don't know what [Docker](https://www.docker.com/) is. This looks more complicated." msgstr "" -#: ../../../docs/faq.md:113 +#: ../../../docs/faq.md:101 msgid "… so you may be leaning toward [installing Synapse manually](https://github.com/element-hq/synapse/blob/master/INSTALL.md)." msgstr "" -#: ../../../docs/faq.md:115 +#: ../../../docs/faq.md:103 msgid "The problem with a manual installation is:" msgstr "" -#: ../../../docs/faq.md:117 +#: ../../../docs/faq.md:105 msgid "Synapse is written in Python. If not packaged for your distribution, you'd need to install various Python modules, etc., and keep them updated." msgstr "" -#: ../../../docs/faq.md:118 +#: ../../../docs/faq.md:106 msgid "Synapse requires a [Postgres](https://www.postgresql.org/) database (it can run on SQLite, but that's very much discouraged). So you'd need to install Postgres as well." msgstr "" -#: ../../../docs/faq.md:119 +#: ../../../docs/faq.md:107 msgid "you may also need a reverse-proxy server in front of it (nginx, Apache), so you'd need to be familiar with that" msgstr "" -#: ../../../docs/faq.md:120 +#: ../../../docs/faq.md:108 msgid "SSL is required, so you'd need to obtain Let's Encrypt (or other free or non-free) certificates for one or more domain names. You'd need to be familiar with [certbot](https://certbot.eff.org/) (when using Let's Encrypt) or similar software." msgstr "" -#: ../../../docs/faq.md:121 +#: ../../../docs/faq.md:109 msgid "for each additional component you'd like to add (client like [Element](https://element.io), bridge to some other chat network, integration manager (stickers, other services, Identity Manager, etc.), you'll need to spend extra time installing and wiring it with the rest of the system in a way that works." msgstr "" -#: ../../../docs/faq.md:122 +#: ../../../docs/faq.md:110 msgid "you'll likely get slower updates for all of these components, depending on your distro packaging or your own time and ability" msgstr "" -#: ../../../docs/faq.md:124 +#: ../../../docs/faq.md:112 msgid "The playbook, on the other hand, installs a bunch of components for you by default, obtains SSL certificates for you, etc. If you'd like, you can enable various bridges and other services with very little effort. All the components are wired to work together." msgstr "" -#: ../../../docs/faq.md:126 +#: ../../../docs/faq.md:114 msgid "All services run in Docker containers (most being officially provided by each component's developers), so we're not at the mercy of distro packaging." msgstr "" -#: ../../../docs/faq.md:128 +#: ../../../docs/faq.md:116 msgid "Why use this playbook and not just use the Docker image directly?" msgstr "" -#: ../../../docs/faq.md:130 +#: ../../../docs/faq.md:118 msgid "Reasons are similar to the reasons for not installing manually." msgstr "" -#: ../../../docs/faq.md:132 +#: ../../../docs/faq.md:120 msgid "Besides Synapse, you'd need other things — a Postgres database, likely the [Element](https://element.io) client, etc., etc." msgstr "" -#: ../../../docs/faq.md:134 +#: ../../../docs/faq.md:122 msgid "Using the playbook, you get all these components in a way that works well together out of the box." msgstr "" -#: ../../../docs/faq.md:136 +#: ../../../docs/faq.md:124 msgid "Occasionally I see some people are talking about \"MDAD\". What is it?" msgstr "" -#: ../../../docs/faq.md:138 +#: ../../../docs/faq.md:126 msgid "It is the acronym of us: **m**atrix-**d**ocker-**a**nsible-**d**eploy." msgstr "" -#: ../../../docs/faq.md:140 +#: ../../../docs/faq.md:128 msgid "What's different about this Ansible playbook compared to [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy)?" msgstr "" -#: ../../../docs/faq.md:142 +#: ../../../docs/faq.md:130 msgid "This is similar to the [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy) Ansible deployment, but:" msgstr "" -#: ../../../docs/faq.md:144 +#: ../../../docs/faq.md:132 msgid "this one is a complete Ansible playbook (instead of just a role), so it's **easier to run** — especially for folks not familiar with Ansible" msgstr "" -#: ../../../docs/faq.md:146 +#: ../../../docs/faq.md:134 msgid "this one installs and hooks together **a lot more Matrix-related services** for you (see above)" msgstr "" -#: ../../../docs/faq.md:148 +#: ../../../docs/faq.md:136 msgid "this one **can be executed more than once** without causing trouble" msgstr "" -#: ../../../docs/faq.md:150 +#: ../../../docs/faq.md:138 msgid "works on various distros: **CentOS** (7.0+), Debian-based distributions (**Debian** 10/Buster+, **Ubuntu** 18.04+), **Archlinux**" msgstr "" -#: ../../../docs/faq.md:152 +#: ../../../docs/faq.md:140 msgid "this one installs everything in a single directory (`/matrix` by default) and **doesn't \"contaminate\" your server** with files all over the place" msgstr "" -#: ../../../docs/faq.md:154 +#: ../../../docs/faq.md:142 msgid "this one **doesn't necessarily take over** ports 80 and 443. By default, it sets up [Traefik](https://doc.traefik.io/traefik/) for you there, but you can also [use your own webserver](configuring-playbook-own-webserver.md)" msgstr "" -#: ../../../docs/faq.md:156 +#: ../../../docs/faq.md:144 msgid "this one **runs everything in Docker containers**, so it's likely more predictable and less fragile (see [Docker images used by this playbook](container-images.md))" msgstr "" -#: ../../../docs/faq.md:158 +#: ../../../docs/faq.md:146 msgid "this one retrieves and automatically renews free [Let's Encrypt](https://letsencrypt.org/) **SSL certificates** for you" msgstr "" -#: ../../../docs/faq.md:160 +#: ../../../docs/faq.md:148 msgid "this one optionally can store the `media_store` content repository files on [Amazon S3](https://aws.amazon.com/s3/) (but defaults to storing files on the server's filesystem)" msgstr "" -#: ../../../docs/faq.md:162 +#: ../../../docs/faq.md:150 msgid "this one optionally **allows you to use an external PostgreSQL server** for Synapse's database (but defaults to running one in a container)" msgstr "" -#: ../../../docs/faq.md:164 +#: ../../../docs/faq.md:152 msgid "helps you **import data from a previous installation** (so you can migrate your manual virtualenv/Docker setup to a more managed one)" msgstr "" -#: ../../../docs/faq.md:166 +#: ../../../docs/faq.md:154 msgid "this one is actually **maintained**" msgstr "" -#: ../../../docs/faq.md:168 +#: ../../../docs/faq.md:156 msgid "Server-related" msgstr "" -#: ../../../docs/faq.md:170 +#: ../../../docs/faq.md:158 msgid "What kind of server do I need to install Matrix using this Ansible playbook?" msgstr "" -#: ../../../docs/faq.md:172 +#: ../../../docs/faq.md:160 msgid "We list our server requirements in [Prerequisites](prerequisites.md)." msgstr "" -#: ../../../docs/faq.md:174 +#: ../../../docs/faq.md:162 msgid "Why not run Matrix on Kubernetes?" msgstr "" -#: ../../../docs/faq.md:176 +#: ../../../docs/faq.md:164 msgid "There's no reason not to run Matrix on [Kubernetes](https://kubernetes.io/)." msgstr "" -#: ../../../docs/faq.md:178 +#: ../../../docs/faq.md:166 msgid "However, that's overly complicated for thousands of us who just want to run a single small (and sometimes not so small) Matrix server, either using \"cloud\" servers or even a [Raspberry Pi](https://www.raspberrypi.org/) at home." msgstr "" -#: ../../../docs/faq.md:180 +#: ../../../docs/faq.md:168 msgid "For us, a Kubernetes-based setup which requires a cluster of multiple computers and is more technically-involved is a no-go." msgstr "" -#: ../../../docs/faq.md:182 +#: ../../../docs/faq.md:170 msgid "There are others working on automating a Matrix-on-Kubernetes setup, such as this [Helm](https://helm.sh/) chart: https://github.com/dacruz21/matrix-chart." msgstr "" -#: ../../../docs/faq.md:184 +#: ../../../docs/faq.md:172 msgid "Why don't you use Podman instead of Docker?" msgstr "" -#: ../../../docs/faq.md:186 +#: ../../../docs/faq.md:174 msgid "We like the philosophy of a daemonless container runtime, but [Podman](https://podman.io) is just not ready for our use case yet." msgstr "" -#: ../../../docs/faq.md:188 +#: ../../../docs/faq.md:176 msgid "Learn more about our past experiences/attempts to give Podman a chance, by reading [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/520)." msgstr "" -#: ../../../docs/faq.md:190 +#: ../../../docs/faq.md:178 msgid "In short, `alias podman=docker` is a lie (for us)." msgstr "" -#: ../../../docs/faq.md:192 +#: ../../../docs/faq.md:180 msgid "Why use Docker?" msgstr "" -#: ../../../docs/faq.md:194 +#: ../../../docs/faq.md:182 msgid "[Docker](https://www.docker.com/) is one of our 2 hard dependencies (the other one being [systemd](https://systemd.io/))." msgstr "" -#: ../../../docs/faq.md:196 +#: ../../../docs/faq.md:184 msgid "It lets us run services in an isolated manner and independently of the (usually old) packages available for distributions." msgstr "" -#: ../../../docs/faq.md:198 +#: ../../../docs/faq.md:186 msgid "It also lets us have a unified setup which runs the same across various supported distros (see them on [Prerequisites](prerequisites.md))." msgstr "" -#: ../../../docs/faq.md:200 +#: ../../../docs/faq.md:188 msgid "Is Docker a hard requirement?" msgstr "" -#: ../../../docs/faq.md:202 +#: ../../../docs/faq.md:190 msgid "Yes. See [Why don't you use Podman instead of Docker?](#why-dont-you-use-podman-instead-of-docker) for why we're not using another container runtime." msgstr "" -#: ../../../docs/faq.md:204 +#: ../../../docs/faq.md:192 msgid "All of our services run in containers. It's how we achieve predictability and also how we support tens of different services across lots of distros." msgstr "" -#: ../../../docs/faq.md:206 +#: ../../../docs/faq.md:194 msgid "The only thing we need on the distro is systemd and Python (we install Docker ourselves, unless you ask us not to)." msgstr "" -#: ../../../docs/faq.md:208 +#: ../../../docs/faq.md:196 msgid "Why don't you use docker-compose?" msgstr "" -#: ../../../docs/faq.md:210 +#: ../../../docs/faq.md:198 msgid "Instead of using [docker-compose](https://docs.docker.com/compose/), we prefer installing systemd services and scheduling those independently." msgstr "" -#: ../../../docs/faq.md:212 +#: ../../../docs/faq.md:200 msgid "There are people who have worked on turning this setup into a docker-compose-based one. See these experiments [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/64#issuecomment-603164625). There is also a demo project ([element-docker-demo](https://github.com/element-hq/element-docker-demo)) by Element." msgstr "" -#: ../../../docs/faq.md:214 +#: ../../../docs/faq.md:202 msgid "Can I run this on a distro without systemd?" msgstr "" -#: ../../../docs/faq.md:216 +#: ../../../docs/faq.md:204 msgid "No. [systemd](https://systemd.io/) is one of our 2 hard dependencies (the other one being [Docker](https://www.docker.com/))." msgstr "" -#: ../../../docs/faq.md:218 +#: ../../../docs/faq.md:206 msgid "Can I install this on a Raspberry Pi?" msgstr "" -#: ../../../docs/faq.md:220 +#: ../../../docs/faq.md:208 msgid "Yes, you can. See our [Alternative Architectures](alternative-architectures.md) documentation page." msgstr "" -#: ../../../docs/faq.md:222 +#: ../../../docs/faq.md:210 msgid "Whether a Raspberry Pi has enough power to give you a good experience is another question. It depends on your use case." msgstr "" -#: ../../../docs/faq.md:224 +#: ../../../docs/faq.md:212 msgid "Also see: [What kind of server specs do I need?](#what-kind-of-server-specs-do-i-need)." msgstr "" -#: ../../../docs/faq.md:226 +#: ../../../docs/faq.md:214 msgid "What kind of server specs do I need?" msgstr "" -#: ../../../docs/faq.md:228 +#: ../../../docs/faq.md:216 msgid "This largely depends on your use case. It's not so much the number of users that you plan to host, but rather the number of large rooms they will join." msgstr "" -#: ../../../docs/faq.md:230 +#: ../../../docs/faq.md:218 msgid "Federated rooms with lots of history and containing hundreds of other servers are very heavy CPU-wise and memory-wise." msgstr "" -#: ../../../docs/faq.md:232 +#: ../../../docs/faq.md:220 msgid "You can probably use a 1 CPU + 1GB memory server to host hundreds of local users just fine, but as soon as one of them joins a federated room like `#matrix:matrix.org` (Matrix HQ) or some IRC-bridged room (say `##linux`), your server will get the need for a lot more power (at least 2GB RAM, etc)." msgstr "" -#: ../../../docs/faq.md:234 +#: ../../../docs/faq.md:222 msgid "Running Matrix on a server with 1GB of memory is possible (especially if you disable some not-so-important services). See [How do I optimize this setup for a low-power server?](#how-do-i-optimize-this-setup-for-a-low-power-server)." msgstr "" -#: ../../../docs/faq.md:236 +#: ../../../docs/faq.md:224 msgid "**We recommend starting with a server having at least 2GB of memory** and even then using it sparingly. If you know for sure you'll be joining various large rooms, etc., then going for 4GB of memory or more is a good idea." msgstr "" -#: ../../../docs/faq.md:238 -msgid "Besides the regular Matrix stuff, we also support things like video-conferencing using [Jitsi](configuring-playbook-jitsi.md) and other additional services which (when installed) may use up a lot of memory. Things do add up. Besides the Synapse Matrix server, Jitsi is especially notorious for consuming a lot of resources. If you plan on running Jitsi, we recommend a server with at least 2GB of memory (preferably more). See our [Jitsi documentation page](configuring-playbook-jitsi.md) to learn how to optimize its memory/CPU usage." +#: ../../../docs/faq.md:226 +msgid "Besides the regular Matrix stuff, we also support things like video-conferencing using [Jitsi](configuring-playbook-jitsi.md) and other additional services which (when installed) may use up a lot of memory. Things do add up. Besides the Synapse Matrix server, Jitsi is especially notorious for consuming a lot of resources. If you plan on running Jitsi, we recommend a server with at least 2GB of memory (preferrably more). See our [Jitsi documentation page](configuring-playbook-jitsi.md) to learn how to optimize its memory/CPU usage." msgstr "" -#: ../../../docs/faq.md:240 +#: ../../../docs/faq.md:228 msgid "Can I run this in an LXC container?" msgstr "" -#: ../../../docs/faq.md:242 +#: ../../../docs/faq.md:230 msgid "If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container." msgstr "" -#: ../../../docs/faq.md:244 +#: ../../../docs/faq.md:232 msgid "Configuration" msgstr "" -#: ../../../docs/faq.md:246 +#: ../../../docs/faq.md:234 msgid "Why install my server at matrix.example.com and not at the base domain?" msgstr "" -#: ../../../docs/faq.md:248 +#: ../../../docs/faq.md:236 msgid "It's the same with email servers. Your email address is likely `name@company.com`, not `name@mail.company.com`, even though it's `mail.company.com` that is really handling your data for `@company.com` email to work." msgstr "" -#: ../../../docs/faq.md:250 +#: ../../../docs/faq.md:238 msgid "Using a separate domain name is easier to manage (although it's a little hard to get right at first) and keeps your Matrix server isolated from your website (if you have one), from your email server (if you have one), etc. Therefore, this playbook sets up services on your Matrix server (`matrix.example.com`) by default." msgstr "" -#: ../../../docs/faq.md:252 +#: ../../../docs/faq.md:240 msgid "I don't control anything on the base domain and can't set up delegation to matrix.example.com. What do I do?" msgstr "" -#: ../../../docs/faq.md:254 +#: ../../../docs/faq.md:242 msgid "If you're not in control of your base domain (or the server handling it) at all, you can take a look at [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" msgstr "" -#: ../../../docs/faq.md:256 +#: ../../../docs/faq.md:244 msgid "I can't set up HTTPS on the base domain. How will I get Matrix federating?" msgstr "" -#: ../../../docs/faq.md:258 +#: ../../../docs/faq.md:246 msgid "If you really can't obtain an HTTPS certificate for your base domain, you can take a look at [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" msgstr "" -#: ../../../docs/faq.md:260 +#: ../../../docs/faq.md:248 msgid "How do I install on matrix.example.com without involving the base domain?" msgstr "" -#: ../../../docs/faq.md:262 +#: ../../../docs/faq.md:250 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/faq.md:283 +#: ../../../docs/faq.md:271 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/faq.md:290 +#: ../../../docs/faq.md:278 msgid "**Notes**:" msgstr "" -#: ../../../docs/faq.md:292 +#: ../../../docs/faq.md:280 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/faq.md:294 +#: ../../../docs/faq.md:282 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/faq.md:296 +#: ../../../docs/faq.md:284 msgid "Without setting up [server delegation](howto-server-delegation.md) to `matrix.example.com`, your user IDs will be like `@alice:matrix.example.com`. This is equivalent to having an email address like `bob@mail.company.com`, instead of just `bob@company.com`." msgstr "" -#: ../../../docs/faq.md:298 +#: ../../../docs/faq.md:286 msgid "I don't use the base domain for anything. How am I supposed to set up Server Delegation for Matrix services?" msgstr "" -#: ../../../docs/faq.md:300 +#: ../../../docs/faq.md:288 msgid "If you don't use your base domain for anything, then it's hard for you to \"serve files over HTTPS\" on it — something we ask you to do for the [.well-known](configuring-well-known.md) setup (needed for [Server Delegation](howto-server-delegation.md))." msgstr "" -#: ../../../docs/faq.md:302 +#: ../../../docs/faq.md:290 msgid "Luckily, the playbook can set up your Matrix server (at `matrix.example.com`) to also handle traffic for the base domain (`example.com`)." msgstr "" -#: ../../../docs/faq.md:304 +#: ../../../docs/faq.md:292 msgid "See [Serving the base domain](configuring-playbook-base-domain-serving.md)." msgstr "" -#: ../../../docs/faq.md:306 +#: ../../../docs/faq.md:294 msgid "How do I optimize this setup for a low-power server?" msgstr "" -#: ../../../docs/faq.md:308 -msgid "For a low-power server, it's best to use an alternative homeserver implementation (other than [Synapse](configuring-playbook-synapse.md))." +#: ../../../docs/faq.md:296 +msgid "You can disable some not-so-important services to save on memory." msgstr "" -#: ../../../docs/faq.md:310 -msgid "You can disable some not-so-important services to save on memory." +#: ../../../docs/faq.md:318 +msgid "You can also consider implementing a restriction on room complexity, in order to prevent users from joining very heavy rooms:" msgstr "" -#: ../../../docs/faq.md:317 +#: ../../../docs/faq.md:328 msgid "If you've installed [Jitsi](configuring-playbook-jitsi.md) (not installed by default), there are additional optimizations listed on its documentation page that you can perform." msgstr "" -#: ../../../docs/faq.md:320 -msgid "Synapse-specific optimizations" +#: ../../../docs/faq.md:330 +msgid "I already have Docker on my server. Can you stop installing Docker via the playbook?" msgstr "" -#: ../../../docs/faq.md:322 -msgid "If you're using [Synapse](configuring-playbook-synapse.md), you can also consider the following optimizations:" +#: ../../../docs/faq.md:332 +msgid "Yes, we can stop installing Docker ourselves. Just use this in your `vars.yml` file:" msgstr "" -#: ../../../docs/faq.md:332 -msgid "You can also consider [implementing a restriction on room complexity](configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts), in order to prevent users from joining very heavy rooms:" +#: ../../../docs/faq.md:338 +msgid "I run another webserver on the same server where I wish to install Matrix. What now?" msgstr "" #: ../../../docs/faq.md:340 -msgid "I already have Docker on my server. Can you stop installing Docker via the playbook?" +msgid "By default, we install a webserver for you ([Traefik](https://doc.traefik.io/traefik/)), but you can also use [your own webserver](configuring-playbook-own-webserver.md)." msgstr "" #: ../../../docs/faq.md:342 -msgid "Yes, we can stop installing Docker ourselves. Just use this in your `vars.yml` file:" +msgid "How is the effective configuration determined?" +msgstr "" + +#: ../../../docs/faq.md:344 +msgid "Configuration variables are defined in multiple places in this playbook and are considered in this order:" +msgstr "" + +#: ../../../docs/faq.md:346 +msgid "there are defaults coming from each role's defaults file (`role/matrix*/defaults/main.yml`). These variable values aim to be good defaults for when the role is used standalone (outside of this collection of roles, also called playbook)." msgstr "" #: ../../../docs/faq.md:348 -msgid "I run another webserver on the same server where I wish to install Matrix. What now?" +msgid "then, there are overrides in `group_vars/matrix_servers`, which aim to adjust these \"standalone role defaults\" to something which better fits the playbook in its entirety." msgstr "" #: ../../../docs/faq.md:350 -msgid "By default, we install a webserver for you ([Traefik](https://doc.traefik.io/traefik/)), but you can also use [your own webserver](configuring-playbook-own-webserver.md)." +msgid "finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` file, which is the ultimate override" msgstr "" #: ../../../docs/faq.md:352 -msgid "How is the effective configuration determined?" +msgid "What configuration variables are available?" msgstr "" #: ../../../docs/faq.md:354 -msgid "Configuration variables are defined in multiple places in this playbook and are considered in this order:" +msgid "You can discover the variables you can override in each role (`roles/*/*/defaults/main.yml`)." msgstr "" #: ../../../docs/faq.md:356 -msgid "there are defaults coming from each role's defaults file (`role/matrix*/defaults/main.yml`). These variable values aim to be good defaults for when the role is used standalone (outside of this collection of roles, also called playbook)." +msgid "As described in [How is the effective configuration determined?](#how-is-the-effective-configuration-determined), these role-defaults may be overriden by values defined in `group_vars/matrix_servers`." msgstr "" #: ../../../docs/faq.md:358 -msgid "then, there are overrides in `group_vars/matrix_servers`, which aim to adjust these \"standalone role defaults\" to something which better fits the playbook in its entirety." +msgid "Refer to both of these for inspiration. Still, as mentioned in [Configuring the playbook](configuring-playbook.md), you're only ever supposed to edit your own `inventory/host_vars/matrix.example.com/vars.yml` file and nothing else inside the playbook (unless you're meaning to contribute new features)." msgstr "" -#: ../../../docs/faq.md:360 -msgid "finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` file, which is the ultimate override" +#: ../../../docs/faq.md:360 ../../../docs/faq.md:372 +msgid "**Note**: some of the roles (`roles/galaxy/*`) live in separate repositories and are only installed after your run `just roles` (or `make roles`) or `just update` (which automatically does `git pull` and `just roles`)." msgstr "" #: ../../../docs/faq.md:362 -msgid "What configuration variables are available?" +msgid "I'd like to adjust some configuration which doesn't have a corresponding variable. How do I do it?" msgstr "" #: ../../../docs/faq.md:364 -msgid "You can discover the variables you can override in each role (`roles/*/*/defaults/main.yml`)." +msgid "The playbook doesn't aim to expose all configuration settings for all services using variables. Doing so would amount to hundreds of variables that we have to create and maintain." msgstr "" #: ../../../docs/faq.md:366 -msgid "As described in [How is the effective configuration determined?](#how-is-the-effective-configuration-determined), these role-defaults may be overridden by values defined in `group_vars/matrix_servers`." +msgid "Instead, we only try to make some important basics configurable using dedicated variables you can see in each role. See [What configuration variables are available?](#what-configuration-variables-are-available)." msgstr "" #: ../../../docs/faq.md:368 -msgid "Refer to both of these for inspiration. Still, as mentioned in [Configuring the playbook](configuring-playbook.md), you're only ever supposed to edit your own `inventory/host_vars/matrix.example.com/vars.yml` file and nothing else inside the playbook (unless you're meaning to contribute new features)." -msgstr "" - -#: ../../../docs/faq.md:370 ../../../docs/faq.md:382 -msgid "**Note**: some of the roles (`roles/galaxy/*`) live in separate repositories and are only installed after your run `just roles` (or `make roles`) or `just update` (which automatically does `git pull` and `just roles`)." +msgid "Besides that, each role (component) aims to provide a `matrix_SOME_COMPONENT_configuration_extension_yaml` (or `matrix_SOME_COMPONENT_configuration_extension_json`) variable, which can be used to override the configuration." msgstr "" -#: ../../../docs/faq.md:372 -msgid "I'd like to adjust some configuration which doesn't have a corresponding variable. How do I do it?" +#: ../../../docs/faq.md:370 +msgid "Check each role's `roles/*/*/defaults/main.yml` for the corresponding variable and an example for how use it." msgstr "" #: ../../../docs/faq.md:374 -msgid "The playbook doesn't aim to expose all configuration settings for all services using variables. Doing so would amount to hundreds of variables that we have to create and maintain." +msgid "Installation" msgstr "" #: ../../../docs/faq.md:376 -msgid "Instead, we only try to make some important basics configurable using dedicated variables you can see in each role. See [What configuration variables are available?](#what-configuration-variables-are-available)." +msgid "How do I run the installation?" msgstr "" #: ../../../docs/faq.md:378 -msgid "Besides that, each role (component) aims to provide a `matrix_SOME_COMPONENT_configuration_extension_yaml` (or `matrix_SOME_COMPONENT_configuration_extension_json`) variable, which can be used to override the configuration." +msgid "See [Installing](installing.md) to learn how to use Ansible to install Matrix services." msgstr "" #: ../../../docs/faq.md:380 -msgid "Check each role's `roles/*/*/defaults/main.yml` for the corresponding variable and an example for how use it." +msgid "However, we recommend you to follow our installation guide, instead of jumping straight to installing." +msgstr "" + +#: ../../../docs/faq.md:382 +msgid "There are two guides available:" msgstr "" #: ../../../docs/faq.md:384 -msgid "Installation" +msgid "⚡ **[Quick start](quick-start.md)** (for beginners): this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"." msgstr "" #: ../../../docs/faq.md:386 -msgid "How do I run the installation?" +msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide by starting with the **[Prerequisites](prerequisites.md)** documentation page." msgstr "" #: ../../../docs/faq.md:388 -msgid "See [Installing](installing.md) to learn how to use Ansible to install Matrix services." +msgid "I installed Synapse some other way. Can I migrate such a setup to the playbook?" msgstr "" #: ../../../docs/faq.md:390 -msgid "However, we recommend you to follow our installation guide, instead of jumping straight to installing." +msgid "Yes, you can." msgstr "" #: ../../../docs/faq.md:392 -msgid "There are two guides available:" +msgid "You generally need to do a playbook installation. It's recommended to follow the full installation guide (starting at the [Prerequisites](prerequisites.md) page), not the [Quick start](quick-start.md) guide. The full installation guide will tell you when it's time to import your existing data into the newly-prepared server." msgstr "" #: ../../../docs/faq.md:394 -msgid "⚡ **[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\"." +msgid "This Ansible playbook guides you into installing a server for `example.com` (user IDs are like this: `@alice:example.com`), while the server is at `matrix.example.com`. If your existing setup has a server name (`server_name` configuration setting in Synapse's `homeserver.yaml` file) other than the base `example.com`, you may need to tweak some additional variables. This FAQ entry may be of use if you're dealing with a more complicated setup — [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" msgstr "" #: ../../../docs/faq.md:396 -msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide by starting with the **[Prerequisites](prerequisites.md)** documentation page." +msgid "After configuring the playbook and installing and **before starting** services (done with `ansible-playbook … --tags=start`) you'd import [your SQLite](importing-synapse-sqlite.md) (or [Postgres](importing-postgres.md)) database and also [import your media store](importing-synapse-media-store.md)." msgstr "" #: ../../../docs/faq.md:398 -msgid "I installed Synapse some other way. Can I migrate such a setup to the playbook?" +msgid "I've downloaded Ansible and the playbook on the server. It can't connect using SSH." msgstr "" #: ../../../docs/faq.md:400 -msgid "Yes, you can." +msgid "If you're using the playbook directly on the server, then Ansible doesn't need to connect using SSH." msgstr "" #: ../../../docs/faq.md:402 -msgid "You generally need to do a playbook installation. It's recommended to follow the full installation guide (starting at the [Prerequisites](prerequisites.md) page), not the [Quick start](quick-start.md) guide. The full installation guide will tell you when it's time to import your existing data into the newly-prepared server." +msgid "It can perform a local connection instead. Just set `ansible_connection=local` at the end of the server line in `inventory/hosts` and re-run the playbook." msgstr "" #: ../../../docs/faq.md:404 -msgid "This Ansible playbook guides you into installing a server for `example.com` (user IDs are like this: `@alice:example.com`), while the server is at `matrix.example.com`. If your existing setup has a server name (`server_name` configuration setting in Synapse's `homeserver.yaml` file) other than the base `example.com`, you may need to tweak some additional variables. This FAQ entry may be of use if you're dealing with a more complicated setup — [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" +msgid "If you're running Ansible from within a container (one of the possibilities we list on our [dedicated Ansible documentation page](ansible.md)), then using `ansible_connection=local` is not possible." msgstr "" #: ../../../docs/faq.md:406 -msgid "After configuring the playbook and installing and **before starting** services (done with `ansible-playbook … --tags=start`) you'd import [your SQLite](importing-synapse-sqlite.md) (or [Postgres](importing-postgres.md)) database and also [import your media store](importing-synapse-media-store.md)." +msgid "Troubleshooting" msgstr "" #: ../../../docs/faq.md:408 -msgid "I've downloaded Ansible and the playbook on the server. It can't connect using SSH." +msgid "I get \"Error response from daemon: configured logging driver does not support reading\" when I do `docker logs matrix-synapse`." msgstr "" #: ../../../docs/faq.md:410 -msgid "If you're using the playbook directly on the server, then Ansible doesn't need to connect using SSH." +msgid "See [How can I see the logs?](#how-can-i-see-the-logs)." msgstr "" #: ../../../docs/faq.md:412 -msgid "It can perform a local connection instead. Just set `ansible_connection=local` at the end of the server line in `inventory/hosts` and re-run the playbook." +msgid "How can I see the logs?" msgstr "" #: ../../../docs/faq.md:414 -msgid "If you're running Ansible from within a container (one of the possibilities we list on our [dedicated Ansible documentation page](ansible.md)), then using `ansible_connection=local` is not possible." +msgid "We utilize [systemd/journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html#Description) for logging." msgstr "" #: ../../../docs/faq.md:416 -msgid "Maintenance and Troubleshooting" +msgid "To see logs for Synapse, run `journalctl -fu matrix-synapse.service`. You may wish to see the [manual page for journalctl](https://www.commandlinux.com/man-page/man1/journalctl.1.html)." msgstr "" #: ../../../docs/faq.md:418 -msgid "💡 Also see this page for generic information about maintaining the services and troubleshooting: [Maintenance and Troubleshooting](maintenance-and-troubleshooting.md)" +msgid "Available service names can be seen by doing `ls /etc/systemd/system/matrix*.service` on the server." msgstr "" #: ../../../docs/faq.md:420 -msgid "Do I need to do anything to keep my Matrix server updated?" +msgid "Some services also log to files in `/matrix/*/data/..`, but we're slowly moving away from that." msgstr "" #: ../../../docs/faq.md:422 -msgid "Yes. We don't update anything for you automatically." +msgid "We also disable Docker logging, so you can't use `docker logs matrix-*` either. We do this to prevent useless double (or even triple) logging and to avoid having to rotate log files." msgstr "" #: ../../../docs/faq.md:424 -msgid "See our [documentation page about upgrading services](maintenance-upgrading-services.md)." +msgid "We just simply delegate logging to journald and it takes care of persistence and expiring old data." msgstr "" #: ../../../docs/faq.md:426 -msgid "How do I move my existing installation to another (VM) server?" +msgid "Also see: [How long do systemd/journald logs persist for?](#how-long-do-systemdjournald-logs-persist-for)" msgstr "" #: ../../../docs/faq.md:428 -msgid "If you have an existing installation done using this Ansible playbook, you can easily migrate that to another server following [our dedicated server migration guide](maintenance-migrating.md)." +msgid "How long do systemd/journald logs persist for?" msgstr "" #: ../../../docs/faq.md:430 -msgid "If your previous installation is done in some other way (not using this Ansible playbook), see [I installed Synapse some other way. Can I migrate such a setup to the playbook?](#i-installed-synapse-some-other-way-can-i-migrate-such-a-setup-to-the-playbook)." +msgid "On some distros, the journald logs are just in-memory and not persisted to disk." msgstr "" #: ../../../docs/faq.md:432 -msgid "What is this `/matrix/postgres/data-auto-upgrade-backup` directory that is taking up so much space?" +msgid "Consult (and feel free to adjust) your distro's journald logging configuration in `/etc/systemd/journald.conf`." msgstr "" #: ../../../docs/faq.md:434 -msgid "When you [perform a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql), we save the the old data files in `/matrix/postgres/data-auto-upgrade-backup`, just so you could easily restore them should something have gone wrong." +msgid "To enable persistence and put some limits on how large the journal log files can become, adjust your configuration like this:" msgstr "" -#: ../../../docs/faq.md:436 -msgid "After verifying that everything still works after the Postgres upgrade, you can safely delete `/matrix/postgres/data-auto-upgrade-backup`" +#: ../../../docs/faq.md:445 +msgid "Maintenance" msgstr "" -#: ../../../docs/faq.md:438 -msgid "I get \"Error response from daemon: configured logging driver does not support reading\" when I run `docker logs matrix-synapse`. Why?" +#: ../../../docs/faq.md:447 +msgid "Do I need to do anything to keep my Matrix server updated?" msgstr "" -#: ../../../docs/faq.md:440 -msgid "To prevent double-logging, Docker logging is disabled by explicitly passing `--log-driver=none` to all containers. Due to this, you cannot view logs using `docker logs matrix-*`." +#: ../../../docs/faq.md:449 +msgid "Yes. We don't update anything for you automatically." msgstr "" -#: ../../../docs/faq.md:442 -msgid "See [this section](maintenance-and-troubleshooting.md#how-to-see-the-logs) on the page for maintenance and troubleshooting for more details to see the logs." +#: ../../../docs/faq.md:451 +msgid "See our [documentation page about upgrading services](maintenance-upgrading-services.md)." msgstr "" -#: ../../../docs/faq.md:444 -msgid "The server fails to start due to the `Unable to start service matrix-coturn.service` error. Why and how to solve it?" +#: ../../../docs/faq.md:453 +msgid "How do I move my existing installation to another (VM) server?" msgstr "" -#: ../../../docs/faq.md:446 -msgid "The error is most likely because Traefik cannot obtain SSL certificates due to certain reasons such as wrong domain name configuration or port 80 being unavailable due to other services." +#: ../../../docs/faq.md:455 +msgid "If you have an existing installation done using this Ansible playbook, you can easily migrate that to another server using [our dedicated server migration guide](maintenance-migrating.md)." msgstr "" -#: ../../../docs/faq.md:448 -msgid "If Traefik fails to obtain an SSL certificate for domain names such as `matrix.`, Traefik Certs Dumper cannot extract the SSL certificate out of there, and coturn cannot be started and the error occurs. Refer to these comments for details:" +#: ../../../docs/faq.md:457 +msgid "If your previous installation is done in some other way (not using this Ansible playbook), see [I installed Synapse some other way. Can I migrate such a setup to the playbook?](#i-installed-synapse-some-other-way-can-i-migrate-such-a-setup-to-the-playbook)." msgstr "" -#: ../../../docs/faq.md:450 -msgid "" +#: ../../../docs/faq.md:459 +msgid "How do I back up the data on my server?" msgstr "" -#: ../../../docs/faq.md:451 -msgid "" +#: ../../../docs/faq.md:461 +msgid "We haven't documented this properly yet, but the general advice is to:" msgstr "" -#: ../../../docs/faq.md:453 -msgid "If you are not sure what the problem is, at first make sure that you have set the \"base domain\" (`example.com`, **not `matrix.example.com`**) to `matrix_domain`. You should be able to find it at the top of your `vars.yml`." +#: ../../../docs/faq.md:463 +msgid "back up Postgres by making a database dump. See [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql)" msgstr "" -#: ../../../docs/faq.md:455 -msgid "If it is correctly specified, look Traefik's logs (`journalctl -fu matrix-traefik.service`) for errors by Let's Encrypt for troubleshooting." +#: ../../../docs/faq.md:465 +msgid "back up all `/matrix` files, except for `/matrix/postgres/data` (you already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` (this directory may exist and contain your old data if you've [performed a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql))." msgstr "" -#: ../../../docs/faq.md:457 +#: ../../../docs/faq.md:467 +msgid "You can later restore these by:" +msgstr "" + +#: ../../../docs/faq.md:469 +msgid "Restoring the `/matrix` directory and files on the new server manually" +msgstr "" + +#: ../../../docs/faq.md:470 +msgid "Following the instruction described on [Installing a server into which you'll import old data](installing.md#installing-a-server-into-which-youll-import-old-data)" +msgstr "" + +#: ../../../docs/faq.md:472 +msgid "If your server's IP address has changed, you may need to [set up DNS](configuring-dns.md) again." +msgstr "" + +#: ../../../docs/faq.md:474 +msgid "What is this `/matrix/postgres/data-auto-upgrade-backup` directory that is taking up so much space?" +msgstr "" + +#: ../../../docs/faq.md:476 +msgid "When you [perform a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql), we save the the old data files in `/matrix/postgres/data-auto-upgrade-backup`, just so you could easily restore them should something have gone wrong." +msgstr "" + +#: ../../../docs/faq.md:478 +msgid "After verifying that everything still works after the Postgres upgrade, you can safely delete `/matrix/postgres/data-auto-upgrade-backup`" +msgstr "" + +#: ../../../docs/faq.md:480 +msgid "How do I debug or force SSL certificate renewal?" +msgstr "" + +#: ../../../docs/faq.md:482 +msgid "SSL certificates are managed automatically by the [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server." +msgstr "" + +#: ../../../docs/faq.md:484 +msgid "If you're having trouble with SSL certificate renewal, check the Traefik logs (`journalctl -fu matrix-traefik`)." +msgstr "" + +#: ../../../docs/faq.md:486 +msgid "If you're [using your own webserver](configuring-playbook-own-webserver.md) instead of the integrated one (Traefik), you should investigate in another way." +msgstr "" + +#: ../../../docs/faq.md:488 msgid "Miscellaneous" msgstr "" -#: ../../../docs/faq.md:459 +#: ../../../docs/faq.md:490 msgid "I would like to see this favorite service of mine integrated and become available on my Matrix server. How can I request it?" msgstr "" -#: ../../../docs/faq.md:461 -msgid "You can freely create an issue for feature request on the repository at GitHub [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/new/choose). Note this is a community project with no financial backing, and there is not assurance that your request would be eventually picked up by others and the requested feature would become available. The easiest way to get a feature into this project is to just develop it yourself." +#: ../../../docs/faq.md:492 +msgid "You can freely create an issue for feature request on the repository at GitHub [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/new). Note this is a community project with no financial backing, and there is not assurance that your request would be eventually picked up by others and the requested feature would become available. The easiest way to get a feature into this project is to just develop it yourself." msgstr "" -#: ../../../docs/faq.md:463 +#: ../../../docs/faq.md:494 msgid "Also, please note that this playbook intends to focus solely on Matrix and Matrix-related services. If your request is not specific to Matrix, you may as well to consider to submit it to the [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook), maintained by the members behind this matrix-docker-ansible-deploy project. [This document on the interoperability](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md) describes how to deploy services along with the Matrix services easily." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/getting-the-playbook.po b/i18n/locales/jp/LC_MESSAGES/docs/getting-the-playbook.po index a3a05a2bf..4a6bfe641 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/getting-the-playbook.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/getting-the-playbook.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,68 +18,68 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/getting-the-playbook.md:8 +#: ../../../docs/getting-the-playbook.md:1 msgid "Getting the playbook" msgstr "" -#: ../../../docs/getting-the-playbook.md:10 -msgid "[Prerequisites](prerequisites.md) > [Configuring DNS settings](configuring-dns.md) > Getting the playbook > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)" +#: ../../../docs/getting-the-playbook.md:3 +msgid "[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > Getting the playbook > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)" msgstr "" -#: ../../../docs/getting-the-playbook.md:12 +#: ../../../docs/getting-the-playbook.md:5 msgid "This Ansible playbook is meant to be executed on your own computer (not the Matrix server)." msgstr "" -#: ../../../docs/getting-the-playbook.md:14 +#: ../../../docs/getting-the-playbook.md:7 msgid "In special cases (if your computer cannot run Ansible, etc.) you may put the playbook on the server as well." msgstr "" -#: ../../../docs/getting-the-playbook.md:16 +#: ../../../docs/getting-the-playbook.md:9 msgid "You can retrieve the playbook's source code by:" msgstr "" -#: ../../../docs/getting-the-playbook.md:17 +#: ../../../docs/getting-the-playbook.md:11 msgid "[Using git to get the playbook](#using-git-to-get-the-playbook) (recommended)" msgstr "" -#: ../../../docs/getting-the-playbook.md:18 +#: ../../../docs/getting-the-playbook.md:13 msgid "[Downloading the playbook as a ZIP archive](#downloading-the-playbook-as-a-zip-archive) (not recommended)" msgstr "" -#: ../../../docs/getting-the-playbook.md:20 +#: ../../../docs/getting-the-playbook.md:15 msgid "Using git to get the playbook" msgstr "" -#: ../../../docs/getting-the-playbook.md:22 +#: ../../../docs/getting-the-playbook.md:17 msgid "We recommend using the [git](https://git-scm.com/) tool to get the playbook's source code, because it lets you easily keep up to date in the future when [Maintaining services](maintenance-upgrading-services.md)." msgstr "" -#: ../../../docs/getting-the-playbook.md:24 +#: ../../../docs/getting-the-playbook.md:19 msgid "Once you've installed git on your computer, you can go to any directory of your choosing and run the following command to retrieve the playbook's source code:" msgstr "" -#: ../../../docs/getting-the-playbook.md:30 +#: ../../../docs/getting-the-playbook.md:25 msgid "This will create a new `matrix-docker-ansible-deploy` directory. You're supposed to execute all other installation commands inside that directory." msgstr "" -#: ../../../docs/getting-the-playbook.md:32 +#: ../../../docs/getting-the-playbook.md:27 msgid "Downloading the playbook as a ZIP archive" msgstr "" -#: ../../../docs/getting-the-playbook.md:34 +#: ../../../docs/getting-the-playbook.md:29 msgid "Alternatively, you can download the playbook as a ZIP archive. This is not recommended, as it's not easy to keep up to date with future updates. We suggest you [use git](#using-git-to-get-the-playbook) instead." msgstr "" -#: ../../../docs/getting-the-playbook.md:36 +#: ../../../docs/getting-the-playbook.md:31 msgid "The latest version is always at the following URL: https://github.com/spantaleev/matrix-docker-ansible-deploy/archive/master.zip" msgstr "" -#: ../../../docs/getting-the-playbook.md:38 +#: ../../../docs/getting-the-playbook.md:33 msgid "You can extract this archive anywhere. You'll get a directory called `matrix-docker-ansible-deploy-master`. You're supposed to execute all other installation commands inside that directory." msgstr "" -#: ../../../docs/getting-the-playbook.md:42 +#: ../../../docs/getting-the-playbook.md:37 msgid "[▶️](configuring-playbook.md) No matter which method you've used to download the playbook, you can proceed by [Configuring the playbook](configuring-playbook.md)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/howto-srv-server-delegation.po b/i18n/locales/jp/LC_MESSAGES/docs/howto-srv-server-delegation.po index 568c7884f..0c04fada6 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/howto-srv-server-delegation.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/howto-srv-server-delegation.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,132 +18,132 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/howto-srv-server-delegation.md:9 +#: ../../../docs/howto-srv-server-delegation.md:1 msgid "Server Delegation via a DNS SRV record (advanced)" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:11 +#: ../../../docs/howto-srv-server-delegation.md:3 msgid "**Reminder** : unless you are affected by the [Downsides of well-known-based Server Delegation](howto-server-delegation.md#downsides-of-well-known-based-server-delegation), we suggest you **stay on the simple/default path**: [Server Delegation](howto-server-delegation.md) by [configuring well-known files](configuring-well-known.md) at the base domain." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:13 +#: ../../../docs/howto-srv-server-delegation.md:5 msgid "This guide is about configuring Server Delegation using DNS SRV records (for the [Traefik](https://doc.traefik.io/traefik/) webserver). This method has special requirements when it comes to SSL certificates, so various changes are required." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:15 +#: ../../../docs/howto-srv-server-delegation.md:7 msgid "Prerequisites" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:17 +#: ../../../docs/howto-srv-server-delegation.md:9 msgid "SRV delegation while still using the playbook provided Traefik to get / renew the certificate requires a wildcard certificate." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:19 +#: ../../../docs/howto-srv-server-delegation.md:11 msgid "To obtain / renew one from [Let's Encrypt](https://letsencrypt.org/), one needs to use a [DNS-01 challenge](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) method instead of the default [HTTP-01](https://letsencrypt.org/docs/challenge-types/#http-01-challenge)." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:21 +#: ../../../docs/howto-srv-server-delegation.md:13 msgid "This means that this is **limited to the list of DNS providers supported by Traefik**, unless you bring in your own certificate." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:23 +#: ../../../docs/howto-srv-server-delegation.md:15 msgid "The up-to-date list can be accessed on [traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers)" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:25 +#: ../../../docs/howto-srv-server-delegation.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:27 +#: ../../../docs/howto-srv-server-delegation.md:19 msgid "**Note**: the changes below instruct you how to do this for a basic Synapse installation. You will need to adapt the variable name and the content of the labels:" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:29 -msgid "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))" +#: ../../../docs/howto-srv-server-delegation.md:21 +msgid "if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md), [conduwuit](./configuring-playbook-conduwuit.md) or [Dendrite](./configuring-playbook-dendrite.md))" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:30 +#: ../../../docs/howto-srv-server-delegation.md:22 msgid "if you're using [Synapse with workers enabled](./configuring-playbook-synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled: true`). In that case, it's actually the `matrix-synapse-reverse-proxy-companion` service which has Traefik labels attached" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:32 +#: ../../../docs/howto-srv-server-delegation.md:24 msgid "Also, all instructions below are from an older version of the playbook and may not work anymore." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:34 +#: ../../../docs/howto-srv-server-delegation.md:26 msgid "Federation Endpoint" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:41 +#: ../../../docs/howto-srv-server-delegation.md:33 msgid "This is because with SRV federation, some servers / tools (one of which being the federation tester) try to access the federation API using the resolved IP address instead of the domain name (or they are not using SNI). This change will make Traefik route all traffic for which the path match this rule go to the federation endpoint." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:43 +#: ../../../docs/howto-srv-server-delegation.md:35 msgid "Tell Traefik which certificate to serve for the federation endpoint" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:45 -msgid "Now that the federation endpoint is not bound to a domain anymore we need to explicitly tell Traefik to use a wildcard certificate in addition to one containing the base name." +#: ../../../docs/howto-srv-server-delegation.md:37 +msgid "Now that the federation endpoint is not bound to a domain anymore we need to explicitely tell Traefik to use a wildcard certificate in addition to one containing the base name." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:47 +#: ../../../docs/howto-srv-server-delegation.md:39 msgid "This is because the Matrix specification expects the federation endpoint to be served using a certificate compatible with the base domain, however, the other resources on the endpoint still need a valid certificate to work." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:56 +#: ../../../docs/howto-srv-server-delegation.md:48 msgid "Configure the DNS-01 challenge for let's encrypt" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:58 +#: ../../../docs/howto-srv-server-delegation.md:50 msgid "Since we're now requesting a wildcard certificate, we need to change the ACME challenge method. To request a wildcard certificate from Let's Encrypt we are required to use the DNS-01 challenge." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:60 +#: ../../../docs/howto-srv-server-delegation.md:52 msgid "This will need 3 changes:" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:61 +#: ../../../docs/howto-srv-server-delegation.md:53 msgid "Add a new certificate resolver that works with DNS-01" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:62 +#: ../../../docs/howto-srv-server-delegation.md:54 msgid "Configure the resolver to allow access to the DNS zone to configure the records to answer the challenge (refer to [Traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers) to know which environment variables to set)" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:63 +#: ../../../docs/howto-srv-server-delegation.md:55 msgid "Tell the playbook to use the new resolver as default" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:65 +#: ../../../docs/howto-srv-server-delegation.md:57 msgid "We cannot just disable the default resolver as that would disable SSL in quite a few places in the playbook." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:93 +#: ../../../docs/howto-srv-server-delegation.md:86 msgid "Adjust coturn's configuration" msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:95 +#: ../../../docs/howto-srv-server-delegation.md:88 msgid "The last step is to alter the generated coturn configuration." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:97 +#: ../../../docs/howto-srv-server-delegation.md:90 msgid "By default, coturn is configured to wait on the certificate for the `matrix.` subdomain using an [instantiated systemd service](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Service%20Templates) using the domain name as the parameter for this service. However, we need to serve the wildcard certificate, which is incompatible with systemd, it will try to expand the `*`, which will break and prevent coturn from starting." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:99 +#: ../../../docs/howto-srv-server-delegation.md:92 msgid "We also need to indicate to coturn where the wildcard certificate is." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:101 +#: ../../../docs/howto-srv-server-delegation.md:94 msgid "⚠️ **Warning** : On first start of the services, coturn might still fail to start because Traefik is still in the process of obtaining the certificates. If you still get an error, make sure Traefik obtained the certificates and restart the coturn service (`just start-group coturn`)." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:103 +#: ../../../docs/howto-srv-server-delegation.md:96 msgid "This should not happen again afterwards as Traefik will renew certificates well before their expiry date, and the coturn service is setup to restart periodically." msgstr "" -#: ../../../docs/howto-srv-server-delegation.md:129 +#: ../../../docs/howto-srv-server-delegation.md:122 msgid "Full example of a working configuration" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/importing-postgres.po b/i18n/locales/jp/LC_MESSAGES/docs/importing-postgres.po index 792f80dec..d7d4df196 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/importing-postgres.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/importing-postgres.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,141 +18,132 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/importing-postgres.md:10 +#: ../../../docs/importing-postgres.md:1 msgid "Importing an existing Postgres database from another installation (optional)" msgstr "" -#: ../../../docs/importing-postgres.md:12 -msgid "You can manually import your database from a previous default installation of Synapse." -msgstr "" - -#: ../../../docs/importing-postgres.md:14 -#: ../../../docs/importing-postgres.md:38 -msgid "**Notes**:" -msgstr "" - -#: ../../../docs/importing-postgres.md:15 -msgid "Don't forget to import your Synapse `media_store` files as well — see [the importing-synapse-media-store guide](importing-synapse-media-store.md) for more details." +#: ../../../docs/importing-postgres.md:3 +msgid "Run this if you'd like to import your database from a previous installation. (don't forget to import your Synapse `media_store` files as well — see [the importing-synape-media-store guide](importing-synapse-media-store.md))." msgstr "" -#: ../../../docs/importing-postgres.md:16 -msgid "If you have an existing installation done using this Ansible playbook, you can easily migrate that to another server following [our dedicated server migration guide](maintenance-migrating.md)." -msgstr "" - -#: ../../../docs/importing-postgres.md:18 +#: ../../../docs/importing-postgres.md:6 msgid "Prerequisites" msgstr "" -#: ../../../docs/importing-postgres.md:20 +#: ../../../docs/importing-postgres.md:8 msgid "For this to work, **the database name in Postgres must match** what this playbook uses. This playbook uses a Postgres database name of `synapse` by default (controlled by the `matrix_synapse_database_database` variable). If your database name differs, be sure to change `matrix_synapse_database_database` to your desired name and to re-run the playbook before proceeding." msgstr "" -#: ../../../docs/importing-postgres.md:22 +#: ../../../docs/importing-postgres.md:10 msgid "The playbook supports importing Postgres dump files in **text** (e.g. `pg_dump > dump.sql`) or **gzipped** formats (e.g. `pg_dump | gzip -c > dump.sql.gz`). Importing multiple databases (as dumped by `pg_dumpall`) is also supported." msgstr "" -#: ../../../docs/importing-postgres.md:24 +#: ../../../docs/importing-postgres.md:12 msgid "The migration might be a good moment, to \"reset\" a not properly working bridge. Be aware, that it might affect all users (new link to bridge, new rooms, …)" msgstr "" -#: ../../../docs/importing-postgres.md:26 +#: ../../../docs/importing-postgres.md:14 msgid "Before doing the actual import, **you need to upload your Postgres dump file to the server** (any path is okay)." msgstr "" -#: ../../../docs/importing-postgres.md:28 +#: ../../../docs/importing-postgres.md:16 msgid "Importing" msgstr "" -#: ../../../docs/importing-postgres.md:30 +#: ../../../docs/importing-postgres.md:18 msgid "To import, run this command (make sure to replace `SERVER_PATH_TO_POSTGRES_DUMP_FILE` with a file path on your server):" msgstr "" -#: ../../../docs/importing-postgres.md:40 +#: ../../../docs/importing-postgres.md:26 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/importing-postgres.md:28 msgid "`SERVER_PATH_TO_POSTGRES_DUMP_FILE` must be a file path to a Postgres dump file on the server (not on your local machine!)" msgstr "" -#: ../../../docs/importing-postgres.md:41 +#: ../../../docs/importing-postgres.md:29 msgid "`postgres_default_import_database` defaults to `matrix`, which is useful for importing multiple databases (for dumps made with `pg_dumpall`). If you're importing a single database (e.g. `synapse`), consider changing `postgres_default_import_database` accordingly" msgstr "" -#: ../../../docs/importing-postgres.md:42 +#: ../../../docs/importing-postgres.md:30 msgid "after importing a large database, it's a good idea to run [an `ANALYZE` operation](https://www.postgresql.org/docs/current/sql-analyze.html) to make Postgres rebuild its database statistics and optimize its query planner. You can easily do this via the playbook by running `just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze` (see [Vacuuming PostgreSQL](maintenance-postgres.md#vacuuming-postgresql) for more details)." msgstr "" -#: ../../../docs/importing-postgres.md:44 +#: ../../../docs/importing-postgres.md:32 msgid "Troubleshooting" msgstr "" -#: ../../../docs/importing-postgres.md:46 +#: ../../../docs/importing-postgres.md:34 msgid "Table Ownership" msgstr "" -#: ../../../docs/importing-postgres.md:48 +#: ../../../docs/importing-postgres.md:36 msgid "A table ownership issue can occur if you are importing from a Synapse installation which was both:" msgstr "" -#: ../../../docs/importing-postgres.md:50 +#: ../../../docs/importing-postgres.md:38 msgid "migrated from SQLite to Postgres, and" msgstr "" -#: ../../../docs/importing-postgres.md:51 +#: ../../../docs/importing-postgres.md:39 msgid "used a username other than 'synapse'" msgstr "" -#: ../../../docs/importing-postgres.md:53 +#: ../../../docs/importing-postgres.md:41 msgid "In this case you may run into the following error during the import task:" msgstr "" -#: ../../../docs/importing-postgres.md:59 +#: ../../../docs/importing-postgres.md:47 msgid "where `synapse_user` is the database username from the previous Synapse installation." msgstr "" -#: ../../../docs/importing-postgres.md:61 +#: ../../../docs/importing-postgres.md:49 msgid "This can be verified by examining the dump for ALTER TABLE statements which set OWNER TO that username:" msgstr "" -#: ../../../docs/importing-postgres.md:73 +#: ../../../docs/importing-postgres.md:61 msgid "It can be worked around by changing the username to `synapse`, for example by using `sed`:" msgstr "" -#: ../../../docs/importing-postgres.md:79 +#: ../../../docs/importing-postgres.md:67 msgid "This uses sed to perform an 'in-place' (`-i`) replacement globally (`/g`), searching for `synapse_user` and replacing with `synapse` (`s/synapse_user/synapse`). If your database username was different, change `synapse_user` to that username instead. Expand search/replace statement as shown in example above, in case of old user name like `matrix` — replacing `matrix` only would… well — you can imagine." msgstr "" -#: ../../../docs/importing-postgres.md:81 +#: ../../../docs/importing-postgres.md:69 msgid "Note that if the previous import failed with an error it may have made changes which are incompatible with re-running the import task right away; if you do so it may fail with an error such as:" msgstr "" -#: ../../../docs/importing-postgres.md:87 +#: ../../../docs/importing-postgres.md:75 msgid "Repeat import" msgstr "" -#: ../../../docs/importing-postgres.md:89 +#: ../../../docs/importing-postgres.md:77 msgid "In this case you can use the command suggested in the import task to clear the database before retrying the import:" msgstr "" -#: ../../../docs/importing-postgres.md:97 +#: ../../../docs/importing-postgres.md:85 msgid "Now on your local machine run `just run-tags setup-postgres` to prepare the database roles etc." msgstr "" -#: ../../../docs/importing-postgres.md:99 +#: ../../../docs/importing-postgres.md:87 msgid "If not, you probably get this error. `synapse` is the correct table owner, but the role is missing in database." msgstr "" -#: ../../../docs/importing-postgres.md:105 +#: ../../../docs/importing-postgres.md:93 msgid "Once the database is clear and the ownership of the tables has been fixed in the SQL file, the import task should succeed." msgstr "" -#: ../../../docs/importing-postgres.md:107 +#: ../../../docs/importing-postgres.md:95 msgid "Check, if `--dbname` is set to `synapse` (not `matrix`) and replace paths (or even better, copy this line from your terminal)" msgstr "" -#: ../../../docs/importing-postgres.md:113 +#: ../../../docs/importing-postgres.md:101 msgid "Hints" msgstr "" -#: ../../../docs/importing-postgres.md:115 +#: ../../../docs/importing-postgres.md:103 msgid "To open psql terminal run `/matrix/postgres/bin/cli`" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-media-store.po b/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-media-store.po index f76b81a52..e267284e4 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-media-store.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-media-store.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,44 +18,44 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/importing-synapse-media-store.md:8 +#: ../../../docs/importing-synapse-media-store.md:1 msgid "Importing `media_store` data files from an existing Synapse installation (optional)" msgstr "" -#: ../../../docs/importing-synapse-media-store.md:10 -msgid "You can manually import your `media_store` files from a previous installation of Synapse." +#: ../../../docs/importing-synapse-media-store.md:3 +msgid "Run this if you'd like to import your `media_store` files from a previous installation of Synapse." msgstr "" -#: ../../../docs/importing-synapse-media-store.md:12 +#: ../../../docs/importing-synapse-media-store.md:5 msgid "Prerequisites" msgstr "" -#: ../../../docs/importing-synapse-media-store.md:14 +#: ../../../docs/importing-synapse-media-store.md:7 msgid "Before doing the actual data restore, **you need to upload your media store directory to the server** (any path is okay)." msgstr "" -#: ../../../docs/importing-synapse-media-store.md:16 +#: ../../../docs/importing-synapse-media-store.md:9 msgid "If you are [storing Matrix media files on Amazon S3](configuring-playbook-s3.md) (optional), restoring with this tool is not possible right now." msgstr "" -#: ../../../docs/importing-synapse-media-store.md:18 +#: ../../../docs/importing-synapse-media-store.md:11 msgid "As an alternative, you can perform a manual restore using the [AWS CLI tool](https://aws.amazon.com/cli/) (e.g. `aws s3 sync /path/to/server/media_store/. s3://name-of-bucket/`)" msgstr "" -#: ../../../docs/importing-synapse-media-store.md:20 +#: ../../../docs/importing-synapse-media-store.md:13 msgid "**Note for Mac users**: Due to case-sensitivity issues on certain Mac filesystems (HFS or HFS+), filename corruption may occur if you copy a `media_store` directory to your Mac. If you're transferring a `media_store` directory between 2 servers, make sure you do it directly (from server to server with a tool such as [rsync](https://rsync.samba.org/)), and not by downloading the files to your Mac." msgstr "" -#: ../../../docs/importing-synapse-media-store.md:22 +#: ../../../docs/importing-synapse-media-store.md:15 msgid "Importing" msgstr "" -#: ../../../docs/importing-synapse-media-store.md:24 +#: ../../../docs/importing-synapse-media-store.md:17 msgid "Run this command (make sure to replace `` with a path on your server):" msgstr "" -#: ../../../docs/importing-synapse-media-store.md:30 +#: ../../../docs/importing-synapse-media-store.md:23 msgid "**Note**: `` must be a file path to a `media_store` directory on the server (not on your local machine!)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-sqlite.po b/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-sqlite.po index d37ef68c4..cbb95955c 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-sqlite.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-sqlite.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,64 +18,60 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/importing-synapse-sqlite.md:9 +#: ../../../docs/importing-synapse-sqlite.md:1 msgid "Importing an existing SQLite database from another Synapse installation (optional)" msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:11 -msgid "You can manually import your database from a previous default installation of Synapse." +#: ../../../docs/importing-synapse-sqlite.md:3 +msgid "Run this if you'd like to import your database from a previous default installation of Synapse (don't forget to import your `media_store` files as well — see [the importing-synapse-media-store guide](importing-synapse-media-store.md))." msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:13 +#: ../../../docs/importing-synapse-sqlite.md:5 msgid "While this playbook only supports running Synapse in combination with PostgreSQL, a Synapse instance installed manually usually defaults to using an SQLite database." msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:15 +#: ../../../docs/importing-synapse-sqlite.md:7 msgid "If you have such a Synapse setup and wish to migrate it to one managed by the playbook (and over to PostgreSQL), this documentation page is for you." msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:17 -msgid "**Note**: don't forget to import your Synapse `media_store` files as well — see [the importing-synapse-media-store guide](importing-synapse-media-store.md) for more details." -msgstr "" - -#: ../../../docs/importing-synapse-sqlite.md:19 +#: ../../../docs/importing-synapse-sqlite.md:9 msgid "Prerequisites" msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:21 +#: ../../../docs/importing-synapse-sqlite.md:11 msgid "Before doing the actual import:" msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:23 +#: ../../../docs/importing-synapse-sqlite.md:13 msgid "**ensure you have NOT started Synapse yet**. That is, make sure you have followed the [Installing step](installing.md), but haven't run the playbook's `start` tag yet. If you had started your new Synapse instance, it may have already initialized your Postgres database and importing onto it may not work. In such cases, you may need to clean up the `synapse` database first." msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:24 +#: ../../../docs/importing-synapse-sqlite.md:14 msgid "**ensure you have uploaded your SQLite database file to the server** (any path is okay)" msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:25 +#: ../../../docs/importing-synapse-sqlite.md:15 msgid "if you're using the integrated Postgres server (**by default, you are** using it, unless you've explicitly switched to [Using an external PostgreSQL server](configuring-playbook-external-postgres.md)), **make sure Postgres is started** by running `just start-group postgres`" msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:27 +#: ../../../docs/importing-synapse-sqlite.md:17 msgid "Importing" msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:29 +#: ../../../docs/importing-synapse-sqlite.md:19 msgid "Run this command (make sure to replace `` with a file path on your server):" msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:35 +#: ../../../docs/importing-synapse-sqlite.md:25 msgid "**Notes**:" msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:37 +#: ../../../docs/importing-synapse-sqlite.md:27 msgid "`` must be replaced with a file path to a `homeserver.db` **file on the server** (not on your local machine!)." msgstr "" -#: ../../../docs/importing-synapse-sqlite.md:38 +#: ../../../docs/importing-synapse-sqlite.md:28 msgid "if the SQLite database is from an older version of Synapse, the **importing procedure may run migrations on it to bring it up to date**. That is, your SQLite database file may get modified and become unusable with your older Synapse version. Keeping a copy of the original is probably wise." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/installing.po b/i18n/locales/jp/LC_MESSAGES/docs/installing.po index fb82125fe..db20df55f 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/installing.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/installing.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,296 +18,288 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/installing.md:15 +#: ../../../docs/installing.md:1 msgid "Installing" msgstr "" -#: ../../../docs/installing.md:17 -msgid "[Prerequisites](prerequisites.md) > [Configuring DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > Installing" +#: ../../../docs/installing.md:3 +msgid "[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > Installing" msgstr "" -#: ../../../docs/installing.md:19 +#: ../../../docs/installing.md:5 msgid "If you've configured your DNS records and the playbook, you can start the installation procedure." msgstr "" -#: ../../../docs/installing.md:21 +#: ../../../docs/installing.md:7 msgid "Update Ansible roles" msgstr "" -#: ../../../docs/installing.md:23 +#: ../../../docs/installing.md:9 msgid "Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside." msgstr "" -#: ../../../docs/installing.md:25 +#: ../../../docs/installing.md:11 msgid "To update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file), run:" msgstr "" -#: ../../../docs/installing.md:27 +#: ../../../docs/installing.md:13 msgid "either: `just update`" msgstr "" -#: ../../../docs/installing.md:28 +#: ../../../docs/installing.md:14 msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)" msgstr "" -#: ../../../docs/installing.md:30 +#: ../../../docs/installing.md:16 msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`" msgstr "" -#: ../../../docs/installing.md:32 +#: ../../../docs/installing.md:18 msgid "For details about `just` commands, take a look at: [Running `just` commands](just.md)." msgstr "" -#: ../../../docs/installing.md:34 +#: ../../../docs/installing.md:20 msgid "Install Matrix server and services" msgstr "" -#: ../../../docs/installing.md:36 +#: ../../../docs/installing.md:22 msgid "The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks." msgstr "" -#: ../../../docs/installing.md:38 +#: ../../../docs/installing.md:24 msgid "The general command syntax for installation (and also maintenance) is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`. It is recommended to get yourself familiar with the [playbook tags](playbook-tags.md) before proceeding." msgstr "" -#: ../../../docs/installing.md:40 +#: ../../../docs/installing.md:26 msgid "If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the all Ansible commands." msgstr "" -#: ../../../docs/installing.md:42 +#: ../../../docs/installing.md:28 msgid "If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to all Ansible commands." msgstr "" -#: ../../../docs/installing.md:44 +#: ../../../docs/installing.md:30 msgid "There 2 ways to start the installation process — depending on whether you're [Installing a brand new server (without importing data)](#installing-a-brand-new-server-without-importing-data) or [Installing a server into which you'll import old data](#installing-a-server-into-which-youll-import-old-data)." msgstr "" -#: ../../../docs/installing.md:46 +#: ../../../docs/installing.md:32 msgid "**Note**: if you are migrating from an old server to a new one, take a look at [this guide](maintenance-migrating.md) instead. This is an easier and more straightforward way than installing a server and importing old data into it." msgstr "" -#: ../../../docs/installing.md:48 +#: ../../../docs/installing.md:34 msgid "Installing a brand new server (without importing data)" msgstr "" -#: ../../../docs/installing.md:50 +#: ../../../docs/installing.md:36 msgid "If this is **a brand new** Matrix server and you **won't be importing old data into it**, run all these tags:" msgstr "" -#: ../../../docs/installing.md:56 +#: ../../../docs/installing.md:42 msgid "This will do a full installation and start all Matrix services." msgstr "" -#: ../../../docs/installing.md:58 +#: ../../../docs/installing.md:44 msgid "**Note**: if the command does not work as expected, make sure that you have properly installed and configured software required to run the playbook, as described on [Prerequisites](prerequisites.md)." msgstr "" -#: ../../../docs/installing.md:60 +#: ../../../docs/installing.md:46 msgid "Installing a server into which you'll import old data" msgstr "" -#: ../../../docs/installing.md:62 +#: ../../../docs/installing.md:48 msgid "If you will be importing data into your newly created Matrix server, install it, but **do not** start its services just yet. Starting its services or messing with its database now will affect your data import later on." msgstr "" -#: ../../../docs/installing.md:64 +#: ../../../docs/installing.md:50 msgid "To do the installation **without** starting services, run `ansible-playbook` with the `install-all` tag only:" msgstr "" -#: ../../../docs/installing.md:70 +#: ../../../docs/installing.md:56 msgid "[!WARNING] Do not run the just \"recipe\" `just install-all` instead, because it automatically starts services at the end of execution. See: [Difference between playbook tags and shortcuts](just.md#difference-between-playbook-tags-and-shortcuts)" msgstr "" -#: ../../../docs/installing.md:73 +#: ../../../docs/installing.md:59 msgid "When this command completes, services won't be running yet." msgstr "" -#: ../../../docs/installing.md:75 +#: ../../../docs/installing.md:61 msgid "You can now:" msgstr "" -#: ../../../docs/installing.md:77 +#: ../../../docs/installing.md:63 msgid "[Importing an existing SQLite database (from another Synapse installation)](importing-synapse-sqlite.md) (optional)" msgstr "" -#: ../../../docs/installing.md:79 +#: ../../../docs/installing.md:65 msgid "[Importing an existing Postgres database (from another installation)](importing-postgres.md) (optional)" msgstr "" -#: ../../../docs/installing.md:81 +#: ../../../docs/installing.md:67 msgid "[Importing `media_store` data files from an existing Synapse installation](importing-synapse-media-store.md) (optional)" msgstr "" -#: ../../../docs/installing.md:83 +#: ../../../docs/installing.md:69 msgid "… and then proceed to starting all services:" msgstr "" -#: ../../../docs/installing.md:89 +#: ../../../docs/installing.md:75 msgid "Create your user account" msgstr "" -#: ../../../docs/installing.md:91 +#: ../../../docs/installing.md:77 msgid "ℹ️ *You can skip this step if you have installed a server and imported old data to it.*" msgstr "" -#: ../../../docs/installing.md:93 +#: ../../../docs/installing.md:79 msgid "As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server." msgstr "" -#: ../../../docs/installing.md:95 +#: ../../../docs/installing.md:81 msgid "After creating the user account, you can log in to it with [Element Web](configuring-playbook-client-element-web.md) that this playbook has installed for you at this URL: `https://element.example.com/`." msgstr "" -#: ../../../docs/installing.md:97 +#: ../../../docs/installing.md:83 msgid "To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer." msgstr "" -#: ../../../docs/installing.md:99 +#: ../../../docs/installing.md:85 msgid "**Notes**:" msgstr "" -#: ../../../docs/installing.md:100 +#: ../../../docs/installing.md:86 msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`" msgstr "" -#: ../../../docs/installing.md:101 +#: ../../../docs/installing.md:87 msgid "For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)" msgstr "" -#: ../../../docs/installing.md:102 +#: ../../../docs/installing.md:88 msgid "Use `admin=yes` to make your user account an administrator of the Matrix server" msgstr "" -#: ../../../docs/installing.md:110 +#: ../../../docs/installing.md:96 msgid "Feel free to create as many accounts (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your account only (with `admin=yes`), and others should be created with `admin=no`." msgstr "" -#: ../../../docs/installing.md:112 +#: ../../../docs/installing.md:98 msgid "For more information, see the documentation for [registering users](registering-users.md)." msgstr "" -#: ../../../docs/installing.md:114 +#: ../../../docs/installing.md:100 msgid "Finalize the installation" msgstr "" -#: ../../../docs/installing.md:116 +#: ../../../docs/installing.md:102 msgid "Now you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network." msgstr "" -#: ../../../docs/installing.md:118 +#: ../../../docs/installing.md:104 msgid "This is required for federation to work! Without a proper configuration, your server will effectively not be part of the Matrix network." msgstr "" -#: ../../../docs/installing.md:120 +#: ../../../docs/installing.md:106 msgid "To configure the delegation, you have these two options. Choose one of them according to your situation." msgstr "" -#: ../../../docs/installing.md:122 +#: ../../../docs/installing.md:108 msgid "If you can afford to point the base domain at the Matrix server, follow the instructions below which guide you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server. It will enable you to use a Matrix user ID like `@alice:example.com` while hosting services on a subdomain like `matrix.example.com`." msgstr "" -#: ../../../docs/installing.md:123 +#: ../../../docs/installing.md:109 msgid "Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot \"serve the base domain\" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server), but feel free to familiarize yourself with all [server delegation (redirection) options](howto-server-delegation.md)." msgstr "" -#: ../../../docs/installing.md:125 +#: ../../../docs/installing.md:111 msgid "To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/installing.md:131 +#: ../../../docs/installing.md:117 msgid "After configuring the playbook, run the command below:" msgstr "" -#: ../../../docs/installing.md:137 -msgid "**If an error is not returned, the installation has completed and the services have been started successfully**🎉" -msgstr "" - -#: ../../../docs/installing.md:139 +#: ../../../docs/installing.md:123 msgid "Things to do next" msgstr "" -#: ../../../docs/installing.md:141 -msgid "After completing the installation, you can:" +#: ../../../docs/installing.md:125 +msgid "After finilizing the installation, you can:" msgstr "" -#: ../../../docs/installing.md:143 -msgid "[check if services work](maintenance-and-troubleshooting.md#how-to-check-if-services-work)" +#: ../../../docs/installing.md:127 +msgid "[check if services work](maintenance-checking-services.md)" msgstr "" -#: ../../../docs/installing.md:144 +#: ../../../docs/installing.md:128 msgid "or [set up additional services](configuring-playbook.md#other-configuration-options) (bridges to other chat networks, bots, etc.)" msgstr "" -#: ../../../docs/installing.md:145 +#: ../../../docs/installing.md:129 msgid "or learn how to [upgrade services when new versions are released](maintenance-upgrading-services.md)" msgstr "" -#: ../../../docs/installing.md:146 +#: ../../../docs/installing.md:130 msgid "or learn how to [maintain your server](faq.md#maintenance)" msgstr "" -#: ../../../docs/installing.md:147 +#: ../../../docs/installing.md:131 msgid "or join some Matrix rooms:" msgstr "" -#: ../../../docs/installing.md:148 -msgid "via the *Explore rooms* feature in Element Web or some other clients, or by discovering them using this [matrix-static list](https://view.matrix.org). **Note**: joining large rooms may overload small servers. For tuning guidance on constrained hosts, see [Limit joining heavy rooms on constrained hosts](configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts)." +#: ../../../docs/installing.md:132 +msgid "via the *Explore rooms* feature in Element Web or some other clients, or by discovering them using this [matrix-static list](https://view.matrix.org). **Note**: joining large rooms may overload small servers." msgstr "" -#: ../../../docs/installing.md:150 +#: ../../../docs/installing.md:133 msgid "or come say Hi in our support room — [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting." msgstr "" -#: ../../../docs/installing.md:151 +#: ../../../docs/installing.md:134 msgid "or help make this playbook better by contributing (code, documentation, or [coffee/beer](https://liberapay.com/s.pantaleev/donate))" msgstr "" -#: ../../../docs/installing.md:153 -msgid "⚠️ Keep the playbook and services up-to-date" +#: ../../../docs/installing.md:136 +msgid "Maintaining your setup in the future" msgstr "" -#: ../../../docs/installing.md:155 +#: ../../../docs/installing.md:138 msgid "While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**." msgstr "" -#: ../../../docs/installing.md:157 +#: ../../../docs/installing.md:140 msgid "The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities." msgstr "" -#: ../../../docs/installing.md:159 +#: ../../../docs/installing.md:142 msgid "Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date." msgstr "" -#: ../../../docs/installing.md:161 -msgid "Also, do not forget to update your system regularly. While this playbook may install basic services, such as Docker, it will not interfere further with system maintenance. Keeping the system itself up-to-date is out of scope for this playbook." -msgstr "" - -#: ../../../docs/installing.md:163 -msgid "For more information about upgrading or maintaining services with the playbook, take a look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)" +#: ../../../docs/installing.md:144 +msgid "For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)" msgstr "" -#: ../../../docs/installing.md:165 +#: ../../../docs/installing.md:146 msgid "Feel free to **re-run the setup command any time** you think something is wrong with the server configuration. Ansible will take your configuration and update your server to match." msgstr "" -#: ../../../docs/installing.md:171 +#: ../../../docs/installing.md:152 msgid "**Note**: see [this page on the playbook tags](playbook-tags.md) for more information about those tags." msgstr "" -#: ../../../docs/installing.md:173 +#: ../../../docs/installing.md:154 msgid "Make full use of `just` shortcut commands" msgstr "" -#: ../../../docs/installing.md:175 +#: ../../../docs/installing.md:156 msgid "After you get familiar with reconfiguring and re-running the playbook to maintain the server, upgrade its services, etc., you probably would like to make use of `just` shortcut commands for faster input." msgstr "" -#: ../../../docs/installing.md:177 +#: ../../../docs/installing.md:158 msgid "For example, `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/installing.md:179 +#: ../../../docs/installing.md:160 msgid "You can learn about the shortcut commands on this page: [Running `just` commands](just.md)" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/just.po b/i18n/locales/jp/LC_MESSAGES/docs/just.po index 68492ff1b..19d13143e 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/just.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/just.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,29 +18,29 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/just.md:8 +#: ../../../docs/just.md:1 msgid "Running `just` commands" msgstr "" -#: ../../../docs/just.md:10 +#: ../../../docs/just.md:3 msgid "We have previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers [`ansible-galaxy`](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html)). Our [`Makefile`](../Makefile) is still around, and you can still run these commands." msgstr "" -#: ../../../docs/just.md:12 +#: ../../../docs/just.md:5 msgid "In addition, we have added support for running commands via [`just`](https://github.com/casey/just) — a more modern command-runner alternative to `make`. It can be used to invoke `ansible-playbook` commands with less typing." msgstr "" -#: ../../../docs/just.md:14 +#: ../../../docs/just.md:7 msgid "The `just` utility executes shortcut commands (called as \"recipes\"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile). Most of the just recipes have no corresponding `Makefile` targets." msgstr "" -#: ../../../docs/just.md:16 -msgid "For some recipes such as `just update`, our `justfile` recommends installing `agru` (a faster alternative to `ansible-galaxy`) to speed up the process." +#: ../../../docs/just.md:9 +msgid "For some recipes such as `just update`, our `justfile` recommends installing [`agru`](https://github.com/etkecc/agru) (a faster alternative to `ansible-galaxy`) to speed up the process." msgstr "" -#: ../../../docs/just.md:18 +#: ../../../docs/just.md:11 msgid "Here are some examples of shortcuts:" msgstr "" @@ -68,7 +68,7 @@ msgstr "" msgid "Run `git pull` (to update the playbook) and install the Ansible roles" msgstr "" -#: ../../../docs/just.md ../../../docs/just.md:40 +#: ../../../docs/just.md ../../../docs/just.md:33 msgid "`just install-all`" msgstr "" @@ -132,50 +132,30 @@ msgstr "" msgid "Registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)" msgstr "" -#: ../../../docs/just.md:33 +#: ../../../docs/just.md:26 msgid "While [our documentation on prerequisites](prerequisites.md) lists `just` as one of the requirements for installation, using `just` is optional. If you find it difficult to install it, do not find it useful, or want to prefer raw `ansible-playbook` commands for some reason, feel free to run all commands manually. For example, you can run `ansible-galaxy` directly to install the Ansible roles: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`." msgstr "" -#: ../../../docs/just.md:35 +#: ../../../docs/just.md:28 msgid "Difference between playbook tags and shortcuts" msgstr "" -#: ../../../docs/just.md:37 +#: ../../../docs/just.md:30 msgid "It is worth noting that `just` \"recipes\" are different from [playbook tags](playbook-tags.md). The recipes are shortcuts of commands defined in `justfile` and can be executed by the `just` program only, while the playbook tags are available for the raw `ansible-playbook` commands as well. Please be careful not to confuse them." msgstr "" -#: ../../../docs/just.md:39 +#: ../../../docs/just.md:32 msgid "For example, these two commands are different:" msgstr "" -#: ../../../docs/just.md:41 +#: ../../../docs/just.md:34 msgid "`ansible-playbook -i inventory/hosts setup.yml --tags=install-all`" msgstr "" -#: ../../../docs/just.md:43 +#: ../../../docs/just.md:36 msgid "The just recipe runs `ensure-matrix-users-created` and `start` tags after `install-all`, while the latter runs only `install-all` tag. The correct shortcut of the latter is `just run-tags install-all`." msgstr "" -#: ../../../docs/just.md:45 -msgid "Such kind of difference sometimes matters. For example, when you install a Matrix server into which you will import old data (see [here](installing.md#installing-a-server-into-which-youll-import-old-data)), you are not supposed to run `just install-all` or `just setup-all`, because these commands start services immediately after installing components, which may prevent you from importing the data." -msgstr "" - -#: ../../../docs/just.md:47 -msgid "Conditional service restart" -msgstr "" - -#: ../../../docs/just.md:49 -msgid "When running `install-all` or `install-service` (whether via `just` or raw `ansible-playbook`), only services whose configuration or container image actually changed during the playbook run will be restarted. Unchanged services are left running (or get started if they were stopped). This reduces unnecessary downtime." -msgstr "" - -#: ../../../docs/just.md:51 -msgid "When running with `setup-*` tags (e.g. `setup-all`, `setup-synapse`), all services are unconditionally restarted regardless of whether changes were detected. This is appropriate for setup's thorough \"full setup\" semantics." -msgstr "" - -#: ../../../docs/just.md:53 -msgid "`start-all` and `start-group` always restart all targeted services, since no installation tasks run during these commands." -msgstr "" - -#: ../../../docs/just.md:55 -msgid "This behavior is automatically determined based on the playbook tags in use. It can be overridden with the `devture_systemd_service_manager_conditional_restart_enabled` variable. For example, to force unconditional restarts during installation: `just install-all --extra-vars='devture_systemd_service_manager_conditional_restart_enabled=false'`" +#: ../../../docs/just.md:38 +msgid "Such kind of difference sometimes matters. For example, when you install a Matrix server into which you will import old data (see [here](installing.md#installing-a-server-into-which-youll-import-old-data)), you are not supposed to run `just install-all` or `just setup-all`, because these commands start services immediately after installing components which may prevent your from importing old data." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-and-troubleshooting.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-and-troubleshooting.po index 2da99c55f..50827aa93 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-and-troubleshooting.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-and-troubleshooting.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,160 +18,68 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/maintenance-and-troubleshooting.md:12 +#: ../../../docs/maintenance-and-troubleshooting.md:1 msgid "Maintenance and Troubleshooting" msgstr "" -#: ../../../docs/maintenance-and-troubleshooting.md:14 -msgid "Maintenance" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:16 -msgid "How to back up the data on your server" +#: ../../../docs/maintenance-and-troubleshooting.md:3 +msgid "How to see the current status of your services" msgstr "" -#: ../../../docs/maintenance-and-troubleshooting.md:18 -msgid "We haven't documented this properly yet, but the general advice is to:" +#: ../../../docs/maintenance-and-troubleshooting.md:5 +msgid "You can check the status of your services by using `systemctl status`. Example:" msgstr "" -#: ../../../docs/maintenance-and-troubleshooting.md:20 -msgid "back up Postgres by making a database dump. See [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql)" +#: ../../../docs/maintenance-and-troubleshooting.md:15 +msgid "Docker containers that the playbook configures are supervised by [systemd](https://wiki.archlinux.org/title/Systemd) and their logs are configured to go to [systemd-journald](https://wiki.archlinux.org/title/Systemd/Journal)." msgstr "" -#: ../../../docs/maintenance-and-troubleshooting.md:22 -msgid "back up all `/matrix` files, except for `/matrix/postgres/data` (you already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` (this directory may exist and contain your old data if you've [performed a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql))." +#: ../../../docs/maintenance-and-troubleshooting.md:17 +msgid "To prevent double-logging, Docker logging is disabled by explicitly passing `--log-driver=none` to all containers. Due to this, you **cannot** view logs using `docker logs`." msgstr "" -#: ../../../docs/maintenance-and-troubleshooting.md:24 -msgid "You can later restore these by:" +#: ../../../docs/maintenance-and-troubleshooting.md:19 +msgid "To view systemd-journald logs using [journalctl](https://man.archlinux.org/man/journalctl.1), run a command like this:" msgstr "" -#: ../../../docs/maintenance-and-troubleshooting.md:26 -msgid "Restoring the `/matrix` directory and files on the new server manually" +#: ../../../docs/maintenance-and-troubleshooting.md:25 +msgid "Increase logging verbosity" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:27 -msgid "Following the instruction described on [Installing a server into which you'll import old data](installing.md#installing-a-server-into-which-youll-import-old-data)" +msgid "Because the [Synapse](https://github.com/element-hq/synapse) Matrix server is originally very chatty when it comes to logging, we intentionally reduce its [logging level](https://docs.python.org/3/library/logging.html#logging-levels) from `INFO` to `WARNING`." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:29 -msgid "If your server's IP address has changed, you may need to [set up DNS](configuring-dns.md) again." +msgid "If you'd like to debug an issue or [report a Synapse bug](https://github.com/element-hq/synapse/issues/new/choose) to the developers, it'd be better if you temporarily increasing the logging level to `INFO`." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:31 -msgid "Remove unused Docker data" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:33 -msgid "You can free some disk space from Docker by removing its unused data. See [docker system prune](https://docs.docker.com/engine/reference/commandline/system_prune/) for more information." +msgid "Example configuration (`inventory/host_vars/matrix.example.com/vars.yml`):" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:39 -msgid "The shortcut command with `just` program is also available: `just run-tags run-docker-prune`" +msgid "Re-run the playbook after making these configuration changes." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:41 -msgid "Postgres" +msgid "Remove unused Docker data" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:43 -msgid "See the dedicated [PostgreSQL maintenance](maintenance-postgres.md) documentation page." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:45 -msgid "Synapse" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:47 -msgid "See the dedicated [Synapse maintenance](maintenance-synapse.md) documentation page." +msgid "You can free some disk space from Docker, see [docker system prune](https://docs.docker.com/engine/reference/commandline/system_prune/) for more information." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:49 -msgid "Troubleshooting" +msgid "The shortcut command with `just` program is also available: `just run-tags run-docker-prune`" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:51 -msgid "How to see the current status of your services" +msgid "Postgres" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:53 -msgid "You can check the status of your services by using `systemctl status`. Example:" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:63 -msgid "How to see the logs" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:65 -msgid "Docker containers that the playbook configures are supervised by [systemd](https://wiki.archlinux.org/title/Systemd) and their logs are configured to go to [systemd-journald](https://wiki.archlinux.org/title/Systemd/Journal)." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:67 -msgid "For example, you can find the logs of `matrix-synapse` in `systemd-journald` by logging in to the server with SSH and running the command as below:" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:73 -msgid "Available service names can be seen by doing `ls /etc/systemd/system/matrix*.service` on the server. Some services also log to files in `/matrix/*/data/..`, but we're slowly moving away from that." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:75 -msgid "We just simply delegate logging to journald and it takes care of persistence and expiring old data." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:77 -msgid "Enable systemd/journald logs persistence" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:79 -msgid "On some distros, the journald logs are just in-memory and not persisted to disk." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:81 -msgid "Consult (and feel free to adjust) your distro's journald logging configuration in `/etc/systemd/journald.conf`." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:83 -msgid "To enable persistence and put some limits on how large the journal log files can become, adjust your configuration like this:" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:94 -msgid "How to check if services work" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:96 -msgid "The playbook can perform a check to ensure that you've configured things correctly and that services are running." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:98 -msgid "To perform the check, run:" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:104 -msgid "The shortcut command with `just` program is also available: `just run-tags self-check`" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:106 -msgid "If it's all green, everything is probably running correctly." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:108 -msgid "Besides this self-check, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:110 -msgid "How to debug or force SSL certificate renewal" -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:112 -msgid "SSL certificates are managed automatically by the [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:114 -msgid "If you're having trouble with SSL certificate renewal, check the Traefik logs (`journalctl -fu matrix-traefik`)." -msgstr "" - -#: ../../../docs/maintenance-and-troubleshooting.md:116 -msgid "If you're [using your own webserver](configuring-playbook-own-webserver.md) instead of the integrated one (Traefik), you should investigate in another way." +msgid "See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) documentation page." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-migrating.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-migrating.po index 77c8b845d..77987e292 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-migrating.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-migrating.po @@ -10,7 +10,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: 2024-12-16 12:05+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,120 +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.18.0\n" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/maintenance-migrating.md:10 +#: ../../../docs/maintenance-migrating.md:1 msgid "Migrating to new server" msgstr "" -#: ../../../docs/maintenance-migrating.md:12 +#: ../../../docs/maintenance-migrating.md:3 msgid "This documentation explains how to migrate your Matrix services (server, client, bridges, etc.) and data **from an old server to a new server**." msgstr "" -#: ../../../docs/maintenance-migrating.md:14 +#: ../../../docs/maintenance-migrating.md:5 msgid "**Notes**:" msgstr "" -#: ../../../docs/maintenance-migrating.md:15 +#: ../../../docs/maintenance-migrating.md:6 msgid "This migration guide is applicable if you migrate from one server to another server having the same CPU architecture (e.g. both servers being `amd64`)." msgstr "" -#: ../../../docs/maintenance-migrating.md:17 +#: ../../../docs/maintenance-migrating.md:8 msgid "If you're trying to migrate between different architectures (e.g. `amd64` --> `arm64`), simply copying the complete `/matrix` directory is **not** possible as it would move the raw PostgreSQL data (`/matrix/postgres/data`) between different architectures. In this specific case, you can use the guide below as a reference, but you would also need to avoid syncing `/matrix/postgres/data` to the new host, and also dump the database on your current server and import it properly on the new server. See our [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql) docs for help with PostgreSQL backup/restore." msgstr "" -#: ../../../docs/maintenance-migrating.md:18 +#: ../../../docs/maintenance-migrating.md:9 msgid "If you have any questions about migration or encountered an issue during migration, do not hesitate to ask for help on [our Matrix room](https://matrix.to/#/%23matrix-docker-ansible-deploy:devture.com). You probably might want to prepare a temporary/sub account on another Matrix server in case it becomes impossible to use your server due to migration failure by any chance." msgstr "" -#: ../../../docs/maintenance-migrating.md:20 +#: ../../../docs/maintenance-migrating.md:11 msgid "You can't change the domain (specified in the `matrix_domain` variable) after the initial deployment." msgstr "" -#: ../../../docs/maintenance-migrating.md:22 +#: ../../../docs/maintenance-migrating.md:13 msgid "Lower DNS TTL" msgstr "" -#: ../../../docs/maintenance-migrating.md:24 +#: ../../../docs/maintenance-migrating.md:15 msgid "Prepare by lowering DNS TTL for your domains (`matrix.example.com`, etc.), so that DNS record changes would happen faster, leading to less downtime." msgstr "" -#: ../../../docs/maintenance-migrating.md:26 +#: ../../../docs/maintenance-migrating.md:17 msgid "Stop services on the old server completely" msgstr "" -#: ../../../docs/maintenance-migrating.md:28 +#: ../../../docs/maintenance-migrating.md:19 msgid "Before migrating, you need to stop all services on the old server and make sure they won't be starting again." msgstr "" -#: ../../../docs/maintenance-migrating.md:30 +#: ../../../docs/maintenance-migrating.md:21 msgid "To do so, it is recommended to run the `systemctl` command on the server. Running the playbook's `stop` tag also stops the services, but just once; they will start again if you reboot the server." msgstr "" -#: ../../../docs/maintenance-migrating.md:32 +#: ../../../docs/maintenance-migrating.md:23 msgid "Log in to the old server and run the command as `root` (or a user that can run it with `sudo`):" msgstr "" -#: ../../../docs/maintenance-migrating.md:38 +#: ../../../docs/maintenance-migrating.md:29 msgid "Copy data directory to the new server" msgstr "" -#: ../../../docs/maintenance-migrating.md:40 +#: ../../../docs/maintenance-migrating.md:31 msgid "After you've confirmed that all services were stopped, copy the `/matrix` directory from the old server to the new server. When copying, make sure to preserve ownership and permissions (use `cp -p` or `rsync -ar`)!" msgstr "" -#: ../../../docs/maintenance-migrating.md:42 +#: ../../../docs/maintenance-migrating.md:33 msgid "Adjust DNS records" msgstr "" -#: ../../../docs/maintenance-migrating.md:44 +#: ../../../docs/maintenance-migrating.md:35 msgid "Make sure your DNS records are adjusted to point to the new server's IP address." msgstr "" -#: ../../../docs/maintenance-migrating.md:46 +#: ../../../docs/maintenance-migrating.md:37 msgid "Update `inventory/hosts` file" msgstr "" -#: ../../../docs/maintenance-migrating.md:48 +#: ../../../docs/maintenance-migrating.md:39 msgid "Having adjusted DNS records, replace the old server's external IP address on the `inventory/hosts` file with that of the new server." msgstr "" -#: ../../../docs/maintenance-migrating.md:50 +#: ../../../docs/maintenance-migrating.md:41 msgid "Create `matrix` user and group on the new server" msgstr "" -#: ../../../docs/maintenance-migrating.md:52 +#: ../../../docs/maintenance-migrating.md:43 msgid "Then, run the command below on your local computer to create the `matrix` user and group on the new server:" msgstr "" -#: ../../../docs/maintenance-migrating.md:58 +#: ../../../docs/maintenance-migrating.md:49 msgid "The shortcut command with `just` program is also available: `just run-tags setup-system-user`" msgstr "" -#: ../../../docs/maintenance-migrating.md:60 +#: ../../../docs/maintenance-migrating.md:51 msgid "**Note**: because the `matrix` user and group are created dynamically on each server, the user/group ID may differ between the old and new server. We suggest that you adjust ownership of `/matrix` files. To adjust the ownership, log in to the new server and run the command:" msgstr "" -#: ../../../docs/maintenance-migrating.md:66 +#: ../../../docs/maintenance-migrating.md:57 msgid "Install and start all services on the new server" msgstr "" -#: ../../../docs/maintenance-migrating.md:68 +#: ../../../docs/maintenance-migrating.md:59 msgid "Finally, run the command below on your local computer to finish the installation and start all services:" msgstr "" -#: ../../../docs/maintenance-migrating.md:74 +#: ../../../docs/maintenance-migrating.md:65 msgid "The shortcut command with `just` program is also available: `just run-tags install-all,start`" msgstr "" -#: ../../../docs/maintenance-migrating.md:76 +#: ../../../docs/maintenance-migrating.md:67 msgid "Check if services work" msgstr "" -#: ../../../docs/maintenance-migrating.md:78 -msgid "After starting the services, you probably might want to ensure that you've migrated things correctly and that services are running. For instructions, see: [check if services work](maintenance-and-troubleshooting.md#how-to-check-if-services-work)" +#: ../../../docs/maintenance-migrating.md:69 +msgid "After starting the services, you probably might want to ensure that you've migrated things correctly and that services are running. For instructions, see: [check if services work](maintenance-checking-services.md)" msgstr "" -#: ../../../docs/maintenance-migrating.md:80 +#: ../../../docs/maintenance-migrating.md:71 msgid "Having make sure that both services and federation work as expected, you can safely shutdown the old server." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-postgres.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-postgres.po index a4b8b4fa2..adde96128 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-postgres.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-postgres.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,204 +18,204 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/maintenance-postgres.md:13 +#: ../../../docs/maintenance-postgres.md:1 msgid "PostgreSQL maintenance" msgstr "" -#: ../../../docs/maintenance-postgres.md:15 +#: ../../../docs/maintenance-postgres.md:3 msgid "This document shows you how to perform various maintenance tasks related to the Postgres database server used by Matrix." msgstr "" -#: ../../../docs/maintenance-postgres.md:17 +#: ../../../docs/maintenance-postgres.md:5 msgid "Table of contents:" msgstr "" -#: ../../../docs/maintenance-postgres.md:18 +#: ../../../docs/maintenance-postgres.md:7 msgid "[Getting a database terminal](#getting-a-database-terminal), for when you wish to execute SQL queries" msgstr "" -#: ../../../docs/maintenance-postgres.md:19 +#: ../../../docs/maintenance-postgres.md:9 msgid "[Vacuuming PostgreSQL](#vacuuming-postgresql), for when you wish to run a Postgres [VACUUM](https://www.postgresql.org/docs/current/sql-vacuum.html) (optimizing disk space)" msgstr "" -#: ../../../docs/maintenance-postgres.md:20 +#: ../../../docs/maintenance-postgres.md:11 msgid "[Backing up PostgreSQL](#backing-up-postgresql), for when you wish to make a backup" msgstr "" -#: ../../../docs/maintenance-postgres.md:21 +#: ../../../docs/maintenance-postgres.md:13 msgid "[Upgrading PostgreSQL](#upgrading-postgresql), for upgrading to new major versions of PostgreSQL. Such **manual upgrades are sometimes required**." msgstr "" -#: ../../../docs/maintenance-postgres.md:22 +#: ../../../docs/maintenance-postgres.md:15 msgid "[Tuning PostgreSQL](#tuning-postgresql) to make it run faster" msgstr "" -#: ../../../docs/maintenance-postgres.md:24 +#: ../../../docs/maintenance-postgres.md:17 msgid "Getting a database terminal" msgstr "" -#: ../../../docs/maintenance-postgres.md:26 -msgid "You can use the `/matrix/postgres/bin/cli` tool to get interactive terminal access ([psql](https://www.postgresql.org/docs/current/app-psql.html)) to the PostgreSQL server." +#: ../../../docs/maintenance-postgres.md:19 +msgid "You can use the `/matrix/postgres/bin/cli` tool to get interactive terminal access ([psql](https://www.postgresql.org/docs/11/app-psql.html)) to the PostgreSQL server." msgstr "" -#: ../../../docs/maintenance-postgres.md:28 +#: ../../../docs/maintenance-postgres.md:21 msgid "If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above tool will not be available." msgstr "" -#: ../../../docs/maintenance-postgres.md:30 +#: ../../../docs/maintenance-postgres.md:23 msgid "By default, this tool puts you in the `matrix` database, which contains nothing." msgstr "" -#: ../../../docs/maintenance-postgres.md:32 +#: ../../../docs/maintenance-postgres.md:25 msgid "To see the available databases, run `\\list` (or just `\\l`)." msgstr "" -#: ../../../docs/maintenance-postgres.md:34 +#: ../../../docs/maintenance-postgres.md:27 msgid "To change to another database (for example `synapse`), run `\\connect synapse` (or just `\\c synapse`)." msgstr "" -#: ../../../docs/maintenance-postgres.md:36 +#: ../../../docs/maintenance-postgres.md:29 msgid "You can then proceed to write queries. Example: `SELECT COUNT(*) FROM users;`" msgstr "" -#: ../../../docs/maintenance-postgres.md:38 -msgid "[!WARNING] **Modifying the database directly (especially as services are running) is dangerous and may lead to irreversible database corruption.** When in doubt, consider [making a backup](#backing-up-postgresql)." +#: ../../../docs/maintenance-postgres.md:31 +msgid "**Be careful**. Modifying the database directly (especially as services are running) is dangerous and may lead to irreversible database corruption. When in doubt, consider [making a backup](#backing-up-postgresql)." msgstr "" -#: ../../../docs/maintenance-postgres.md:41 +#: ../../../docs/maintenance-postgres.md:33 msgid "Vacuuming PostgreSQL" msgstr "" -#: ../../../docs/maintenance-postgres.md:43 +#: ../../../docs/maintenance-postgres.md:35 msgid "Deleting lots data from Postgres does not make it release disk space, until you perform a [`VACUUM` operation](https://www.postgresql.org/docs/current/sql-vacuum.html)." msgstr "" -#: ../../../docs/maintenance-postgres.md:45 +#: ../../../docs/maintenance-postgres.md:37 msgid "You can run different `VACUUM` operations via the playbook, with the default preset being `vacuum-complete`:" msgstr "" -#: ../../../docs/maintenance-postgres.md:47 +#: ../../../docs/maintenance-postgres.md:39 msgid "(default) `vacuum-complete`: stops all services temporarily and runs `VACUUM FULL VERBOSE ANALYZE`." msgstr "" -#: ../../../docs/maintenance-postgres.md:48 +#: ../../../docs/maintenance-postgres.md:40 msgid "`vacuum-full`: stops all services temporarily and runs `VACUUM FULL VERBOSE`" msgstr "" -#: ../../../docs/maintenance-postgres.md:49 +#: ../../../docs/maintenance-postgres.md:41 msgid "`vacuum`: runs `VACUUM VERBOSE` without stopping any services" msgstr "" -#: ../../../docs/maintenance-postgres.md:50 +#: ../../../docs/maintenance-postgres.md:42 msgid "`vacuum-analyze` runs `VACUUM VERBOSE ANALYZE` without stopping any services" msgstr "" -#: ../../../docs/maintenance-postgres.md:51 +#: ../../../docs/maintenance-postgres.md:43 msgid "`analyze` runs `ANALYZE VERBOSE` without stopping any services (this is just [ANALYZE](https://www.postgresql.org/docs/current/sql-analyze.html) without doing a vacuum, so it's faster)" msgstr "" -#: ../../../docs/maintenance-postgres.md:53 +#: ../../../docs/maintenance-postgres.md:45 msgid "**Note**: for the `vacuum-complete` and `vacuum-full` presets, you'll need plenty of available disk space in your Postgres data directory (usually `/matrix/postgres/data`). These presets also stop all services (e.g. Synapse, etc.) while the vacuum operation is running." msgstr "" -#: ../../../docs/maintenance-postgres.md:55 +#: ../../../docs/maintenance-postgres.md:47 msgid "Example playbook invocations:" msgstr "" -#: ../../../docs/maintenance-postgres.md:57 +#: ../../../docs/maintenance-postgres.md:49 msgid "`just run-tags run-postgres-vacuum`: runs the default `vacuum-complete` preset and restarts all services" msgstr "" -#: ../../../docs/maintenance-postgres.md:58 +#: ../../../docs/maintenance-postgres.md:50 msgid "`just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze`: runs the `analyze` preset with all services remaining operational at all times" msgstr "" -#: ../../../docs/maintenance-postgres.md:60 +#: ../../../docs/maintenance-postgres.md:52 msgid "Backing up PostgreSQL" msgstr "" -#: ../../../docs/maintenance-postgres.md:62 -msgid "To automatically make Postgres database backups on a fixed schedule, consider enabling the [Postgres Backup](configuring-playbook-postgres-backup.md) service." +#: ../../../docs/maintenance-postgres.md:54 +msgid "To automatically make Postgres database backups on a fixed schedule, see [Setting up postgres backup](configuring-playbook-postgres-backup.md)." msgstr "" -#: ../../../docs/maintenance-postgres.md:64 -msgid "To make a one-off back up of the current PostgreSQL database, make sure it's running and then execute a command like this on the server:" +#: ../../../docs/maintenance-postgres.md:56 +msgid "To make a one off back up of the current PostgreSQL database, make sure it's running and then execute a command like this on the server:" msgstr "" -#: ../../../docs/maintenance-postgres.md:75 +#: ../../../docs/maintenance-postgres.md:67 msgid "If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above command will not work, because neither the credentials file (`/matrix/postgres/env-postgres-psql`), nor the `matrix-postgres` container is available." msgstr "" -#: ../../../docs/maintenance-postgres.md:77 +#: ../../../docs/maintenance-postgres.md:69 msgid "Restoring a backup made this way can be done by [importing it](importing-postgres.md)." msgstr "" -#: ../../../docs/maintenance-postgres.md:79 +#: ../../../docs/maintenance-postgres.md:71 msgid "Upgrading PostgreSQL" msgstr "" -#: ../../../docs/maintenance-postgres.md:81 +#: ../../../docs/maintenance-postgres.md:73 msgid "Unless you are using an [external Postgres server](configuring-playbook-external-postgres.md), this playbook initially installs Postgres for you." msgstr "" -#: ../../../docs/maintenance-postgres.md:83 +#: ../../../docs/maintenance-postgres.md:75 msgid "Once installed, the playbook attempts to preserve the Postgres version it starts with. This is because newer Postgres versions cannot start with data generated by older Postgres versions." msgstr "" -#: ../../../docs/maintenance-postgres.md:85 +#: ../../../docs/maintenance-postgres.md:77 msgid "Upgrades must be performed manually." msgstr "" -#: ../../../docs/maintenance-postgres.md:87 +#: ../../../docs/maintenance-postgres.md:79 msgid "The playbook can upgrade your existing Postgres setup with the following command:" msgstr "" -#: ../../../docs/maintenance-postgres.md:93 +#: ../../../docs/maintenance-postgres.md:85 msgid "**The old Postgres data directory is backed up** automatically, by renaming it to `/matrix/postgres/data-auto-upgrade-backup`. To rename to a different path, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_auto_upgrade_backup_data_path=/another/disk/matrix-postgres-before-upgrade\"`" msgstr "" -#: ../../../docs/maintenance-postgres.md:95 +#: ../../../docs/maintenance-postgres.md:87 msgid "The auto-upgrade-backup directory stays around forever, until you **manually decide to delete it**." msgstr "" -#: ../../../docs/maintenance-postgres.md:97 +#: ../../../docs/maintenance-postgres.md:89 msgid "As part of the upgrade, the database is dumped to `/tmp`, an upgraded and empty Postgres server is started, and then the dump is restored into the new server. To use a different directory for the dump, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_dump_dir=/directory/to/dump/here\"`" msgstr "" -#: ../../../docs/maintenance-postgres.md:99 +#: ../../../docs/maintenance-postgres.md:91 msgid "To save disk space in `/tmp`, the dump file is gzipped on the fly at the expense of CPU usage. If you have plenty of space in `/tmp` and would rather avoid gzipping, you can explicitly pass a dump filename which doesn't end in `.gz`. Example: `--extra-vars=\"postgres_dump_name=matrix-postgres-dump.sql\"`" msgstr "" -#: ../../../docs/maintenance-postgres.md:101 -msgid "**All databases, roles, etc. on the Postgres server are migrated**. However, other components that depend on specific Postgres versions (like the [Postgres Backup](configuring-playbook-postgres-backup.md) service) may need to be updated after the upgrade by using `just install-all`" +#: ../../../docs/maintenance-postgres.md:93 +msgid "**All databases, roles, etc. on the Postgres server are migrated**." msgstr "" -#: ../../../docs/maintenance-postgres.md:103 +#: ../../../docs/maintenance-postgres.md:95 msgid "Tuning PostgreSQL" msgstr "" -#: ../../../docs/maintenance-postgres.md:105 +#: ../../../docs/maintenance-postgres.md:97 msgid "PostgreSQL can be [tuned](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) to make it run faster. This is done by passing extra arguments to the Postgres process." msgstr "" -#: ../../../docs/maintenance-postgres.md:107 -msgid "The [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) **already does some tuning by default**, which matches the [tuning logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) done by websites like https://pgtune.leopard.in.ua/. You can manually influence some of the tuning variables. These parameters (variables) are injected via the `postgres_postgres_process_extra_arguments_default` variable." +#: ../../../docs/maintenance-postgres.md:99 +msgid "The [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) **already does some tuning by default**, which matches the [tuning logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) done by websites like https://pgtune.leopard.in.ua/. You can manually influence some of the tuning variables. These parameters (variables) are injected via the `postgres_postgres_process_extra_arguments_auto` variable." msgstr "" -#: ../../../docs/maintenance-postgres.md:109 +#: ../../../docs/maintenance-postgres.md:101 msgid "Most users should be fine with the automatically-done tuning. However, you may wish to:" msgstr "" -#: ../../../docs/maintenance-postgres.md:111 -msgid "**adjust the automatically-determined tuning parameters manually**: change the values for the tuning variables defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) (see `postgres_max_connections`, `postgres_data_storage` etc). These variables are ultimately passed to Postgres via a `postgres_postgres_process_extra_arguments_default` variable" +#: ../../../docs/maintenance-postgres.md:103 +msgid "**adjust the automatically-determined tuning parameters manually**: change the values for the tuning variables defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) (see `postgres_max_connections`, `postgres_data_storage` etc). These variables are ultimately passed to Postgres via a `postgres_postgres_process_extra_arguments_auto` variable" msgstr "" -#: ../../../docs/maintenance-postgres.md:113 -msgid "**turn automatically-performed tuning off**: override it like this: `postgres_postgres_process_extra_arguments_default: []`" +#: ../../../docs/maintenance-postgres.md:105 +msgid "**turn automatically-performed tuning off**: override it like this: `postgres_postgres_process_extra_arguments_auto: []`" msgstr "" -#: ../../../docs/maintenance-postgres.md:115 -msgid "**add additional tuning parameters**: define your additional Postgres configuration parameters in `postgres_postgres_process_extra_arguments_custom`. See `postgres_postgres_process_extra_arguments_default` defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) for inspiration" +#: ../../../docs/maintenance-postgres.md:107 +msgid "**add additional tuning parameters**: define your additional Postgres configuration parameters in `postgres_postgres_process_extra_arguments_custom`. See `postgres_postgres_process_extra_arguments_auto` defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) for inspiration" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-synapse.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-synapse.po index cc0206864..ce45f3f8f 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-synapse.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-synapse.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,192 +18,184 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/maintenance-synapse.md:12 +#: ../../../docs/maintenance-synapse.md:1 msgid "Synapse maintenance" msgstr "" -#: ../../../docs/maintenance-synapse.md:14 +#: ../../../docs/maintenance-synapse.md:3 msgid "This document shows you how to perform various maintenance tasks related to the Synapse chat server." msgstr "" -#: ../../../docs/maintenance-synapse.md:16 +#: ../../../docs/maintenance-synapse.md:5 msgid "Table of contents:" msgstr "" -#: ../../../docs/maintenance-synapse.md:17 +#: ../../../docs/maintenance-synapse.md:7 msgid "[Purging old data with the Purge History API](#purging-old-data-with-the-purge-history-api), for when you wish to delete in-use (but old) data from the Synapse database" msgstr "" -#: ../../../docs/maintenance-synapse.md:18 +#: ../../../docs/maintenance-synapse.md:9 msgid "[Compressing state with rust-synapse-compress-state](#compressing-state-with-rust-synapse-compress-state)" msgstr "" -#: ../../../docs/maintenance-synapse.md:19 +#: ../../../docs/maintenance-synapse.md:11 msgid "[Browse and manipulate the database](#browse-and-manipulate-the-database), for when you really need to take matters into your own hands" msgstr "" -#: ../../../docs/maintenance-synapse.md:20 +#: ../../../docs/maintenance-synapse.md:13 msgid "[Make Synapse faster](#make-synapse-faster)" msgstr "" -#: ../../../docs/maintenance-synapse.md:22 -msgid "💡 See this page for details about configuring Synapse: [Configuring Synapse](configuring-playbook-synapse.md)" -msgstr "" - -#: ../../../docs/maintenance-synapse.md:24 +#: ../../../docs/maintenance-synapse.md:15 msgid "Purging old data with the Purge History API" msgstr "" -#: ../../../docs/maintenance-synapse.md:26 +#: ../../../docs/maintenance-synapse.md:17 msgid "You can use the **[Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md)** to delete old messages on a per-room basis. **This is destructive** (especially for non-federated rooms), because it means **people will no longer have access to history past a certain point**." msgstr "" -#: ../../../docs/maintenance-synapse.md:28 +#: ../../../docs/maintenance-synapse.md:19 msgid "To make use of this Synapse Admin API, **you'll need an admin access token** first. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" -#: ../../../docs/maintenance-synapse.md:30 +#: ../../../docs/maintenance-synapse.md:21 msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" -#: ../../../docs/maintenance-synapse.md:33 +#: ../../../docs/maintenance-synapse.md:24 msgid "Synapse's Admin API is not exposed to the internet by default, following [official Synapse reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints). To expose it you will need to add `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` to your `vars.yml` file." msgstr "" -#: ../../../docs/maintenance-synapse.md:35 +#: ../../../docs/maintenance-synapse.md:26 msgid "Follow the [Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md) documentation page for the actual purging instructions." msgstr "" -#: ../../../docs/maintenance-synapse.md:37 +#: ../../../docs/maintenance-synapse.md:28 msgid "After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." msgstr "" -#: ../../../docs/maintenance-synapse.md:39 +#: ../../../docs/maintenance-synapse.md:30 msgid "Compressing state with rust-synapse-compress-state" msgstr "" -#: ../../../docs/maintenance-synapse.md:41 +#: ../../../docs/maintenance-synapse.md:32 msgid "[rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) can be used to optimize some `_state` tables used by Synapse. If your server participates in large rooms this is the most effective way to reduce the size of your database." msgstr "" -#: ../../../docs/maintenance-synapse.md:43 +#: ../../../docs/maintenance-synapse.md:34 msgid "**Note**: besides running the `rust-synapse-compress-state` tool manually, you can also enable its `synapse-auto-compressor` tool by [Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md). The automatic tool will run on a schedule every day and you won't have to compress state manually ever again." msgstr "" -#: ../../../docs/maintenance-synapse.md:45 +#: ../../../docs/maintenance-synapse.md:36 msgid "`rust-synapse-compress-state` should be safe to use (even when Synapse is running), but it's always a good idea to [make Postgres backups](./maintenance-postgres.md#backing-up-postgresql) first." msgstr "" -#: ../../../docs/maintenance-synapse.md:47 +#: ../../../docs/maintenance-synapse.md:38 msgid "To ask the playbook to run rust-synapse-compress-state, execute:" msgstr "" -#: ../../../docs/maintenance-synapse.md:53 +#: ../../../docs/maintenance-synapse.md:44 msgid "The shortcut command with `just` program is also available: `just run-tags rust-synapse-compress-state`" msgstr "" -#: ../../../docs/maintenance-synapse.md:55 +#: ../../../docs/maintenance-synapse.md:46 msgid "By default, all rooms with more than `100000` state group rows will be compressed. If you need to adjust this, pass: `--extra-vars='matrix_synapse_rust_synapse_compress_state_min_state_groups_required=SOME_NUMBER_HERE'` to the command above." msgstr "" -#: ../../../docs/maintenance-synapse.md:57 +#: ../../../docs/maintenance-synapse.md:48 msgid "After state compression, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." msgstr "" -#: ../../../docs/maintenance-synapse.md:59 +#: ../../../docs/maintenance-synapse.md:50 msgid "Browse and manipulate the database" msgstr "" -#: ../../../docs/maintenance-synapse.md:61 +#: ../../../docs/maintenance-synapse.md:52 msgid "When the [Synapse Admin API](https://github.com/element-hq/synapse/tree/master/docs/admin_api) and the other tools do not provide a more convenient way, having a look at synapse's postgresql database can satisfy a lot of admins' needs." msgstr "" -#: ../../../docs/maintenance-synapse.md:63 +#: ../../../docs/maintenance-synapse.md:54 msgid "Editing the database manually is not recommended or supported by the Synapse developers. If you are going to do so you should [make a database backup](./maintenance-postgres.md#backing-up-postgresql)." msgstr "" -#: ../../../docs/maintenance-synapse.md:65 +#: ../../../docs/maintenance-synapse.md:56 msgid "First, set up an SSH tunnel to your Matrix server (skip if it is your local machine):" msgstr "" -#: ../../../docs/maintenance-synapse.md:72 +#: ../../../docs/maintenance-synapse.md:63 msgid "Then start up an ephemeral [adminer](https://www.adminer.org/) container on the Matrix server, connecting it to the `matrix` network and linking the postgresql container:" msgstr "" -#: ../../../docs/maintenance-synapse.md:78 +#: ../../../docs/maintenance-synapse.md:69 msgid "You should then be able to browse the adminer database administration GUI at http://localhost:1799/ after entering your DB credentials (found in the `host_vars` or on the server in `{{matrix_synapse_config_dir_path}}/homeserver.yaml` under `database.args`)" msgstr "" -#: ../../../docs/maintenance-synapse.md:80 +#: ../../../docs/maintenance-synapse.md:71 msgid "⚠️️ Be **very careful** with this, there is **no undo** for impromptu DB operations." msgstr "" -#: ../../../docs/maintenance-synapse.md:82 +#: ../../../docs/maintenance-synapse.md:73 msgid "Make Synapse faster" msgstr "" -#: ../../../docs/maintenance-synapse.md:84 +#: ../../../docs/maintenance-synapse.md:75 msgid "Synapse's presence feature which tracks which users are online and which are offline can use a lot of processing power. You can disable presence by adding `matrix_synapse_presence_enabled: false` to your `vars.yml` file." msgstr "" -#: ../../../docs/maintenance-synapse.md:86 -msgid "On smaller servers, consider limiting joins to very complex rooms with [the room complexity guard](configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts)." -msgstr "" - -#: ../../../docs/maintenance-synapse.md:88 +#: ../../../docs/maintenance-synapse.md:77 msgid "If you have enough compute resources (CPU & RAM), you can make Synapse better use of them by [enabling load-balancing with workers](configuring-playbook-synapse.md#load-balancing-with-workers)." msgstr "" -#: ../../../docs/maintenance-synapse.md:90 +#: ../../../docs/maintenance-synapse.md:79 msgid "[Tuning your PostgreSQL database](maintenance-postgres.md#tuning-postgresql) could also improve Synapse performance. The playbook tunes the integrated Postgres database automatically, but based on your needs you may wish to adjust tuning variables manually. If you're using an [external Postgres database](configuring-playbook-external-postgres.md), you will also need to tune Postgres manually." msgstr "" -#: ../../../docs/maintenance-synapse.md:92 +#: ../../../docs/maintenance-synapse.md:81 msgid "Tuning caches and cache autotuning" msgstr "" -#: ../../../docs/maintenance-synapse.md:94 +#: ../../../docs/maintenance-synapse.md:83 msgid "Tuning Synapse's cache factor is useful for performance increases but also as part of controlling Synapse's memory use. Use the variable `matrix_synapse_caches_global_factor` to set the cache factor as part of this process." msgstr "" -#: ../../../docs/maintenance-synapse.md:96 +#: ../../../docs/maintenance-synapse.md:85 msgid "**The playbook defaults the global cache factor to a large value** (e.g. `10`). A smaller value (e.g. `0.5`) will decrease the amount used for caches, but will [not necessarily decrease RAM usage as a whole](https://github.com/matrix-org/synapse/issues/3939)." msgstr "" -#: ../../../docs/maintenance-synapse.md:98 +#: ../../../docs/maintenance-synapse.md:87 msgid "Tuning the cache factor is useful only to a limited degree (as its crude to do in isolation) and therefore users who are tuning their cache factor should likely look into tuning autotune variables as well (see below)." msgstr "" -#: ../../../docs/maintenance-synapse.md:100 +#: ../../../docs/maintenance-synapse.md:89 msgid "Cache autotuning is **enabled by default** and controlled via the following variables:" msgstr "" -#: ../../../docs/maintenance-synapse.md:102 +#: ../../../docs/maintenance-synapse.md:91 msgid "`matrix_synapse_cache_autotuning_max_cache_memory_usage` — defaults to 1/8 of total RAM with a cap of 2GB; values are specified in bytes" msgstr "" -#: ../../../docs/maintenance-synapse.md:103 +#: ../../../docs/maintenance-synapse.md:92 msgid "`matrix_synapse_cache_autotuning_target_cache_memory_usage` — defaults to 1/16 of total RAM with a cap of 1GB; values are specified in bytes" msgstr "" -#: ../../../docs/maintenance-synapse.md:104 +#: ../../../docs/maintenance-synapse.md:93 msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` — defaults to `30s`" msgstr "" -#: ../../../docs/maintenance-synapse.md:106 +#: ../../../docs/maintenance-synapse.md:95 msgid "You can **learn more about cache-autotuning and the global cache factor settings** in the [Synapse's documentation on caches and associated values](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values)." msgstr "" -#: ../../../docs/maintenance-synapse.md:108 +#: ../../../docs/maintenance-synapse.md:97 msgid "To **disable cache auto-tuning**, unset all values:" msgstr "" -#: ../../../docs/maintenance-synapse.md:116 +#: ../../../docs/maintenance-synapse.md:105 msgid "Users who wish to lower Synapse's RAM footprint should look into lowering the global cache factor and tweaking the autotune variables (or disabling auto-tuning). If your cache factor is too low for a given auto tune setting your caches will not reach autotune thresholds and autotune won't be able to do its job. Therefore, when auto-tuning is enabled (which it is by default), it's recommended to have your cache factor be large." msgstr "" -#: ../../../docs/maintenance-synapse.md:118 +#: ../../../docs/maintenance-synapse.md:107 msgid "See also [How do I optimize this setup for a low-power server?](faq.md#how-do-i-optimize-this-setup-for-a-low-power-server)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/playbook-tags.po b/i18n/locales/jp/LC_MESSAGES/docs/playbook-tags.po index c3bdb1947..13642e626 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/playbook-tags.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/playbook-tags.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,68 +18,60 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/playbook-tags.md:8 +#: ../../../docs/playbook-tags.md:1 msgid "Playbook tags" msgstr "" -#: ../../../docs/playbook-tags.md:10 +#: ../../../docs/playbook-tags.md:3 msgid "The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks." msgstr "" -#: ../../../docs/playbook-tags.md:12 -msgid "The general command syntax is:" +#: ../../../docs/playbook-tags.md:5 +msgid "The general command syntax is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`" msgstr "" -#: ../../../docs/playbook-tags.md:13 -msgid "(**recommended**) when using `just`: `just run-tags COMMA_SEPARATED_TAGS_GO_HERE`" -msgstr "" - -#: ../../../docs/playbook-tags.md:14 -msgid "when not using `just`: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`" -msgstr "" - -#: ../../../docs/playbook-tags.md:16 +#: ../../../docs/playbook-tags.md:7 msgid "Here are some playbook tags that you should be familiar with:" msgstr "" -#: ../../../docs/playbook-tags.md:18 +#: ../../../docs/playbook-tags.md:9 msgid "`setup-all` — runs all setup tasks (installation and uninstallation) for all components, but does not start/restart services" msgstr "" -#: ../../../docs/playbook-tags.md:20 +#: ../../../docs/playbook-tags.md:11 msgid "`install-all` — like `setup-all`, but skips uninstallation tasks. Useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove components, you'd need to run `setup-all` though, or these components will still remain installed" msgstr "" -#: ../../../docs/playbook-tags.md:22 +#: ../../../docs/playbook-tags.md:13 msgid "`setup-SERVICE` (e.g. `setup-postmoogle`) — runs the setup tasks only for a given role, but does not start/restart services. You can discover these additional tags in each role (`roles/**/tasks/main.yml`). Running per-component setup tasks is **not recommended**, as components sometimes depend on each other and running just the setup tasks for a given component may not be enough. For example, setting up the [mautrix-telegram bridge](configuring-playbook-bridge-mautrix-telegram.md), in addition to the `setup-mautrix-telegram` tag, requires database changes (the `setup-postgres` tag) as well as reverse-proxy changes (the `setup-nginx-proxy` tag)." msgstr "" -#: ../../../docs/playbook-tags.md:24 +#: ../../../docs/playbook-tags.md:15 msgid "`install-SERVICE` (e.g. `install-postmoogle`) — like `setup-SERVICE`, but skips uninstallation tasks. See `install-all` above for additional information." msgstr "" -#: ../../../docs/playbook-tags.md:26 +#: ../../../docs/playbook-tags.md:17 msgid "`start` — starts all systemd services and makes them start automatically in the future" msgstr "" -#: ../../../docs/playbook-tags.md:28 +#: ../../../docs/playbook-tags.md:19 msgid "`stop` — stops all systemd services" msgstr "" -#: ../../../docs/playbook-tags.md:30 -msgid "`ensure-matrix-users-created` or its alias `ensure-users-created` — a special tag which ensures that all special users needed by the playbook (for bots, etc.) are created. See the variable `matrix_user_creator_users_auto` on [`group_vars/matrix_servers`](../group_vars/matrix_servers) for actual values of users which running this tag can create by default." +#: ../../../docs/playbook-tags.md:21 +msgid "`ensure-matrix-users-created` — a special tag which ensures that all special users needed by the playbook (for bots, etc.) are created" msgstr "" -#: ../../../docs/playbook-tags.md:32 +#: ../../../docs/playbook-tags.md:23 msgid "**Notes**:" msgstr "" -#: ../../../docs/playbook-tags.md:33 +#: ../../../docs/playbook-tags.md:24 msgid "`setup-*` tags and `install-*` tags **do not start services** automatically, because you may wish to do things before starting services, such as importing a database dump, restoring data from another server, etc." msgstr "" -#: ../../../docs/playbook-tags.md:34 +#: ../../../docs/playbook-tags.md:25 msgid "Please be careful not to confuse the playbook tags with the `just` shortcut commands (\"recipes\"). For details about `just` commands, see: [Running `just` commands](just.md)" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/prerequisites.po b/i18n/locales/jp/LC_MESSAGES/docs/prerequisites.po index 126fa6cd3..37a069f73 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/prerequisites.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/prerequisites.po @@ -10,7 +10,7 @@ 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" +"POT-Creation-Date: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,124 +18,148 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/prerequisites.md:12 +#: ../../../docs/prerequisites.md:1 msgid "Prerequisites" msgstr "" -#: ../../../docs/prerequisites.md:14 -msgid "Prerequisites > [Configuring DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)" +#: ../../../docs/prerequisites.md:3 +msgid "Prerequisites > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)" msgstr "" -#: ../../../docs/prerequisites.md:16 +#: ../../../docs/prerequisites.md:5 msgid "To install Matrix services using this Ansible playbook, you need to prepare several requirements both on your local computer (where you will run the playbook to configure the server) and the server (where the playbook will install the Matrix services for you). **These requirements need to be set up manually** before proceeding to the next step." msgstr "" -#: ../../../docs/prerequisites.md:18 +#: ../../../docs/prerequisites.md:7 msgid "We will be using `example.com` as the domain in the following instruction. Please remember to replace it with your own domain before running any commands." msgstr "" -#: ../../../docs/prerequisites.md:20 +#: ../../../docs/prerequisites.md:9 msgid "**Note**: if you do not have an existing Matrix server and want to start quickly with \"opinionated defaults\", we suggest you to follow ⚡ **[Quick start](quick-start.md)** installation guide." msgstr "" -#: ../../../docs/prerequisites.md:22 +#: ../../../docs/prerequisites.md:11 msgid "Your local computer" msgstr "" -#: ../../../docs/prerequisites.md:24 +#: ../../../docs/prerequisites.md:13 msgid "[Ansible](http://ansible.com/) program. It's used to run this playbook and configures your server for you. Take a look at [our guide about Ansible](ansible.md) for more information, as well as [version requirements](ansible.md#supported-ansible-versions) and alternative ways to run Ansible." msgstr "" -#: ../../../docs/prerequisites.md:26 +#: ../../../docs/prerequisites.md:15 +msgid "[passlib](https://passlib.readthedocs.io/en/stable/index.html) Python library. See [this official documentation](https://passlib.readthedocs.io/en/stable/install.html#installation-instructions) for an instruction to install it. On most distros, you need to install some `python-passlib` or `py3-passlib` package, etc." +msgstr "" + +#: ../../../docs/prerequisites.md:17 msgid "[`git`](https://git-scm.com/) as the recommended way to download the playbook. `git` may also be required on the server if you will be [self-building](self-building.md) components." msgstr "" -#: ../../../docs/prerequisites.md:28 -msgid "[`just`](https://github.com/casey/just) for running `just roles`, `just update`, etc. (see [`justfile`](../justfile)), although you can also run these commands manually. Take a look at this documentation for more information: [Running `just` commands](just.md)." +#: ../../../docs/prerequisites.md:19 +msgid "[`just`](https://github.com/casey/just) for running `just roles`, `just update`, etc. (see [`justfile`](../justfile)), although you can also run these commands manually. Take at look at this documentation for more information: [Running `just` commands](just.md)." msgstr "" -#: ../../../docs/prerequisites.md:30 +#: ../../../docs/prerequisites.md:21 msgid "Strong password (random strings) generator. The playbook often requires you to create a strong password and use it for settings on `vars.yml`, components, etc. As any tools should be fine, this playbook has adopted [`pwgen`](https://linux.die.net/man/1/pwgen) (running `pwgen -s 64 1`). [Password Tech](https://pwgen-win.sourceforge.io/), formerly known as \"PWGen for Windows\", is available as free and open source password generator for Windows. Generally, using a random generator available on the internet is not recommended." msgstr "" -#: ../../../docs/prerequisites.md:32 +#: ../../../docs/prerequisites.md:23 msgid "Server" msgstr "" -#: ../../../docs/prerequisites.md:34 +#: ../../../docs/prerequisites.md:25 msgid "(Recommended) An **x86** server ([What kind of server specs do I need?](faq.md#what-kind-of-server-specs-do-i-need)) running one of these operating systems that make use of [systemd](https://systemd.io/):" msgstr "" -#: ../../../docs/prerequisites.md:35 +#: ../../../docs/prerequisites.md:26 msgid "**Archlinux**" msgstr "" -#: ../../../docs/prerequisites.md:36 +#: ../../../docs/prerequisites.md:27 msgid "**CentOS**, **Rocky Linux**, **AlmaLinux**, or possibly other RHEL alternatives (although your mileage may vary)" msgstr "" -#: ../../../docs/prerequisites.md:37 +#: ../../../docs/prerequisites.md:28 msgid "**Debian** (10/Buster or newer)" msgstr "" -#: ../../../docs/prerequisites.md:38 +#: ../../../docs/prerequisites.md:29 msgid "**Ubuntu** (18.04 or newer, although [20.04 may be problematic](ansible.md#supported-ansible-versions) if you run the Ansible playbook on it)" msgstr "" -#: ../../../docs/prerequisites.md:40 +#: ../../../docs/prerequisites.md:31 msgid "Generally, newer is better. We only strive to support released stable versions of distributions, not betas or pre-releases. The playbook can take over your whole server or co-exist with other services that you have there." msgstr "" -#: ../../../docs/prerequisites.md:42 +#: ../../../docs/prerequisites.md:33 msgid "This playbook somewhat supports running on non-`amd64` architectures like ARM. See [Alternative Architectures](alternative-architectures.md)." msgstr "" -#: ../../../docs/prerequisites.md:44 +#: ../../../docs/prerequisites.md:35 msgid "If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container." msgstr "" -#: ../../../docs/prerequisites.md:46 +#: ../../../docs/prerequisites.md:37 msgid "`root` access to your server (or a user capable of elevating to `root` via `sudo`)." msgstr "" -#: ../../../docs/prerequisites.md:48 +#: ../../../docs/prerequisites.md:39 msgid "[Python](https://www.python.org/). Most distributions install Python by default, but some don't (e.g. Ubuntu 18.04) and require manual installation (something like `apt-get install python3`). On some distros, Ansible may incorrectly [detect the Python version](https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html) (2 vs 3) and you may need to explicitly specify the interpreter path in `inventory/hosts` during installation (e.g. `ansible_python_interpreter=/usr/bin/python3`)" msgstr "" -#: ../../../docs/prerequisites.md:50 -msgid "[sudo](https://www.sudo.ws/), even when you've configured Ansible to log in as `root`, because this Ansible playbook sometimes uses the Ansible [become](https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_privilege_escalation.html) module to perform tasks as another user (e.g. `matrix`) and the `become` module's default implementation uses `sudo`. Some distributions, like a minimal Debian net install, do not include the `sudo` package by default." +#: ../../../docs/prerequisites.md:41 +msgid "[sudo](https://www.sudo.ws/), even when you've configured Ansible to log in as `root`. Some distributions, like a minimal Debian net install, do not include the `sudo` package by default." msgstr "" -#: ../../../docs/prerequisites.md:52 +#: ../../../docs/prerequisites.md:43 msgid "An HTTPS-capable web server at the base domain name (`example.com`) which is capable of serving static files. Unless you decide to [Serve the base domain from the Matrix server](configuring-playbook-base-domain-serving.md) or alternatively, to use DNS SRV records for [Server Delegation](howto-server-delegation.md)." msgstr "" -#: ../../../docs/prerequisites.md:54 +#: ../../../docs/prerequisites.md:45 msgid "Properly configured DNS records for `example.com` (details in [Configuring DNS](configuring-dns.md))." msgstr "" -#: ../../../docs/prerequisites.md:56 +#: ../../../docs/prerequisites.md:47 msgid "Some TCP/UDP ports open. This playbook (actually [Docker itself](https://docs.docker.com/network/iptables/)) configures the server's internal firewall for you. In most cases, you don't need to do anything special. But **if your server is running behind another firewall**, you'd need to open these ports:" msgstr "" -#: ../../../docs/prerequisites.md:58 +#: ../../../docs/prerequisites.md:49 msgid "`80/tcp`: HTTP webserver" msgstr "" -#: ../../../docs/prerequisites.md:59 +#: ../../../docs/prerequisites.md:50 msgid "`443/tcp` and `443/udp`: HTTPS webserver" msgstr "" -#: ../../../docs/prerequisites.md:60 +#: ../../../docs/prerequisites.md:51 +msgid "`3478/tcp`: TURN over TCP (used by coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:52 +msgid "`3478/udp`: TURN over UDP (used by coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:53 +msgid "`5349/tcp`: TURN over TCP (used by coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:54 +msgid "`5349/udp`: TURN over UDP (used by coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:55 msgid "`8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. Some components like [Matrix User Verification Service](configuring-playbook-user-verification-service.md#open-matrix-federation-port) require this port to be opened **even with federation disabled**." msgstr "" -#: ../../../docs/prerequisites.md:61 +#: ../../../docs/prerequisites.md:56 +msgid "the range `49152-49172/udp`: TURN over UDP" +msgstr "" + +#: ../../../docs/prerequisites.md:57 msgid "potentially some other ports, depending on the additional (non-default) services that you enable in the **configuring the playbook** step (later on). Consult each service's documentation page in `docs/` for that." msgstr "" -#: ../../../docs/prerequisites.md:65 +#: ../../../docs/prerequisites.md:61 msgid "[▶️](configuring-dns.md) When ready to proceed, continue with [Configuring DNS](configuring-dns.md)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/quick-start.po b/i18n/locales/jp/LC_MESSAGES/docs/quick-start.po index 36b7f5b89..f582e5454 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/quick-start.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/quick-start.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,81 +18,81 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/quick-start.md:7 +#: ../../../docs/quick-start.md:1 msgid "Quick start" msgstr "" -#: ../../../docs/quick-start.md:15 +#: ../../../docs/quick-start.md:9 msgid "This page explains how to use this Ansible playbook to install Matrix services on your server with a minimal set of core services." msgstr "" -#: ../../../docs/quick-start.md:17 +#: ../../../docs/quick-start.md:11 msgid "We will be using `example.com` as the \"base domain\" in the following instruction." msgstr "" -#: ../../../docs/quick-start.md:19 +#: ../../../docs/quick-start.md:13 msgid "By following the instruction on this page, you will set up:" msgstr "" -#: ../../../docs/quick-start.md:21 +#: ../../../docs/quick-start.md:15 msgid "**your own Matrix server** on a `matrix.example.com` server, which is configured to present itself as `example.com`" msgstr "" -#: ../../../docs/quick-start.md:22 +#: ../../../docs/quick-start.md:16 msgid "**your user account** like `@alice:example.com` on the server" msgstr "" -#: ../../../docs/quick-start.md:23 +#: ../../../docs/quick-start.md:17 msgid "a **self-hosted Matrix client**, [Element Web](configuring-playbook-client-element-web.md) with the default subdomain at `element.example.com`" msgstr "" -#: ../../../docs/quick-start.md:24 +#: ../../../docs/quick-start.md:18 msgid "Matrix delegation, so that your `matrix.example.com` server (presenting itself as `example.com`) can join the Matrix Federation and communicate with any other server in the Matrix network" msgstr "" -#: ../../../docs/quick-start.md:26 +#: ../../../docs/quick-start.md:20 msgid "Please remember to replace `example.com` with your own domain before running any commands." msgstr "" -#: ../../../docs/quick-start.md:28 +#: ../../../docs/quick-start.md:22 msgid "Prerequisites" msgstr "" -#: ../../../docs/quick-start.md:30 +#: ../../../docs/quick-start.md:24 msgid "This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Prerequisites](prerequisites.md)" msgstr "" -#: ../../../docs/quick-start.md:32 +#: ../../../docs/quick-start.md:26 msgid "At first, **check prerequisites** and prepare for installation by setting up programs [on your own computer](prerequisites.md#your-local-computer) and [your server](prerequisites.md#server). You also need `root` access on your server (a user that could elevate to `root` via `sudo` also works)." msgstr "" -#: ../../../docs/quick-start.md:34 +#: ../../../docs/quick-start.md:28 msgid "When preparing your server, make sure to check [the server specs you need](faq.md#what-kind-of-server-specs-do-i-need). We recommend starting with a server having at least 2GB of memory." msgstr "" -#: ../../../docs/quick-start.md:40 +#: ../../../docs/quick-start.md:34 msgid "If you encounter an error during installation, please make sure that you have installed and configured programs correctly." msgstr "" -#: ../../../docs/quick-start.md:42 +#: ../../../docs/quick-start.md:36 msgid "One of the main reasons of basic errors is using an incompatible version of required software such as Ansible. Take a look at [our guide about Ansible](ansible.md) for more information. In short: installing the latest available version is recommended." msgstr "" -#: ../../../docs/quick-start.md:44 +#: ../../../docs/quick-start.md:38 msgid "Configure your DNS settings" msgstr "" -#: ../../../docs/quick-start.md:46 -msgid "This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Configuring DNS settings](configuring-dns.md)" +#: ../../../docs/quick-start.md:40 +msgid "This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Configuring your DNS settings](configuring-dns.md)" msgstr "" -#: ../../../docs/quick-start.md:48 +#: ../../../docs/quick-start.md:42 msgid "After installing and configuring prerequisites, you will need to **configure DNS records**." msgstr "" -#: ../../../docs/quick-start.md:50 +#: ../../../docs/quick-start.md:44 msgid "To configure Matrix services in the default settings, go to your DNS service provider, and adjust DNS records as below." msgstr "" @@ -133,15 +133,7 @@ msgid "-" msgstr "" #: ../../../docs/quick-start.md -msgid "`matrix-server-IPv4`" -msgstr "" - -#: ../../../docs/quick-start.md -msgid "AAAA" -msgstr "" - -#: ../../../docs/quick-start.md -msgid "`matrix-server-IPv6`" +msgid "`matrix-server-IP`" msgstr "" #: ../../../docs/quick-start.md @@ -156,290 +148,286 @@ msgstr "" msgid "`matrix.example.com`" msgstr "" -#: ../../../docs/quick-start.md:58 -msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IPv4/IPv6 address." -msgstr "" - -#: ../../../docs/quick-start.md:60 -msgid "If you don't have IPv6 connectivity yet, you can skip the `AAAA` record. For more details about IPv6, see the [Configuring IPv6](./configuring-ipv6.md) documentation page." +#: ../../../docs/quick-start.md:51 +msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)." msgstr "" -#: ../../../docs/quick-start.md:62 +#: ../../../docs/quick-start.md:53 msgid "It might take some time for the DNS records to propagate after creation." msgstr "" -#: ../../../docs/quick-start.md:64 +#: ../../../docs/quick-start.md:55 msgid "**💡 Note**: if you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\"" msgstr "" -#: ../../../docs/quick-start.md:66 +#: ../../../docs/quick-start.md:57 msgid "Get the playbook" msgstr "" -#: ../../../docs/quick-start.md:68 +#: ../../../docs/quick-start.md:59 msgid "This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Getting the playbook](getting-the-playbook.md)" msgstr "" -#: ../../../docs/quick-start.md:70 +#: ../../../docs/quick-start.md:61 msgid "Next, let's **get the playbook's source code**." msgstr "" -#: ../../../docs/quick-start.md:72 +#: ../../../docs/quick-start.md:63 msgid "We recommend to do so with [git](https://git-scm.com/) as it enables you to keep it up to date with the latest source code. While it is possible to download the playbook as a ZIP archive, it is not recommended." msgstr "" -#: ../../../docs/quick-start.md:74 +#: ../../../docs/quick-start.md:65 msgid "To get the playbook with git, install git on your computer, go to a directory, and run the command:" msgstr "" -#: ../../../docs/quick-start.md:80 +#: ../../../docs/quick-start.md:71 msgid "It will fetch the playbook to a new `matrix-docker-ansible-deploy` directory underneath the directory you are currently in." msgstr "" -#: ../../../docs/quick-start.md:82 +#: ../../../docs/quick-start.md:73 msgid "Configure the playbook" msgstr "" -#: ../../../docs/quick-start.md:84 +#: ../../../docs/quick-start.md:75 msgid "This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Configuring the playbook](configuring-playbook.md)" msgstr "" -#: ../../../docs/quick-start.md:86 +#: ../../../docs/quick-start.md:77 msgid "Now that the playbook was fetched, it is time to **configure** it per your needs." msgstr "" -#: ../../../docs/quick-start.md:88 +#: ../../../docs/quick-start.md:79 msgid "To install Matrix services with this playbook, you would at least need 2 configuration files." msgstr "" -#: ../../../docs/quick-start.md:90 +#: ../../../docs/quick-start.md:81 msgid "For your convenience, we have prepared example files of them ([`vars.yml`](../examples/vars.yml) and [`hosts`](../examples/hosts))." msgstr "" -#: ../../../docs/quick-start.md:92 +#: ../../../docs/quick-start.md:83 msgid "To start quickly based on these example files, go into the `matrix-docker-ansible-deploy` directory and follow the instructions below:" msgstr "" -#: ../../../docs/quick-start.md:94 +#: ../../../docs/quick-start.md:85 msgid "Create a directory to hold your configuration: `mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\"" msgstr "" -#: ../../../docs/quick-start.md:95 +#: ../../../docs/quick-start.md:86 msgid "Copy the sample configuration file: `cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`" msgstr "" -#: ../../../docs/quick-start.md:96 +#: ../../../docs/quick-start.md:87 msgid "Copy the sample inventory hosts file: `cp examples/hosts inventory/hosts`" msgstr "" -#: ../../../docs/quick-start.md:97 +#: ../../../docs/quick-start.md:88 msgid "Edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`)" msgstr "" -#: ../../../docs/quick-start.md:98 +#: ../../../docs/quick-start.md:89 msgid "Edit the inventory hosts file (`inventory/hosts`)" msgstr "" -#: ../../../docs/quick-start.md:100 +#: ../../../docs/quick-start.md:91 msgid "Before editing these 2 files, make sure to read explanations on them to understand what needs to be configured." msgstr "" -#: ../../../docs/quick-start.md:102 +#: ../../../docs/quick-start.md:93 msgid "**💡 Notes:**" msgstr "" -#: ../../../docs/quick-start.md:103 +#: ../../../docs/quick-start.md:94 msgid "If you are not in control of anything on the base domain, you would need to set additional configuration on `vars.yml`. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ." msgstr "" -#: ../../../docs/quick-start.md:104 +#: ../../../docs/quick-start.md:95 msgid "Certain configuration decisions (like the base domain configured in `matrix_domain` and homeserver implementation configured in `matrix_homeserver_implementation`) are final. If you make the wrong choice and wish to change it, you'll have to run the Uninstalling step and start over." msgstr "" -#: ../../../docs/quick-start.md:105 +#: ../../../docs/quick-start.md:96 msgid "Instead of configuring a lot of things all at once, we recommend starting with the basic (default) settings in order to get yourself familiar with how the playbook works. After making sure that everything works as expected, you can add (and remove) advanced settings / features and run the playbook as many times as you wish." msgstr "" -#: ../../../docs/quick-start.md:107 +#: ../../../docs/quick-start.md:98 msgid "Install" msgstr "" -#: ../../../docs/quick-start.md:109 +#: ../../../docs/quick-start.md:100 msgid "This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Installing](installing.md)" msgstr "" -#: ../../../docs/quick-start.md:111 +#: ../../../docs/quick-start.md:102 msgid "After editing `vars.yml` and `hosts` files, let's start the **installation** procedure." msgstr "" -#: ../../../docs/quick-start.md:113 +#: ../../../docs/quick-start.md:104 msgid "Update Ansible roles" msgstr "" -#: ../../../docs/quick-start.md:115 +#: ../../../docs/quick-start.md:106 msgid "Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside." msgstr "" -#: ../../../docs/quick-start.md:117 +#: ../../../docs/quick-start.md:108 msgid "To update your playbook directory and all upstream Ansible roles, run:" msgstr "" -#: ../../../docs/quick-start.md:119 +#: ../../../docs/quick-start.md:110 msgid "either: `just update`" msgstr "" -#: ../../../docs/quick-start.md:120 +#: ../../../docs/quick-start.md:111 msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)" msgstr "" -#: ../../../docs/quick-start.md:122 +#: ../../../docs/quick-start.md:113 msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`" msgstr "" -#: ../../../docs/quick-start.md:124 +#: ../../../docs/quick-start.md:115 msgid "Run installation command" msgstr "" -#: ../../../docs/quick-start.md:126 +#: ../../../docs/quick-start.md:117 msgid "Then, run the command below to start installation:" msgstr "" -#: ../../../docs/quick-start.md:132 +#: ../../../docs/quick-start.md:123 msgid "If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the command." msgstr "" -#: ../../../docs/quick-start.md:134 +#: ../../../docs/quick-start.md:125 msgid "If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to the command." msgstr "" -#: ../../../docs/quick-start.md:136 +#: ../../../docs/quick-start.md:127 msgid "Wait until the command completes. If it's all green, everything should be running properly." msgstr "" -#: ../../../docs/quick-start.md:138 +#: ../../../docs/quick-start.md:129 msgid "Create your user account" msgstr "" -#: ../../../docs/quick-start.md:140 +#: ../../../docs/quick-start.md:131 msgid "This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Registering users](registering-users.md)" msgstr "" -#: ../../../docs/quick-start.md:142 +#: ../../../docs/quick-start.md:133 msgid "As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server." msgstr "" -#: ../../../docs/quick-start.md:144 +#: ../../../docs/quick-start.md:135 msgid "To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer." msgstr "" -#: ../../../docs/quick-start.md:146 +#: ../../../docs/quick-start.md:137 msgid "**💡 Notes**:" msgstr "" -#: ../../../docs/quick-start.md:147 +#: ../../../docs/quick-start.md:138 msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`" msgstr "" -#: ../../../docs/quick-start.md:148 +#: ../../../docs/quick-start.md:139 msgid "For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)" msgstr "" -#: ../../../docs/quick-start.md:160 +#: ../../../docs/quick-start.md:151 msgid "Finalize server installation" msgstr "" -#: ../../../docs/quick-start.md:162 +#: ../../../docs/quick-start.md:153 msgid "This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Server Delegation](howto-server-delegation.md)" msgstr "" -#: ../../../docs/quick-start.md:164 +#: ../../../docs/quick-start.md:155 msgid "Now that you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network." msgstr "" -#: ../../../docs/quick-start.md:166 +#: ../../../docs/quick-start.md:157 msgid "**This is required for federation to work!** Without a proper configuration, your server will effectively not be part of the Matrix network." msgstr "" -#: ../../../docs/quick-start.md:168 +#: ../../../docs/quick-start.md:159 msgid "To configure the delegation, you have these two options. Choose one of them according to your situation." msgstr "" -#: ../../../docs/quick-start.md:170 +#: ../../../docs/quick-start.md:161 msgid "If you can afford to point the base domain at the Matrix server, follow the instruction below which guides you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server." msgstr "" -#: ../../../docs/quick-start.md:171 +#: ../../../docs/quick-start.md:162 msgid "Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot \"serve the base domain\" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server)." msgstr "" -#: ../../../docs/quick-start.md:173 +#: ../../../docs/quick-start.md:164 msgid "To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/quick-start.md:179 +#: ../../../docs/quick-start.md:170 msgid "After configuring the playbook, run the command below and wait until it finishes:" msgstr "" -#: ../../../docs/quick-start.md:185 +#: ../../../docs/quick-start.md:176 msgid "💡 Running the `install-matrix-static-files` playbook tag (as done here) is an optimized version of running [the full setup command](#run-installation-command)." msgstr "" -#: ../../../docs/quick-start.md:187 +#: ../../../docs/quick-start.md:178 msgid "After the command finishes, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain." msgstr "" -#: ../../../docs/quick-start.md:189 +#: ../../../docs/quick-start.md:180 msgid "Re-run the full setup command any time" msgstr "" -#: ../../../docs/quick-start.md:191 +#: ../../../docs/quick-start.md:182 msgid "If you think something is wrong with the server configuration, feel free to re-run the setup command any time:" msgstr "" -#: ../../../docs/quick-start.md:197 +#: ../../../docs/quick-start.md:188 msgid "Log in to your user account" msgstr "" -#: ../../../docs/quick-start.md:199 +#: ../../../docs/quick-start.md:190 msgid "Finally, let's make sure that you can log in to the created account with the specified password." msgstr "" -#: ../../../docs/quick-start.md:201 +#: ../../../docs/quick-start.md:192 msgid "You should be able to log in to it with your own [Element Web](configuring-playbook-client-element-web.md) client which you have set up at `element.example.com` by running the playbook. Open the URL (`https://element.example.com`) in a web browser and enter your credentials to log in." msgstr "" -#: ../../../docs/quick-start.md:203 -msgid "**If you successfully logged in to your account, the installation and configuration have completed successfully**🎉" +#: ../../../docs/quick-start.md:194 +msgid "**If you successfully logged in to your account, installing and configuring is complete**🎉" msgstr "" -#: ../../../docs/quick-start.md:205 +#: ../../../docs/quick-start.md:196 msgid "Come say Hi👋 in our support room — [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting." msgstr "" -#: ../../../docs/quick-start.md:207 +#: ../../../docs/quick-start.md:198 msgid "Things to do next" msgstr "" -#: ../../../docs/quick-start.md:209 +#: ../../../docs/quick-start.md:200 msgid "Once you get familiar with the playbook, you might probably want to set up additional services such as a bridge on your server." msgstr "" -#: ../../../docs/quick-start.md:211 +#: ../../../docs/quick-start.md:202 msgid "As this page intends to be a quick start guide which explains how to start the core Matrix services, it does not cover a topic like how to set them up. Take a look at the list of [things to do next](installing.md#things-to-do-next) to learn more." msgstr "" -#: ../../../docs/quick-start.md:213 +#: ../../../docs/quick-start.md:204 msgid "⚠️Keep the playbook and services up-to-date" msgstr "" -#: ../../../docs/quick-start.md:215 +#: ../../../docs/quick-start.md:206 msgid "While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**." msgstr "" -#: ../../../docs/quick-start.md:217 +#: ../../../docs/quick-start.md:208 msgid "Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date." msgstr "" -#: ../../../docs/quick-start.md:219 -msgid "For more information about upgrading or maintaining services with the playbook, take a look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)" +#: ../../../docs/quick-start.md:210 +msgid "For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/uninstalling.po b/i18n/locales/jp/LC_MESSAGES/docs/uninstalling.po index d6f169404..2c11b3a87 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/uninstalling.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/uninstalling.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,65 +18,64 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/uninstalling.md:9 +#: ../../../docs/uninstalling.md:1 msgid "Uninstalling" msgstr "" -#: ../../../docs/uninstalling.md:11 -msgid "[!WARNING]" +#: ../../../docs/uninstalling.md:3 +msgid "⚠️ **Warnings**:" msgstr "" -#: ../../../docs/uninstalling.md:12 +#: ../../../docs/uninstalling.md:4 msgid "If your server federates with others, make sure to **leave any federated rooms before nuking your Matrix server's data**. Otherwise, the next time you set up a Matrix server for this domain (regardless of the installation method you use), you'll encounter trouble federating." msgstr "" -#: ../../../docs/uninstalling.md:13 +#: ../../../docs/uninstalling.md:5 msgid "If you have some trouble with your installation, you can just [re-run the playbook](installing.md) and it will try to set things up again. **Uninstalling and then installing anew rarely solves anything**." msgstr "" -#: ../../../docs/uninstalling.md:15 +#: ../../../docs/uninstalling.md:9 msgid "Uninstalling using a script" msgstr "" -#: ../../../docs/uninstalling.md:17 +#: ../../../docs/uninstalling.md:11 msgid "Installing places a `/matrix/bin/remove-all` script on the server." msgstr "" -#: ../../../docs/uninstalling.md:19 +#: ../../../docs/uninstalling.md:13 msgid "You can run it to to have it uninstall things for you automatically (see below). **Use with caution!**" msgstr "" -#: ../../../docs/uninstalling.md:21 +#: ../../../docs/uninstalling.md:15 msgid "Uninstalling manually" msgstr "" -#: ../../../docs/uninstalling.md:23 +#: ../../../docs/uninstalling.md:17 msgid "If you prefer to uninstall manually, run these commands (most are meant to be executed on the Matrix server itself):" msgstr "" -#: ../../../docs/uninstalling.md:25 +#: ../../../docs/uninstalling.md:19 msgid "ensure all Matrix services are stopped: `ansible-playbook -i inventory/hosts setup.yml --tags=stop` (if you can't get Ansible working to run this command, you can run `systemctl stop 'matrix*'` manually on the server)" msgstr "" -#: ../../../docs/uninstalling.md:27 -#, python-brace-format +#: ../../../docs/uninstalling.md:21 msgid "delete the Matrix-related systemd `.service` and `.timer` files (`rm -f /etc/systemd/system/matrix*.{service,timer}`) and reload systemd (`systemctl daemon-reload`)" msgstr "" -#: ../../../docs/uninstalling.md:29 +#: ../../../docs/uninstalling.md:23 msgid "delete some cached Docker images (`docker system prune -a`) or just delete them all (`docker rmi $(docker images -aq)`)" msgstr "" -#: ../../../docs/uninstalling.md:31 +#: ../../../docs/uninstalling.md:25 msgid "delete the Docker networks: `docker network rm matrix matrix-coturn` (might have been deleted already if you ran the `docker system prune` command)" msgstr "" -#: ../../../docs/uninstalling.md:33 +#: ../../../docs/uninstalling.md:27 msgid "uninstall Docker itself, if necessary" msgstr "" -#: ../../../docs/uninstalling.md:35 +#: ../../../docs/uninstalling.md:29 msgid "delete the `/matrix` directory (`rm -rf /matrix`)" msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/updating-users-passwords.po b/i18n/locales/jp/LC_MESSAGES/docs/updating-users-passwords.po index faa31c7b9..a55d876e4 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/updating-users-passwords.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/updating-users-passwords.po @@ -10,7 +10,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: 2025-01-27 09:54+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,76 +18,76 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" -#: ../../../docs/updating-users-passwords.md:13 +#: ../../../docs/updating-users-passwords.md:1 msgid "Updating users passwords" msgstr "" -#: ../../../docs/updating-users-passwords.md:15 +#: ../../../docs/updating-users-passwords.md:3 msgid "Option 1 (if you are using the integrated Postgres database):" msgstr "" -#: ../../../docs/updating-users-passwords.md:17 +#: ../../../docs/updating-users-passwords.md:5 msgid "**Notes**:" msgstr "" -#: ../../../docs/updating-users-passwords.md:18 +#: ../../../docs/updating-users-passwords.md:6 msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`" msgstr "" -#: ../../../docs/updating-users-passwords.md:19 +#: ../../../docs/updating-users-passwords.md:7 msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)" msgstr "" -#: ../../../docs/updating-users-passwords.md:21 +#: ../../../docs/updating-users-passwords.md:9 msgid "You can reset a user's password via the Ansible playbook:" msgstr "" -#: ../../../docs/updating-users-passwords.md:27 +#: ../../../docs/updating-users-passwords.md:15 msgid "**You can then log in with that user** via Element Web that this playbook has created for you at a URL like this: `https://element.example.com/`." msgstr "" -#: ../../../docs/updating-users-passwords.md:29 +#: ../../../docs/updating-users-passwords.md:17 msgid "Option 2 (if you are using an external Postgres server):" msgstr "" -#: ../../../docs/updating-users-passwords.md:31 +#: ../../../docs/updating-users-passwords.md:19 msgid "You can manually generate the password hash by using the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#finalize-the-installation):" msgstr "" -#: ../../../docs/updating-users-passwords.md:37 -msgid "and then connecting to the Postgres server and executing:" +#: ../../../docs/updating-users-passwords.md:25 +msgid "and then connecting to the postgres server and executing:" msgstr "" -#: ../../../docs/updating-users-passwords.md:43 +#: ../../../docs/updating-users-passwords.md:31 msgid "where `` is the hash returned by the docker command above." msgstr "" -#: ../../../docs/updating-users-passwords.md:45 +#: ../../../docs/updating-users-passwords.md:33 msgid "Option 3:" msgstr "" -#: ../../../docs/updating-users-passwords.md:47 +#: ../../../docs/updating-users-passwords.md:35 msgid "Use the Synapse User Admin API as described here: https://github.com/element-hq/synapse/blob/master/docs/admin_api/user_admin_api.rst#reset-password" msgstr "" -#: ../../../docs/updating-users-passwords.md:49 +#: ../../../docs/updating-users-passwords.md:37 msgid "This requires an [access token](obtaining-access-tokens.md) from a server admin account. *This method will also log the user out of all of their clients while the other options do not.*" msgstr "" -#: ../../../docs/updating-users-passwords.md:51 +#: ../../../docs/updating-users-passwords.md:39 msgid "If you didn't make your account a server admin when you created it, you can learn how to switch it now by reading about it in [Adding/Removing Administrator privileges to an existing user in Synapse](registering-users.md#addingremoving-administrator-privileges-to-an-existing-user-in-synapse)." msgstr "" -#: ../../../docs/updating-users-passwords.md:53 +#: ../../../docs/updating-users-passwords.md:41 msgid "Example:" msgstr "" -#: ../../../docs/updating-users-passwords.md:55 +#: ../../../docs/updating-users-passwords.md:43 msgid "To set @alice:example.com's password to `correct_horse_battery_staple` you could use this curl command:" msgstr "" -#: ../../../docs/updating-users-passwords.md:61 +#: ../../../docs/updating-users-passwords.md:49 msgid "Make sure to replace `ACCESS_TOKEN_HERE` with the access token of the server admin account." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/i18n/README.po b/i18n/locales/jp/LC_MESSAGES/i18n/README.po index a5314ca41..f93ab6c11 100644 --- a/i18n/locales/jp/LC_MESSAGES/i18n/README.po +++ b/i18n/locales/jp/LC_MESSAGES/i18n/README.po @@ -10,7 +10,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: 2024-12-20 15:27+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -18,7 +18,7 @@ msgstr "" "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" +"Generated-By: Babel 2.16.0\n" #: ../../README.md:8 msgid "Internationalization" @@ -57,7 +57,7 @@ msgid "[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we p msgstr "" #: ../../README.md:23 -msgid "[.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionally ignore translated results (`translations/` directories) for languages that are still in progress. We only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold." +msgid "[.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionaly ignore translated results (`translations/` directories) for languages taht are still in progress. We only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold." msgstr "" #: ../../README.md:24 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-slack.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-slack.pot index 2f74f095d..1079798b2 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-slack.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-slack.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -16,22 +16,242 @@ 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 "Setting up Appservice Slack bridging (optional, removed)" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:24 -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." +msgid "Create a Classic Slack App" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:26 -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." +msgid "First, you need to create a Classic Slack App [here](https://api.slack.com/apps?new_classic_app=1)." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:28 -msgid "Uninstalling the component manually" +msgid "Name the app \"matrixbot\" (or anything else you'll remember). Select the team/workspace this app will belong to. Click on bot users and add a new bot user. We will use this account to bridge the the rooms." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:30 -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:" +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//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) `" +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." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-discord.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-discord.pot index 5296d04af..1ed9203b6 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-discord.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-discord.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -28,146 +28,130 @@ 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 "The playbook can install and configure [mautrix-discord](https://github.com/mautrix/discord) for you." +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 "See the project's [documentation](https://docs.mau.fi/bridges/go/discord/index.html) to learn what it does and why it might be useful to you." +msgid "The playbook can install and configure [mautrix-discord](https://github.com/mautrix/discord) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:23 -msgid "Prerequisites" +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 -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)." +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:27 -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)." +msgid "There are 2 ways to login to discord using this bridge, either by [scanning a QR code](#method-1-login-using-qr-code-recommended) using the Discord mobile app **or** by using a [Discord token](#method-2-login-using-discord-token-not-recommended)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:29 -msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)" +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 "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 "Enable Appservice Double Puppet or Shared Secret Auth (optional)" msgstr "" #: ../../../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." +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 -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." +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 -msgid "Adjusting the playbook configuration" +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 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:41 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:45 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:47 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:47 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:49 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:50 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:52 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:52 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:54 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:54 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:56 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../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: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." +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 -msgid "Usage" +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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 -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)." +msgid "Usage" msgstr "" #: ../../../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)." +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 -msgid "After logging in, the bridge will create portal rooms for some recent direct messages." +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 -msgid "Bridge guilds" +msgid "After logging in, the bridge will create portal rooms for some recent direct messages." msgstr "" #: ../../../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." +msgid "Bridge guilds" msgstr "" #: ../../../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." +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 -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." +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 -msgid "Enable relay" +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:83 -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 "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 ` 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 "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 +#: ../../../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`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:93 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:87 msgid "Increase logging verbosity" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:95 +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:89 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 "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-slack.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-slack.pot index 0d404903b..9625ff9cb 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-slack.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-slack.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -25,105 +25,117 @@ msgid "Refer the common guide for configuring mautrix bridges: [Setting up msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:14 -msgid "The playbook can install and configure [mautrix-slack](https://github.com/mautrix/slack) for you." +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 "See the project's [documentation](https://docs.mau.fi/bridges/go/slack/index.html) to learn what it does and why it might be useful to you." +msgid "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 "See the [features and roadmap](https://github.com/mautrix/slack/blob/main/ROADMAP.md) for more information." +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 -msgid "Prerequisites" +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 -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)." +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 -msgid "Note that neither of these methods are officially supported by Slack." +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:26 -msgid "Enable Appservice Double Puppet (optional)" +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 "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." +msgid "Note that neither of these methods are officially supported by Slack. [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) uses a Slack bot account which is the only officially supported method for bridging a Slack channel." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:30 -msgid "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." +msgid "Enable Appservice Double Puppet (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:32 -msgid "Adjusting the playbook configuration" +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 +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 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:38 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:40 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:44 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:42 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:46 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:44 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:48 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:46 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:50 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:48 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:52 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:55 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:59 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:57 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:61 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:59 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:63 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:61 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:65 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:63 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:67 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:65 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:69 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:67 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:71 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:69 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:73 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:71 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:75 msgid "Increase logging verbosity" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:73 +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:77 msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-client-sable.pot b/i18n/translation-templates/docs/configuring-playbook-client-sable.pot deleted file mode 100644 index df2a02ea2..000000000 --- a/i18n/translation-templates/docs/configuring-playbook-client-sable.pot +++ /dev/null @@ -1,113 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2018-2026, Slavi Pantaleev, Aine Etke, MDAD community members -# This file is distributed under the same license as the matrix-docker-ansible-deploy package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: matrix-docker-ansible-deploy \n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../../../docs/configuring-playbook-client-sable.md:9 -msgid "Setting up Sable (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:11 -msgid "The playbook can install and configure the [Sable](https://github.com/7w1/sable) Matrix web client for you." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:13 -msgid "Sable is a web client focusing primarily on simple, elegant and secure interface. It can be installed alongside or instead of [Element Web](./configuring-playbook-client-element-web.md), [Cinny](./configuring-playbook-client-cinny.md) and others." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:15 -msgid "Adjusting DNS records" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:17 -msgid "By default, this playbook installs Sable on the `sable.` subdomain (`sable.example.com`) and requires you to create a CNAME record for `sable`, which targets `matrix.example.com`." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:19 -msgid "When setting, replace `example.com` with your own." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:21 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:23 -msgid "To enable Sable, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:29 -msgid "Adjusting the Sable URL (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:31 -msgid "By tweaking the `sable_hostname` variable, you can easily make the service available at a **different hostname** than the default one." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:33 -msgid "Example additional configuration for your `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:43 -msgid "After changing the domain, **you may need to adjust your DNS** records to point the Sable domain to the Matrix server." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:45 -msgid "**Note**: while there is a `sable_path_prefix` variable for changing the path where Sable is served, overriding it is [not possible](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Sable requires an application rebuild (with a tweaked build config) to be functional under a custom path. You'd need to serve Sable at a dedicated subdomain." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:47 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:49 -msgid "There are some additional things you may wish to configure about the component." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:51 -msgid "Take a look at:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:53 -msgid "`roles/galaxy/sable/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:54 -msgid "`roles/galaxy/sable/templates/config.json.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `sable_configuration_extension_json` variable" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:56 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:58 -msgid "After configuring the playbook and [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:65 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:67 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:69 -msgid "Troubleshooting" -msgstr "" - -#: ../../../docs/configuring-playbook-client-sable.md:71 -msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-client-sable`." -msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-continuwuity.pot b/i18n/translation-templates/docs/configuring-playbook-continuwuity.pot index 97fa037f8..0d95a2676 100644 --- a/i18n/translation-templates/docs/configuring-playbook-continuwuity.pot +++ b/i18n/translation-templates/docs/configuring-playbook-continuwuity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -93,69 +93,69 @@ msgid "Unlike other homeserver implementations (like Synapse and Dendrite), cont msgstr "" #: ../../../docs/configuring-playbook-continuwuity.md:61 -msgid "On first startup, Continuwuity creates a special one-time-use registration token and logs it to the server's console. To access this, you will need to SSH into the server and run the following command:" +msgid "If you followed the instructions above (see [Adjusting the playbook configuration](#adjusting-the-playbook-configuration)), you should have registration enabled and protected by a registration token." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:68 -msgid "Find the token, highlight it, and copy it (ctrl+shift+C). This token should allow you to create the first user account via any client (like [Element Web](./configuring-playbook-client-element-web.md)) which supports creating users." +#: ../../../docs/configuring-playbook-continuwuity.md:63 +msgid "This should allow you to create the first user account via any client (like [Element Web](./configuring-playbook-client-element-web.md)) which supports creating users." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:70 +#: ../../../docs/configuring-playbook-continuwuity.md:65 msgid "The **first user account that you create will be marked as an admin** and **will be automatically invited to an admin room**." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:73 +#: ../../../docs/configuring-playbook-continuwuity.md:68 msgid "Configuring bridges / appservices" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:75 +#: ../../../docs/configuring-playbook-continuwuity.md:70 msgid "For other homeserver implementations (like Synapse and Dendrite), the playbook automatically registers appservices (for bridges, bots, etc.) with the homeserver." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:77 +#: ../../../docs/configuring-playbook-continuwuity.md:72 msgid "For continuwuity, you will have to manually register appservices using the [`!admin appservices register` command](https://continuwuity.org/appservices.html#set-up-the-appservice---general-instructions) sent to the server bot account." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:79 +#: ../../../docs/configuring-playbook-continuwuity.md:74 msgid "The server's bot account has a Matrix ID of `@conduit:example.com` (not `@continuwuity:example.com`!) due to continuwuity's historical legacy. Your first user account would already have been invited to an admin room with this bot." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:82 +#: ../../../docs/configuring-playbook-continuwuity.md:77 msgid "Find the appservice file you'd like to register. This can be any `registration.yaml` file found in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:84 +#: ../../../docs/configuring-playbook-continuwuity.md:79 msgid "Then, send its content to the existing admin room:" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:108 +#: ../../../docs/configuring-playbook-continuwuity.md:103 msgid "Migrating from conduwuit" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:110 +#: ../../../docs/configuring-playbook-continuwuity.md:105 msgid "Since Continuwuity is a drop-in replacement for [conduwuit](configuring-playbook-conduwuit.md), migration is possible." msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:112 +#: ../../../docs/configuring-playbook-continuwuity.md:107 msgid "Make sure that Continuwuity is properly set up on your `vars.yml` as described above" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:114 +#: ../../../docs/configuring-playbook-continuwuity.md:109 msgid "Make sure that Conduwuit references are removed from your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:116 +#: ../../../docs/configuring-playbook-continuwuity.md:111 msgid "Run the installation in a way that installs new services and uninstalls old ones (e.g. `just setup-all`)" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:118 +#: ../../../docs/configuring-playbook-continuwuity.md:113 msgid "Run the playbook with the `continuwuity-migrate-from-conduwuit` tag (e.g. `just run-tags continuwuity-migrate-from-conduwuit`). This migrates data from `/matrix/conduwuit` to `/matrix/continuwuity`" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:120 +#: ../../../docs/configuring-playbook-continuwuity.md:115 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-continuwuity.md:122 +#: ../../../docs/configuring-playbook-continuwuity.md:117 msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-continuwuity`." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-email.pot b/i18n/translation-templates/docs/configuring-playbook-email.pot index babaf630b..1f56396e5 100644 --- a/i18n/translation-templates/docs/configuring-playbook-email.pot +++ b/i18n/translation-templates/docs/configuring-playbook-email.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -41,109 +41,89 @@ msgid "📁 `roles/galaxy/exim_relay/docs/configuring-exim-relay.md` locally, if msgstr "" #: ../../../docs/configuring-playbook-email.md:20 -msgid "Why use exim-relay?" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:22 -msgid "**Benefits of using exim-relay** instead of configuring SMTP directly in each service:" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:24 -msgid "**Final delivery capability**: Can deliver emails directly if you don't have an SMTP server" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:26 -msgid "**Centralized configuration**: Configure your upstream SMTP server once in exim-relay, then point all services ([Synapse](configuring-playbook-synapse.md), [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), etc.) there—no need to configure SMTP in each component" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:28 -msgid "**Local spooling**: Stores messages locally and retries delivery if your upstream SMTP server is temporarily unavailable" -msgstr "" - -#: ../../../docs/configuring-playbook-email.md:30 msgid "Firewall settings" msgstr "" -#: ../../../docs/configuring-playbook-email.md:32 +#: ../../../docs/configuring-playbook-email.md:22 msgid "No matter whether you send email directly (the default) or you relay email through another host, you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration)." msgstr "" -#: ../../../docs/configuring-playbook-email.md:34 +#: ../../../docs/configuring-playbook-email.md:24 msgid "Docker automatically opens these ports in the server's firewall, so you likely don't need to do anything. If you use another firewall in front of the server, you may need to adjust it." msgstr "" -#: ../../../docs/configuring-playbook-email.md:36 +#: ../../../docs/configuring-playbook-email.md:26 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-email.md:38 +#: ../../../docs/configuring-playbook-email.md:28 msgid "Enable DKIM authentication to improve deliverability (optional)" msgstr "" -#: ../../../docs/configuring-playbook-email.md:40 +#: ../../../docs/configuring-playbook-email.md:30 msgid "By default, exim-relay attempts to deliver emails directly. This may or may not work, depending on your domain configuration." msgstr "" -#: ../../../docs/configuring-playbook-email.md:42 +#: ../../../docs/configuring-playbook-email.md:32 msgid "To improve email deliverability, you can configure authentication methods such as DKIM (DomainKeys Identified Mail), SPF, and DMARC for your domain. Without setting any of these authentication methods, your outgoing email is most likely to be quarantined as spam at recipient's mail servers." msgstr "" -#: ../../../docs/configuring-playbook-email.md:44 +#: ../../../docs/configuring-playbook-email.md:34 msgid "For details about configuring DKIM, refer [this section](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md#enable-dkim-support-optional) on the role's documentation." msgstr "" -#: ../../../docs/configuring-playbook-email.md:46 +#: ../../../docs/configuring-playbook-email.md:36 msgid "💡 If you cannot enable DKIM, SPF, or DMARC on your domain for some reason, we recommend relaying email through another SMTP server." msgstr "" -#: ../../../docs/configuring-playbook-email.md:48 +#: ../../../docs/configuring-playbook-email.md:38 msgid "Relaying email through another SMTP server (optional)" msgstr "" -#: ../../../docs/configuring-playbook-email.md:50 +#: ../../../docs/configuring-playbook-email.md:40 msgid "**On some cloud providers such as Google Cloud, [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible.** In this case, you will need to relay email through another SMTP server." msgstr "" -#: ../../../docs/configuring-playbook-email.md:52 +#: ../../../docs/configuring-playbook-email.md:42 msgid "For details about configuration, refer [this section](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md#relaying-email-through-another-smtp-server) on the role's document." msgstr "" -#: ../../../docs/configuring-playbook-email.md:54 +#: ../../../docs/configuring-playbook-email.md:44 msgid "Disable mail service (optional)" msgstr "" -#: ../../../docs/configuring-playbook-email.md:56 +#: ../../../docs/configuring-playbook-email.md:46 msgid "For a low-power server you might probably want to disable exim-relay. To do so, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-email.md:62 +#: ../../../docs/configuring-playbook-email.md:52 msgid "Note that disabling exim-relay will stop email-notifications and other similar functions from working." msgstr "" -#: ../../../docs/configuring-playbook-email.md:64 +#: ../../../docs/configuring-playbook-email.md:54 msgid "See [this entry on the FAQ](faq.md#how-do-i-optimize-this-setup-for-a-low-power-server) for other possible optimizations for a low-power server." msgstr "" -#: ../../../docs/configuring-playbook-email.md:66 +#: ../../../docs/configuring-playbook-email.md:56 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-email.md:68 +#: ../../../docs/configuring-playbook-email.md:58 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-email.md:75 +#: ../../../docs/configuring-playbook-email.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-email.md:77 +#: ../../../docs/configuring-playbook-email.md:67 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-email.md:79 +#: ../../../docs/configuring-playbook-email.md:69 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-email.md:81 +#: ../../../docs/configuring-playbook-email.md:71 msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md#troubleshooting) on the role's documentation for details." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-jitsi.pot b/i18n/translation-templates/docs/configuring-playbook-jitsi.pot index 964118cd4..52954c44b 100644 --- a/i18n/translation-templates/docs/configuring-playbook-jitsi.pot +++ b/i18n/translation-templates/docs/configuring-playbook-jitsi.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -25,153 +25,149 @@ msgid "The playbook can install and configure the [Jitsi](https://jitsi.org/) vi msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:21 -msgid "Because Jitsi still requires a TURN server, enabling Jitsi automatically enables coturn (`coturn_enabled: true`) unless you explicitly disable it." -msgstr "" - -#: ../../../docs/configuring-playbook-jitsi.md:24 msgid "Jitsi is an open source video-conferencing platform. It can not only be integrated with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS) as a widget, but also be used as standalone web app." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:26 +#: ../../../docs/configuring-playbook-jitsi.md:23 msgid "💡 If you're into experimental technology, you may also be interested in trying out [Element Call](configuring-playbook-element-call.md) - a native Matrix video conferencing application." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:28 +#: ../../../docs/configuring-playbook-jitsi.md:25 msgid "The [Ansible role for Jitsi](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring Jitsi, you can check them via:" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:29 +#: ../../../docs/configuring-playbook-jitsi.md:26 msgid "🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md) online" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:30 +#: ../../../docs/configuring-playbook-jitsi.md:27 msgid "📁 `roles/galaxy/jitsi/docs/configuring-jitsi.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:32 +#: ../../../docs/configuring-playbook-jitsi.md:29 msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:34 +#: ../../../docs/configuring-playbook-jitsi.md:31 msgid "Before proceeding, make sure to check server's requirements recommended by [the official deployment guide](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-requirements)." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:36 +#: ../../../docs/configuring-playbook-jitsi.md:33 msgid "You may need to open some ports to your server, if you use another firewall in front of the server. Refer [the role's documentation](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#prerequisites) to check which ones to be configured." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:38 +#: ../../../docs/configuring-playbook-jitsi.md:35 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:40 +#: ../../../docs/configuring-playbook-jitsi.md:37 msgid "By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to create a CNAME record for `jitsi`, which targets `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:42 +#: ../../../docs/configuring-playbook-jitsi.md:39 msgid "When setting, replace `example.com` with your own." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:44 +#: ../../../docs/configuring-playbook-jitsi.md:41 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:46 +#: ../../../docs/configuring-playbook-jitsi.md:43 msgid "To enable Jitsi, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:64 +#: ../../../docs/configuring-playbook-jitsi.md:61 msgid "As the most of the necessary settings for the role have been taken care of by the playbook, you can enable Jitsi on your Matrix server with this minimum configuration." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:66 +#: ../../../docs/configuring-playbook-jitsi.md:63 msgid "However, **since Jitsi's performance heavily depends on server resource (bandwidth, RAM, and CPU), it is recommended to review settings and optimize them as necessary before deployment.** You can check [here](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#example-configurations) for an example set of configurations to set up a Jitsi instance, focusing on performance. If you will host a large conference, you probably might also want to consider to provision additional JVBs ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)). See [here](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#set-up-additional-jvbs-for-more-video-conferences-optional) for details about setting them up with the playbook." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:68 +#: ../../../docs/configuring-playbook-jitsi.md:65 msgid "See the role's documentation for details about configuring Jitsi per your preference (such as setting [a custom hostname](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#set-the-hostname) and [the environment variable for running Jitsi in a LAN](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#configure-jvb_advertise_ips-for-running-behind-nat-or-on-a-lan-environment-optional))." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:70 +#: ../../../docs/configuring-playbook-jitsi.md:67 msgid "Enable authentication and guests mode (optional)" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:72 +#: ../../../docs/configuring-playbook-jitsi.md:69 msgid "By default the Jitsi Meet instance **does not require for anyone to log in, and is open to use without an account**." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:74 +#: ../../../docs/configuring-playbook-jitsi.md:71 msgid "If you would like to control who is allowed to start meetings on your instance, you'd need to enable Jitsi's authentication and optionally guests mode." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:76 +#: ../../../docs/configuring-playbook-jitsi.md:73 msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#configure-jitsi-authentication-and-guests-mode-optional) on the role's documentation for details about how to configure the authentication and guests mode. The recommended authentication method is `internal` as it also works in federated rooms. If you want to enable authentication with Matrix OpenID making use of [Matrix User Verification Service (UVS)](configuring-playbook-user-verification-service.md), see [here](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix) for details about how to set it up." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:78 +#: ../../../docs/configuring-playbook-jitsi.md:75 msgid "Enable Gravatar (optional)" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:80 +#: ../../../docs/configuring-playbook-jitsi.md:77 msgid "In the default Jisti Meet configuration, `gravatar.com` is enabled as an avatar service." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:82 +#: ../../../docs/configuring-playbook-jitsi.md:79 msgid "Since the Element clients send the URL of configured Matrix avatars to the Jitsi instance, our configuration has disabled the Gravatar service." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:84 +#: ../../../docs/configuring-playbook-jitsi.md:81 msgid "To enable the Gravatar service nevertheless, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:90 +#: ../../../docs/configuring-playbook-jitsi.md:87 msgid "[!WARNING] This will result in third party request leaking data to the Gravatar Service (`gravatar.com`, unless configured otherwise). Besides metadata, the Matrix user_id and possibly the room ID (via `referrer` header) will be also sent to the third party." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:93 +#: ../../../docs/configuring-playbook-jitsi.md:90 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:95 +#: ../../../docs/configuring-playbook-jitsi.md:92 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:102 +#: ../../../docs/configuring-playbook-jitsi.md:99 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:104 +#: ../../../docs/configuring-playbook-jitsi.md:101 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:106 +#: ../../../docs/configuring-playbook-jitsi.md:103 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:108 +#: ../../../docs/configuring-playbook-jitsi.md:105 msgid "You can use the self-hosted Jitsi server in multiple ways:" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:110 +#: ../../../docs/configuring-playbook-jitsi.md:107 msgid "**by adding a widget to a room via Element Web** (the one configured by the playbook at `https://element.example.com`). Just start a voice or a video call in a room containing more than 2 members and that would create a Jitsi widget which utilizes your self-hosted Jitsi server." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:112 +#: ../../../docs/configuring-playbook-jitsi.md:109 msgid "**directly (without any Matrix integration)**. Just go to `https://jitsi.example.com`, and you can start a videoconference." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:114 +#: ../../../docs/configuring-playbook-jitsi.md:111 msgid "Note that you'll need to log in to your Jitsi's account to start a conference if you have configured authentication with `internal` auth." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:116 +#: ../../../docs/configuring-playbook-jitsi.md:113 msgid "Check [the official user guide](https://jitsi.github.io/handbook/docs/category/user-guide) for details about how to use Jitsi." msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:118 +#: ../../../docs/configuring-playbook-jitsi.md:115 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-jitsi.md:120 +#: ../../../docs/configuring-playbook-jitsi.md:117 msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#troubleshooting) on the role's documentation for details." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-livekit-server.pot b/i18n/translation-templates/docs/configuring-playbook-livekit-server.pot index ffe0810df..000f0b883 100644 --- a/i18n/translation-templates/docs/configuring-playbook-livekit-server.pot +++ b/i18n/translation-templates/docs/configuring-playbook-livekit-server.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -41,7 +41,7 @@ msgid "🌐 [the role's documentation at the MASH project](https://github.com/mo msgstr "" #: ../../../docs/configuring-playbook-livekit-server.md:18 -msgid "📁 `roles/galaxy/livekit_server/docs/configuring-livekit-server.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" +msgid "📁 `roles/galaxy/livekit-server/docs/configuring-livekit-server.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)" msgstr "" #: ../../../docs/configuring-playbook-livekit-server.md:20 @@ -69,69 +69,17 @@ msgid "`5350/tcp`: TURN/TCP. Also see the [Limitations](#limitations) section be msgstr "" #: ../../../docs/configuring-playbook-livekit-server.md:32 -msgid "`30000-30020/udp`: TURN relay range used by LiveKit's embedded TURN server." +msgid "💡 The suggestions above are inspired by the upstream [Ports and Firewall](https://docs.livekit.io/home/self-hosting/ports-firewall/) documentation based on how LiveKit is configured in the playbook. If you've using custom configuration for the LiveKit Server role, you may need to adjust the firewall rules accordingly." msgstr "" #: ../../../docs/configuring-playbook-livekit-server.md:34 -msgid "💡 The suggestions above are inspired by the upstream [Ports and Firewall](https://docs.livekit.io/home/self-hosting/ports-firewall/) documentation based on how LiveKit is configured in the playbook. If you're using custom configuration for the LiveKit Server role, you may need to adjust firewall rules accordingly." +msgid "Limitations" msgstr "" #: ../../../docs/configuring-playbook-livekit-server.md:36 -msgid "TURN TLS handling" +msgid "For some reason, LiveKit Server's TURN ports (`3479/udp` and `5350/tcp`) are not reachable over IPv6 regardless of whether you've [enabled IPv6](./configuring-ipv6.md) for your server." msgstr "" #: ../../../docs/configuring-playbook-livekit-server.md:38 -msgid "When `matrix_playbook_reverse_proxy_type` is `playbook-managed-traefik` (which is the default for this playbook), TURN over TCP is terminated by Traefik and forwarded to LiveKit with `turn.external_tls = true`. In this playbook default, this mode is enabled automatically when SSL is enabled and TURN is enabled." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:40 -msgid "The playbook installs a dedicated Traefik TCP entrypoint for TURN (`matrix-livekit-turn`) by default and binds it to `tcp/5350`." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:41 -msgid "`livekit_server_config_turn_external_tls` is automatically enabled for this setup." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:42 -msgid "Because Traefik handles TLS, LiveKit no longer needs certificate-file paths for TURN in this mode." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:44 -msgid "To opt out and keep TURN TLS termination in LiveKit itself, set:" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:50 -msgid "In this playbook, certificate paths are managed automatically via `group_vars/matrix_servers` when certificate dumping is enabled." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:52 -msgid "If your setup uses `other-traefik-container` or [another reverse-proxy](./configuring-playbook-own-webserver.md), behavior is unchanged by default and still relies on certificates being available inside the container as before." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:54 -msgid "Deployments using `other-traefik-container` can opt into the same Traefik-terminated mode there, by setting:" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:62 -msgid "and configuring their own Traefik TCP entrypoint dedicated to LiveKit TURN traffic." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:64 -msgid "Limitations" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:66 -msgid "LiveKit Server's TURN listener behavior depends on where TLS is terminated:" -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:68 -msgid "Direct LiveKit TURN listeners (`livekit_server_config_turn_external_tls: false`) still use IPv4-only sockets for `3479/udp` and `5350/tcp`, so IPv6 connectivity to these endpoints is not possible." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:69 -msgid "With [TURN TLS handling](#turn-tls-handling) (`livekit_server_config_turn_external_tls: true`), the playbook's dedicated `matrix-livekit-turn` TCP entrypoint can still listen on both IPv4 and IPv6. Traefik then forwards TURN/TCP to LiveKit." -msgstr "" - -#: ../../../docs/configuring-playbook-livekit-server.md:71 -msgid "It appears that LiveKit Server intentionally only listens on `udp4` and `tcp4` in direct mode, as seen [here](https://github.com/livekit/livekit/blob/154b4d26b769c68a03c096124094b97bf61a996f/pkg/service/turn.go#L128) and [here](https://github.com/livekit/livekit/blob/154b4d26b769c68a03c096124094b97bf61a996f/pkg/service/turn.go#L92)." +msgid "It seems like LiveKit Server intentionally only listens on `udp4` and `tcp4` as seen [here](https://github.com/livekit/livekit/blob/154b4d26b769c68a03c096124094b97bf61a996f/pkg/service/turn.go#L128) and [here](https://github.com/livekit/livekit/blob/154b4d26b769c68a03c096124094b97bf61a996f/pkg/service/turn.go#L92)." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-matrix-rtc.pot b/i18n/translation-templates/docs/configuring-playbook-matrix-rtc.pot index d0fa0ba77..20c5f27e6 100644 --- a/i18n/translation-templates/docs/configuring-playbook-matrix-rtc.pot +++ b/i18n/translation-templates/docs/configuring-playbook-matrix-rtc.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -45,11 +45,11 @@ msgid "Various experimental features for the Synapse homeserver which Element Ca msgstr "" #: ../../../docs/configuring-playbook-matrix-rtc.md:20 -msgid "A [LiveKit Server](configuring-playbook-livekit-server.md) (automatically installed when [Element Call or the Matrix RTC stack is enabled](configuring-playbook-element-call.md#decide-between-element-call-vs-just-the-matrix-rtc-stack))" +msgid "A [LiveKit Server](configuring-playbook-livekit-server.md) (automatically installed when [Element Call or the Matrix RTC stack is enabled](#decide-between-element-call-vs-just-the-matrix-rtc-stack))" msgstr "" #: ../../../docs/configuring-playbook-matrix-rtc.md:21 -msgid "The [LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md) (automatically installed when [Element Call or the Matrix RTC stack is enabled](configuring-playbook-element-call.md#decide-between-element-call-vs-just-the-matrix-rtc-stack))" +msgid "The [LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md) (automatically installed when [Element Call or the Matrix RTC stack is enabled](#decide-between-element-call-vs-just-the-matrix-rtc-stack))" msgstr "" #: ../../../docs/configuring-playbook-matrix-rtc.md:22 diff --git a/i18n/translation-templates/docs/configuring-playbook-prometheus-grafana.pot b/i18n/translation-templates/docs/configuring-playbook-prometheus-grafana.pot index d85a1a594..f2ab67ceb 100644 --- a/i18n/translation-templates/docs/configuring-playbook-prometheus-grafana.pot +++ b/i18n/translation-templates/docs/configuring-playbook-prometheus-grafana.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -143,7 +143,7 @@ msgid "[Prometheus role](https://github.com/mother-of-all-self-hosting/ansible-r msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:109 -msgid "`roles/galaxy/prometheus_nginxlog_exporter/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +msgid "`roles/custom/matrix-prometheus-nginxlog-exporter/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:111 @@ -291,7 +291,7 @@ msgid "Set this to `true` to enable the node (general system stats) exporter (lo msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:0 -msgid "`prometheus_node_exporter_container_labels_metrics_enabled`" +msgid "`prometheus_node_exporter_container_labels_traefik_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:0 @@ -307,7 +307,7 @@ msgid "Set this to `true` to enable the [Postgres exporter](#enable-metrics-and- msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:0 -msgid "`prometheus_postgres_exporter_container_labels_metrics_enabled`" +msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:0 @@ -315,19 +315,19 @@ msgid "Set this to `true` to expose the [Postgres exporter](#enable-metrics-and- msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:0 -msgid "`prometheus_nginxlog_exporter_enabled`" +msgid "`matrix_prometheus_nginxlog_exporter_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:0 -msgid "Set this to `true` to enable the [prometheus-nginxlog-exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) (locally, on the container network)." +msgid "Set this to `true` to enable the [nginx Log exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) (locally, on the container network)." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:0 -msgid "`prometheus_nginxlog_exporter_container_labels_metrics_enabled`" +msgid "`matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:0 -msgid "Set this to `true` to expose the [prometheus-nginxlog-exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) metrics on `https://matrix.example.com/metrics/nginxlog`." +msgid "Set this to `true` to expose the [nginx Log exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) metrics on `https://matrix.example.com/metrics/nginxlog`." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:187 diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-admin.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-admin.pot new file mode 100644 index 000000000..6c368e2f4 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-synapse-admin.pot @@ -0,0 +1,145 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2026, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2026-02-13 10:32+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/configuring-playbook-synapse-admin.md:13 +msgid "Setting up Synapse Admin (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:15 +msgid "The playbook can install and configure [etkecc/synapse-admin](https://github.com/etkecc/synapse-admin) (a [feature-rich](https://github.com/etkecc/synapse-admin#fork-differences) fork of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin), community room: [#synapse-admin:etke.cc](https://matrix.to/#/#synapse-admin:etke.cc)) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:17 +msgid "synapse-admin is a web UI tool you can use to **administrate users, rooms, media, etc. on your Matrix server**. It's designed to work with the Synapse homeserver implementation and WON'T work with Dendrite because [Dendrite Admin API](https://element-hq.github.io/dendrite/administration/adminapi) differs from [Synapse Admin API](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:19 +msgid "💡 **Note**: the latest version of synapse-admin is hosted by [etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). If you only need this service occasionally and trust giving your admin credentials to a 3rd party Single Page Application, you can consider using it from there and avoiding the (small) overhead of self-hosting." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:21 +msgid "💡 **Note**: The playbook also supports an alternative management UI in the shape of [Element Admin](./configuring-playbook-element-admin.md). However, it's currently less feature-rich than Synapse Admin and has a dependency on [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:23 +msgid "Adjusting DNS records (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:25 +msgid "By default, this playbook installs Synapse Admin on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:27 +msgid "If you wish to adjust it, see the section [below](#adjusting-the-synapse-admin-url-optional) for details about DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:29 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:31 +msgid "To enable Synapse Admin, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:37 +msgid "**Note**: Synapse Admin requires Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to function. Access to them is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, for additional security, we normally leave them unexposed, following [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). Because Synapse Admin needs these APIs to function, when installing Synapse Admin, the playbook **automatically** exposes the Synapse Admin API publicly for you. Depending on the homeserver implementation you're using (Synapse, Dendrite), this is equivalent to:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:39 +msgid "for [Synapse](./configuring-playbook-synapse.md) (our default homeserver implementation): `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:40 +msgid "for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:42 +msgid "By default, synapse-admin installation will be [restricted to only work with one homeserver](https://github.com/etkecc/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) — the one managed by the playbook. To adjust these restrictions, tweak the `matrix_synapse_admin_config_restrictBaseUrl` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:44 +msgid "Adjusting the Synapse Admin URL (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:46 +msgid "By tweaking the `matrix_synapse_admin_hostname` and `matrix_synapse_admin_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:48 +msgid "Example additional configuration for your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:56 +msgid "If you've changed the default hostname, you may need to create a CNAME record for the Synapse Admin domain (`admin.example.com`), which targets `matrix.example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:58 +msgid "When setting, replace `example.com` with your own." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:60 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:62 +msgid "There are some additional things you may wish to configure about the component." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:64 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:66 +msgid "`roles/custom/matrix-synapse-admin/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_synapse_admin_configuration_extension_json` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:68 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:70 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.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-synapse-admin.md:79 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:81 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:83 +msgid "After installation, Synapse Admin will be accessible at: `https://matrix.example.com/synapse-admin/`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:85 +msgid "To use Synapse Admin, you need to have [registered at least one administrator account](registering-users.md) on your server." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:87 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:89 +msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-synapse-admin`." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-auto-accept-invite.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-auto-accept-invite.pot index 01fd11adc..b36ec32af 100644 --- a/i18n/translation-templates/docs/configuring-playbook-synapse-auto-accept-invite.pot +++ b/i18n/translation-templates/docs/configuring-playbook-synapse-auto-accept-invite.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -16,18 +16,54 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:18 -msgid "Setting up Synapse Auto Invite Accept (optional, removed)" +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:9 +msgid "Setting up Synapse Auto Invite Accept (optional)" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:20 -msgid "🪦 The playbook used to be able to install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite), but no longer includes this component, as the same functionality [has been integrated](https://github.com/element-hq/synapse/pull/17147) to Synapse since [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0)." +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:11 +msgid "The playbook can install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) for you." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:22 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:13 +msgid "In short, it automatically accepts room invites. You can specify that only 1:1 room invites are auto-accepted. Defaults to false if not specified." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:15 +msgid "See the project's [documentation](https://github.com/matrix-org/synapse-auto-accept-invite/blob/main/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:17 +msgid "**Note**: Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0), the same feature [has been merged](https://github.com/element-hq/synapse/pull/17147) into Synapse (see the [Native alternative](#native-alternative) section below). You'd better use the native feature, instead of the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) 3rd party module." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:19 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:21 +msgid "If you decide that you'd like to let this playbook install the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite module for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:29 +msgid "Synapse worker deployments" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:31 +msgid "In a [workerized Synapse deployment](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/c9a842147e09647c355799ca024d65a5de66b099/docs/configuring-playbook-synapse.md#load-balancing-with-workers) it is possible to run this module on a worker to reduce the load on the main process (Default is `null`). For example, add this to your configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:37 +msgid "There might be an [issue with federation](https://github.com/matrix-org/synapse-auto-accept-invite/issues/18)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:39 msgid "Native alternative" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:24 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:41 +msgid "Since Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0), the functionality provided by the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) 3rd party module [has been made](https://github.com/element-hq/synapse/pull/17147) part of Synapse." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:43 msgid "Here's example configuration for using the **native** Synapse feature:" msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-s3-storage-provider.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-s3-storage-provider.pot index d3d96da98..58ceb305b 100644 --- a/i18n/translation-templates/docs/configuring-playbook-synapse-s3-storage-provider.pot +++ b/i18n/translation-templates/docs/configuring-playbook-synapse-s3-storage-provider.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -293,13 +293,9 @@ msgid "… triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` t msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:180 -msgid "The same `migrate` script also prunes empty directories in the local media repository (`remote_content` and `remote_thumbnail`) after upload/delete operations." -msgstr "" - -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:182 msgid "So… you don't need to perform any maintenance yourself." msgstr "" -#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:184 +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:182 msgid "The schedule is defined in the format of systemd timer calendar. To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs):" msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-traefik.pot b/i18n/translation-templates/docs/configuring-playbook-traefik.pot index 7a7b73547..b0679f9ba 100644 --- a/i18n/translation-templates/docs/configuring-playbook-traefik.pot +++ b/i18n/translation-templates/docs/configuring-playbook-traefik.pot @@ -8,7 +8,7 @@ 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" +"POT-Creation-Date: 2026-02-13 10:32+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -48,147 +48,139 @@ msgstr "" msgid "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:" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:37 -msgid "Generate the `traefik_dashboard_basicauth_htpasswd` value on your local machine with a command like `htpasswd -nb YOUR_USERNAME_HERE YOUR_PASSWORD_HERE`." -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:39 -msgid "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." -msgstr "" - -#: ../../../docs/configuring-playbook-traefik.md:41 +#: ../../../docs/configuring-playbook-traefik.md:38 msgid "[!WARNING] Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:44 +#: ../../../docs/configuring-playbook-traefik.md:41 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:46 +#: ../../../docs/configuring-playbook-traefik.md:43 msgid "There are some additional things you may wish to configure about the component." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:48 +#: ../../../docs/configuring-playbook-traefik.md:45 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:50 +#: ../../../docs/configuring-playbook-traefik.md:47 msgid "[Traefik role](https://github.com/mother-of-all-self-hosting/ansible-role-traefik)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-traefik/blob/main/defaults/main.yml) for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `traefik_configuration_extension_yaml` variable" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:52 +#: ../../../docs/configuring-playbook-traefik.md:49 msgid "For example, to enable and secure the Dashboard, you can add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:54 +#: ../../../docs/configuring-playbook-traefik.md:51 msgid "**Note**: this is a contrived example as you can enable and secure the Dashboard using the dedicated variables. See above for details." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:72 +#: ../../../docs/configuring-playbook-traefik.md:69 msgid "Reverse-proxying another service behind Traefik" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:74 +#: ../../../docs/configuring-playbook-traefik.md:71 msgid "The preferred way to reverse-proxy additional services behind Traefik would be to start the service as another container, configure the container with the corresponding Traefik [container labels](https://docs.docker.com/config/labels-custom-metadata/) (see [Traefik & Docker](https://doc.traefik.io/traefik/routing/providers/docker/)), and connect the service to the `traefik` network. Some services are also already available via the compatible [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook), but take a look at the minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md)." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:76 +#: ../../../docs/configuring-playbook-traefik.md:73 msgid "However, if your service does not run on a container or runs on another machine, the following configuration might be what you are looking for." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:78 +#: ../../../docs/configuring-playbook-traefik.md:75 msgid "Reverse-proxying a remote HTTP/HTTPS service behind Traefik" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:80 +#: ../../../docs/configuring-playbook-traefik.md:77 msgid "If you want to host another webserver would be reachable via `my-fancy-website.example.net` from the internet and via `https://:` from inside your network, you can make the playbook's integrated Traefik instance reverse-proxy the traffic to the correct host." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:82 +#: ../../../docs/configuring-playbook-traefik.md:79 msgid "Prerequisites: DNS and routing for the domain `my-fancy-website.example.net` need to be set up correctly. In this case, you'd be pointing the domain name to your Matrix server — `my-fancy-website.example.net` would be a CNAME going to `matrix.example.com`." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:84 +#: ../../../docs/configuring-playbook-traefik.md:81 msgid "First, we have to adjust the static configuration of Traefik, so that we can add additional configuration files:" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:98 +#: ../../../docs/configuring-playbook-traefik.md:95 msgid "If you are using a self-signed certificate on your webserver, you can tell Traefik to trust your own backend servers by adding more configuration to the static configuration file. If you do so, bear in mind the security implications of disabling the certificate validity checks towards your back end." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:112 +#: ../../../docs/configuring-playbook-traefik.md:109 msgid "Next, you have to add a new dynamic configuration file for Traefik that contains the actual information of the server using the `aux_file_definitions` variable. In this example, we will terminate SSL at the Traefik instance and connect to the other server via HTTPS. Traefik will now take care of managing the certificates." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:131 -#: ../../../docs/configuring-playbook-traefik.md:154 +#: ../../../docs/configuring-playbook-traefik.md:128 +#: ../../../docs/configuring-playbook-traefik.md:151 msgid "Changing the `url` to one with an `http://` prefix would allow to connect to the server via HTTP." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:133 +#: ../../../docs/configuring-playbook-traefik.md:130 msgid "Reverse-proxying another service behind Traefik without terminating SSL" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:135 +#: ../../../docs/configuring-playbook-traefik.md:132 msgid "If you do not want to terminate SSL at the Traefik instance (for example, because you're already terminating SSL at other webserver), you need to adjust the static configuration in the same way as in the previous chapter in order to be able to add our own dynamic configuration files. Afterwards, you can add the following configuration to your `vars.yml` configuration file:" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:156 +#: ../../../docs/configuring-playbook-traefik.md:153 msgid "With these changes, all TCP traffic will be reverse-proxied to the target system." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:158 +#: ../../../docs/configuring-playbook-traefik.md:155 msgid "[!WARNING] This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:161 +#: ../../../docs/configuring-playbook-traefik.md:158 msgid "Traefik behind a `proxy_protocol` reverse-proxy" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:163 +#: ../../../docs/configuring-playbook-traefik.md:160 msgid "If you run a reverse-proxy which speaks `proxy_protocol`, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:182 +#: ../../../docs/configuring-playbook-traefik.md:179 msgid "Other configurations" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:184 +#: ../../../docs/configuring-playbook-traefik.md:181 msgid "Adjusting SSL certificate retrieval" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:186 +#: ../../../docs/configuring-playbook-traefik.md:183 msgid "See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:188 +#: ../../../docs/configuring-playbook-traefik.md:185 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:190 +#: ../../../docs/configuring-playbook-traefik.md:187 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:197 +#: ../../../docs/configuring-playbook-traefik.md:194 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:199 +#: ../../../docs/configuring-playbook-traefik.md:196 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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-traefik.md:201 +#: ../../../docs/configuring-playbook-traefik.md:198 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:203 +#: ../../../docs/configuring-playbook-traefik.md:200 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-traefik`." msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:205 +#: ../../../docs/configuring-playbook-traefik.md:202 msgid "Increase logging verbosity" msgstr "" -#: ../../../docs/configuring-playbook-traefik.md:207 +#: ../../../docs/configuring-playbook-traefik.md:204 msgid "The default logging level for this component is `INFO`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-turn.pot b/i18n/translation-templates/docs/configuring-playbook-turn.pot index 69e150c8b..98744ac3c 100644 --- a/i18n/translation-templates/docs/configuring-playbook-turn.pot +++ b/i18n/translation-templates/docs/configuring-playbook-turn.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -21,213 +21,173 @@ msgid "Configuring a TURN server (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-turn.md:16 -msgid "By default, the [coturn](https://github.com/coturn/coturn) TURN server component is enabled automatically only when [Jitsi](configuring-playbook-jitsi.md) is enabled. If you're not using Jitsi, coturn is not enabled by default." +msgid "By default, this playbook installs and configures the [coturn](https://github.com/coturn/coturn) as a TURN server, through which clients can make audio/video calls even from [NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed networks. It also configures the Synapse chat server by default, so that it points to the coturn TURN server installed by the playbook. If that's okay, you can skip this document." msgstr "" #: ../../../docs/configuring-playbook-turn.md:18 -msgid "If you explicitly need coturn while not using Jitsi, enable it with:" +msgid "If you'd like to stop the playbook installing the server, see the section [below](#disabling-coturn) to check the configuration for disabling it." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:24 -msgid "and configure its IP-related settings in the section below." +#: ../../../docs/configuring-playbook-turn.md:20 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:26 -msgid "If you'd like coturn to stay disabled even when Jitsi is enabled, or if you prefer to use an external TURN provider, see [disabling coturn](#disabling-coturn) section below." +#: ../../../docs/configuring-playbook-turn.md:22 +msgid "Define public IP manually (optional)" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:28 -msgid "When Coturn is not enabled, homeservers (like Synapse) would not point to TURN servers and *legacy* audio/video call functionality may fail. If you're using [Matrix RTC](configuring-playbook-matrix-rtc.md) (for [Element Call](configuring-playbook-element-call.md)), you likely don't have a need to enable coturn." +#: ../../../docs/configuring-playbook-turn.md:24 +msgid "In the `hosts` file we explicitly ask for your server's external IP address when defining `ansible_host`, because the same value is used for configuring coturn." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:30 -msgid "Adjusting firewall rules" +#: ../../../docs/configuring-playbook-turn.md:26 +msgid "If you'd rather use a local IP for `ansible_host`, add the following configuration to your `vars.yml` file. Make sure to replace `YOUR_PUBLIC_IP` with the pubic IP used by the server." msgstr "" #: ../../../docs/configuring-playbook-turn.md:32 -msgid "To ensure Coturn functions correctly, the following firewall rules and port forwarding settings are required when coturn is enabled:" +msgid "If you'd like to rely on external IP address auto-detection (not recommended unless you need it), set an empty value to the variable. The playbook will automatically contact an [echoip](https://github.com/mpolden/echoip)-compatible service (`https://ifconfig.co/json` by default) to determine your server's IP address. This API endpoint is configurable via the `coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable." msgstr "" #: ../../../docs/configuring-playbook-turn.md:34 -msgid "`3478/tcp`: STUN/TURN over TCP" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:35 -msgid "`3478/udp`: STUN/TURN over UDP" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:36 -msgid "`5349/tcp`: TURN over TCP" +msgid "[!NOTE] You can self-host the echoip service by using the [Mother-of-All-Self-Hosting (MASH)](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook. See [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/echoip.md) for the instruction to install it with the playbook. If you are wondering how to use it for your Matrix server, refer to [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/setting-up-services-on-mdad-server.md) for the overview." msgstr "" #: ../../../docs/configuring-playbook-turn.md:37 -msgid "`5349/udp`: TURN over UDP" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:38 -msgid "`49152-49172/udp`: TURN/UDP relay range" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:40 -msgid "If LiveKit's embedded TURN is enabled at the same time (for MatrixRTC/Element Call), keep the Coturn relay range distinct from LiveKit's relay range (`livekit_server_config_turn_relay_range_start`/`livekit_server_config_turn_relay_range_end`)." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:42 -msgid "💡 Docker configures the server's internal firewall for you. In most cases, you don't need to do anything special on the host itself." +msgid "If your server has multiple external IP addresses, the coturn role offers a different variable for specifying them:" msgstr "" #: ../../../docs/configuring-playbook-turn.md:44 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:46 -msgid "Define public IP manually (optional)" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:48 -msgid "If you enable coturn (either via Jitsi or manually), we recommend that you configure the public IP addresses of your server in the `vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:55 -msgid "If you'd like to rely on external IP address auto-detection (not recommended unless you need it), avoid configuring this variable. The playbook will automatically contact an [echoip](https://github.com/mpolden/echoip)-compatible service (`https://ifconfig.co/json` by default) to determine your server's IP address. This API endpoint is configurable via the `coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:57 -msgid "[!NOTE] You can self-host the echoip service by using the [Mother-of-All-Self-Hosting (MASH)](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook. See [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/echoip.md) for the instruction to install it with the playbook. If you are wondering how to use it for your Matrix server, refer to [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/setting-up-services-on-mdad-server.md) for the overview." -msgstr "" - -#: ../../../docs/configuring-playbook-turn.md:60 msgid "Change the authentication mechanism (optional)" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:62 +#: ../../../docs/configuring-playbook-turn.md:46 msgid "The playbook uses the [`auth-secret` authentication method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L186-L199) by default, but you may switch to the [`lt-cred-mech` method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L178) which [some report](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3191) to be working better." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:64 +#: ../../../docs/configuring-playbook-turn.md:48 msgid "To do so, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:70 +#: ../../../docs/configuring-playbook-turn.md:54 msgid "Regardless of the selected authentication method, the playbook generates secrets automatically and passes them to the homeserver and coturn." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:72 +#: ../../../docs/configuring-playbook-turn.md:56 msgid "If [Jitsi](configuring-playbook-jitsi.md) is installed, note that switching to `lt-cred-mech` will disable the integration between Jitsi and your coturn server, as Jitsi seems to support the `auth-secret` authentication method only." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:74 +#: ../../../docs/configuring-playbook-turn.md:58 msgid "Customize the Coturn hostname (optional)" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:76 +#: ../../../docs/configuring-playbook-turn.md:60 msgid "By default, Coturn uses the same hostname as your Matrix homeserver (the value of `matrix_server_fqn_matrix`, which is typically `matrix.example.com`)." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:78 +#: ../../../docs/configuring-playbook-turn.md:62 msgid "If you'd like to use a custom subdomain for Coturn (e.g., `turn.example.com` or `t.matrix.example.com`), add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:84 +#: ../../../docs/configuring-playbook-turn.md:68 msgid "The playbook will automatically:" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:85 +#: ../../../docs/configuring-playbook-turn.md:69 msgid "Configure Coturn to use this hostname" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:86 +#: ../../../docs/configuring-playbook-turn.md:70 msgid "Obtain an SSL certificate for the custom domain via Traefik" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:87 +#: ../../../docs/configuring-playbook-turn.md:71 msgid "Update all TURN URIs to point to the custom domain" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:89 +#: ../../../docs/configuring-playbook-turn.md:73 msgid "**Note**: Make sure the custom hostname resolves to your server's IP address via DNS before running the playbook." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:91 +#: ../../../docs/configuring-playbook-turn.md:75 msgid "Use your own external coturn server (optional)" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:93 +#: ../../../docs/configuring-playbook-turn.md:77 msgid "If you'd like to use another TURN server (be it coturn or some other one), add the following configuration to your `vars.yml` file. Make sure to replace `HOSTNAME_OR_IP` with your own." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:107 +#: ../../../docs/configuring-playbook-turn.md:91 msgid "If you have or want to enable Jitsi, you might want to enable the TURN server there too. If you do not do it, Jitsi will fall back to an upstream service." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:114 +#: ../../../docs/configuring-playbook-turn.md:98 msgid "You can put multiple host/port combinations if you'd like to." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:116 +#: ../../../docs/configuring-playbook-turn.md:100 msgid "Edit the reloading schedule (optional)" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:118 +#: ../../../docs/configuring-playbook-turn.md:102 msgid "By default the service is reloaded on 6:30 a.m. every day based on the `coturn_reload_schedule` variable so that new SSL certificates can kick in. It is defined in the format of systemd timer calendar." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:120 +#: ../../../docs/configuring-playbook-turn.md:104 msgid "To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:126 +#: ../../../docs/configuring-playbook-turn.md:110 msgid "**Note**: the actual job may run with a delay. See `coturn_reload_schedule_randomized_delay_sec` for its default value." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:128 +#: ../../../docs/configuring-playbook-turn.md:112 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:130 +#: ../../../docs/configuring-playbook-turn.md:114 msgid "There are some additional things you may wish to configure about the TURN server." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:132 +#: ../../../docs/configuring-playbook-turn.md:116 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:134 +#: ../../../docs/configuring-playbook-turn.md:118 msgid "`roles/galaxy/coturn/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:136 +#: ../../../docs/configuring-playbook-turn.md:120 msgid "Disabling coturn" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:138 -msgid "Coturn is only enabled by default when [Jitsi](configuring-playbook-jitsi.md) is enabled. In most instances, you don't need to explicitly disable it." +#: ../../../docs/configuring-playbook-turn.md:122 +msgid "If, for some reason, you'd like for the playbook to not install coturn (or to uninstall it if it was previously installed), add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:140 -msgid "To force the playbook to not install Coturn (even when Jitsi is enabled), add the following configuration to your `vars.yml` file:" +#: ../../../docs/configuring-playbook-turn.md:128 +msgid "In that case, Synapse would not point to any coturn servers and audio/video call functionality may fail." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:146 +#: ../../../docs/configuring-playbook-turn.md:130 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:148 +#: ../../../docs/configuring-playbook-turn.md:132 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:155 +#: ../../../docs/configuring-playbook-turn.md:139 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:157 +#: ../../../docs/configuring-playbook-turn.md:141 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-turn.md:159 +#: ../../../docs/configuring-playbook-turn.md:143 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-turn.md:161 +#: ../../../docs/configuring-playbook-turn.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-coturn`." msgstr "" diff --git a/i18n/translation-templates/docs/faq.pot b/i18n/translation-templates/docs/faq.pot index 09a086d35..a5b376804 100644 --- a/i18n/translation-templates/docs/faq.pot +++ b/i18n/translation-templates/docs/faq.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -573,266 +573,254 @@ msgid "How do I optimize this setup for a low-power server?" msgstr "" #: ../../../docs/faq.md:308 -msgid "For a low-power server, it's best to use an alternative homeserver implementation (other than [Synapse](configuring-playbook-synapse.md))." -msgstr "" - -#: ../../../docs/faq.md:310 msgid "You can disable some not-so-important services to save on memory." msgstr "" -#: ../../../docs/faq.md:317 -msgid "If you've installed [Jitsi](configuring-playbook-jitsi.md) (not installed by default), there are additional optimizations listed on its documentation page that you can perform." -msgstr "" - -#: ../../../docs/faq.md:320 -msgid "Synapse-specific optimizations" +#: ../../../docs/faq.md:327 +msgid "You can also consider implementing a restriction on room complexity, in order to prevent users from joining very heavy rooms:" msgstr "" -#: ../../../docs/faq.md:322 -msgid "If you're using [Synapse](configuring-playbook-synapse.md), you can also consider the following optimizations:" -msgstr "" - -#: ../../../docs/faq.md:332 -msgid "You can also consider [implementing a restriction on room complexity](configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts), in order to prevent users from joining very heavy rooms:" +#: ../../../docs/faq.md:337 +msgid "If you've installed [Jitsi](configuring-playbook-jitsi.md) (not installed by default), there are additional optimizations listed on its documentation page that you can perform." msgstr "" -#: ../../../docs/faq.md:340 +#: ../../../docs/faq.md:339 msgid "I already have Docker on my server. Can you stop installing Docker via the playbook?" msgstr "" -#: ../../../docs/faq.md:342 +#: ../../../docs/faq.md:341 msgid "Yes, we can stop installing Docker ourselves. Just use this in your `vars.yml` file:" msgstr "" -#: ../../../docs/faq.md:348 +#: ../../../docs/faq.md:347 msgid "I run another webserver on the same server where I wish to install Matrix. What now?" msgstr "" -#: ../../../docs/faq.md:350 +#: ../../../docs/faq.md:349 msgid "By default, we install a webserver for you ([Traefik](https://doc.traefik.io/traefik/)), but you can also use [your own webserver](configuring-playbook-own-webserver.md)." msgstr "" -#: ../../../docs/faq.md:352 +#: ../../../docs/faq.md:351 msgid "How is the effective configuration determined?" msgstr "" -#: ../../../docs/faq.md:354 +#: ../../../docs/faq.md:353 msgid "Configuration variables are defined in multiple places in this playbook and are considered in this order:" msgstr "" -#: ../../../docs/faq.md:356 +#: ../../../docs/faq.md:355 msgid "there are defaults coming from each role's defaults file (`role/matrix*/defaults/main.yml`). These variable values aim to be good defaults for when the role is used standalone (outside of this collection of roles, also called playbook)." msgstr "" -#: ../../../docs/faq.md:358 +#: ../../../docs/faq.md:357 msgid "then, there are overrides in `group_vars/matrix_servers`, which aim to adjust these \"standalone role defaults\" to something which better fits the playbook in its entirety." msgstr "" -#: ../../../docs/faq.md:360 +#: ../../../docs/faq.md:359 msgid "finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` file, which is the ultimate override" msgstr "" -#: ../../../docs/faq.md:362 +#: ../../../docs/faq.md:361 msgid "What configuration variables are available?" msgstr "" -#: ../../../docs/faq.md:364 +#: ../../../docs/faq.md:363 msgid "You can discover the variables you can override in each role (`roles/*/*/defaults/main.yml`)." msgstr "" -#: ../../../docs/faq.md:366 +#: ../../../docs/faq.md:365 msgid "As described in [How is the effective configuration determined?](#how-is-the-effective-configuration-determined), these role-defaults may be overridden by values defined in `group_vars/matrix_servers`." msgstr "" -#: ../../../docs/faq.md:368 +#: ../../../docs/faq.md:367 msgid "Refer to both of these for inspiration. Still, as mentioned in [Configuring the playbook](configuring-playbook.md), you're only ever supposed to edit your own `inventory/host_vars/matrix.example.com/vars.yml` file and nothing else inside the playbook (unless you're meaning to contribute new features)." msgstr "" -#: ../../../docs/faq.md:370 -#: ../../../docs/faq.md:382 +#: ../../../docs/faq.md:369 +#: ../../../docs/faq.md:381 msgid "**Note**: some of the roles (`roles/galaxy/*`) live in separate repositories and are only installed after your run `just roles` (or `make roles`) or `just update` (which automatically does `git pull` and `just roles`)." msgstr "" -#: ../../../docs/faq.md:372 +#: ../../../docs/faq.md:371 msgid "I'd like to adjust some configuration which doesn't have a corresponding variable. How do I do it?" msgstr "" -#: ../../../docs/faq.md:374 +#: ../../../docs/faq.md:373 msgid "The playbook doesn't aim to expose all configuration settings for all services using variables. Doing so would amount to hundreds of variables that we have to create and maintain." msgstr "" -#: ../../../docs/faq.md:376 +#: ../../../docs/faq.md:375 msgid "Instead, we only try to make some important basics configurable using dedicated variables you can see in each role. See [What configuration variables are available?](#what-configuration-variables-are-available)." msgstr "" -#: ../../../docs/faq.md:378 +#: ../../../docs/faq.md:377 msgid "Besides that, each role (component) aims to provide a `matrix_SOME_COMPONENT_configuration_extension_yaml` (or `matrix_SOME_COMPONENT_configuration_extension_json`) variable, which can be used to override the configuration." msgstr "" -#: ../../../docs/faq.md:380 +#: ../../../docs/faq.md:379 msgid "Check each role's `roles/*/*/defaults/main.yml` for the corresponding variable and an example for how use it." msgstr "" -#: ../../../docs/faq.md:384 +#: ../../../docs/faq.md:383 msgid "Installation" msgstr "" -#: ../../../docs/faq.md:386 +#: ../../../docs/faq.md:385 msgid "How do I run the installation?" msgstr "" -#: ../../../docs/faq.md:388 +#: ../../../docs/faq.md:387 msgid "See [Installing](installing.md) to learn how to use Ansible to install Matrix services." msgstr "" -#: ../../../docs/faq.md:390 +#: ../../../docs/faq.md:389 msgid "However, we recommend you to follow our installation guide, instead of jumping straight to installing." msgstr "" -#: ../../../docs/faq.md:392 +#: ../../../docs/faq.md:391 msgid "There are two guides available:" msgstr "" -#: ../../../docs/faq.md:394 +#: ../../../docs/faq.md:393 msgid "⚡ **[Quick start](quick-start.md)** (for beginners): this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"." msgstr "" -#: ../../../docs/faq.md:396 +#: ../../../docs/faq.md:395 msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide by starting with the **[Prerequisites](prerequisites.md)** documentation page." msgstr "" -#: ../../../docs/faq.md:398 +#: ../../../docs/faq.md:397 msgid "I installed Synapse some other way. Can I migrate such a setup to the playbook?" msgstr "" -#: ../../../docs/faq.md:400 +#: ../../../docs/faq.md:399 msgid "Yes, you can." msgstr "" -#: ../../../docs/faq.md:402 +#: ../../../docs/faq.md:401 msgid "You generally need to do a playbook installation. It's recommended to follow the full installation guide (starting at the [Prerequisites](prerequisites.md) page), not the [Quick start](quick-start.md) guide. The full installation guide will tell you when it's time to import your existing data into the newly-prepared server." msgstr "" -#: ../../../docs/faq.md:404 +#: ../../../docs/faq.md:403 msgid "This Ansible playbook guides you into installing a server for `example.com` (user IDs are like this: `@alice:example.com`), while the server is at `matrix.example.com`. If your existing setup has a server name (`server_name` configuration setting in Synapse's `homeserver.yaml` file) other than the base `example.com`, you may need to tweak some additional variables. This FAQ entry may be of use if you're dealing with a more complicated setup — [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" msgstr "" -#: ../../../docs/faq.md:406 +#: ../../../docs/faq.md:405 msgid "After configuring the playbook and installing and **before starting** services (done with `ansible-playbook … --tags=start`) you'd import [your SQLite](importing-synapse-sqlite.md) (or [Postgres](importing-postgres.md)) database and also [import your media store](importing-synapse-media-store.md)." msgstr "" -#: ../../../docs/faq.md:408 +#: ../../../docs/faq.md:407 msgid "I've downloaded Ansible and the playbook on the server. It can't connect using SSH." msgstr "" -#: ../../../docs/faq.md:410 +#: ../../../docs/faq.md:409 msgid "If you're using the playbook directly on the server, then Ansible doesn't need to connect using SSH." msgstr "" -#: ../../../docs/faq.md:412 +#: ../../../docs/faq.md:411 msgid "It can perform a local connection instead. Just set `ansible_connection=local` at the end of the server line in `inventory/hosts` and re-run the playbook." msgstr "" -#: ../../../docs/faq.md:414 +#: ../../../docs/faq.md:413 msgid "If you're running Ansible from within a container (one of the possibilities we list on our [dedicated Ansible documentation page](ansible.md)), then using `ansible_connection=local` is not possible." msgstr "" -#: ../../../docs/faq.md:416 +#: ../../../docs/faq.md:415 msgid "Maintenance and Troubleshooting" msgstr "" -#: ../../../docs/faq.md:418 +#: ../../../docs/faq.md:417 msgid "💡 Also see this page for generic information about maintaining the services and troubleshooting: [Maintenance and Troubleshooting](maintenance-and-troubleshooting.md)" msgstr "" -#: ../../../docs/faq.md:420 +#: ../../../docs/faq.md:419 msgid "Do I need to do anything to keep my Matrix server updated?" msgstr "" -#: ../../../docs/faq.md:422 +#: ../../../docs/faq.md:421 msgid "Yes. We don't update anything for you automatically." msgstr "" -#: ../../../docs/faq.md:424 +#: ../../../docs/faq.md:423 msgid "See our [documentation page about upgrading services](maintenance-upgrading-services.md)." msgstr "" -#: ../../../docs/faq.md:426 +#: ../../../docs/faq.md:425 msgid "How do I move my existing installation to another (VM) server?" msgstr "" -#: ../../../docs/faq.md:428 +#: ../../../docs/faq.md:427 msgid "If you have an existing installation done using this Ansible playbook, you can easily migrate that to another server following [our dedicated server migration guide](maintenance-migrating.md)." msgstr "" -#: ../../../docs/faq.md:430 +#: ../../../docs/faq.md:429 msgid "If your previous installation is done in some other way (not using this Ansible playbook), see [I installed Synapse some other way. Can I migrate such a setup to the playbook?](#i-installed-synapse-some-other-way-can-i-migrate-such-a-setup-to-the-playbook)." msgstr "" -#: ../../../docs/faq.md:432 +#: ../../../docs/faq.md:431 msgid "What is this `/matrix/postgres/data-auto-upgrade-backup` directory that is taking up so much space?" msgstr "" -#: ../../../docs/faq.md:434 +#: ../../../docs/faq.md:433 msgid "When you [perform a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql), we save the the old data files in `/matrix/postgres/data-auto-upgrade-backup`, just so you could easily restore them should something have gone wrong." msgstr "" -#: ../../../docs/faq.md:436 +#: ../../../docs/faq.md:435 msgid "After verifying that everything still works after the Postgres upgrade, you can safely delete `/matrix/postgres/data-auto-upgrade-backup`" msgstr "" -#: ../../../docs/faq.md:438 +#: ../../../docs/faq.md:437 msgid "I get \"Error response from daemon: configured logging driver does not support reading\" when I run `docker logs matrix-synapse`. Why?" msgstr "" -#: ../../../docs/faq.md:440 +#: ../../../docs/faq.md:439 msgid "To prevent double-logging, Docker logging is disabled by explicitly passing `--log-driver=none` to all containers. Due to this, you cannot view logs using `docker logs matrix-*`." msgstr "" -#: ../../../docs/faq.md:442 +#: ../../../docs/faq.md:441 msgid "See [this section](maintenance-and-troubleshooting.md#how-to-see-the-logs) on the page for maintenance and troubleshooting for more details to see the logs." msgstr "" -#: ../../../docs/faq.md:444 +#: ../../../docs/faq.md:443 msgid "The server fails to start due to the `Unable to start service matrix-coturn.service` error. Why and how to solve it?" msgstr "" -#: ../../../docs/faq.md:446 +#: ../../../docs/faq.md:445 msgid "The error is most likely because Traefik cannot obtain SSL certificates due to certain reasons such as wrong domain name configuration or port 80 being unavailable due to other services." msgstr "" -#: ../../../docs/faq.md:448 +#: ../../../docs/faq.md:447 msgid "If Traefik fails to obtain an SSL certificate for domain names such as `matrix.`, Traefik Certs Dumper cannot extract the SSL certificate out of there, and coturn cannot be started and the error occurs. Refer to these comments for details:" msgstr "" -#: ../../../docs/faq.md:450 +#: ../../../docs/faq.md:449 msgid "" msgstr "" -#: ../../../docs/faq.md:451 +#: ../../../docs/faq.md:450 msgid "" msgstr "" -#: ../../../docs/faq.md:453 +#: ../../../docs/faq.md:452 msgid "If you are not sure what the problem is, at first make sure that you have set the \"base domain\" (`example.com`, **not `matrix.example.com`**) to `matrix_domain`. You should be able to find it at the top of your `vars.yml`." msgstr "" -#: ../../../docs/faq.md:455 +#: ../../../docs/faq.md:454 msgid "If it is correctly specified, look Traefik's logs (`journalctl -fu matrix-traefik.service`) for errors by Let's Encrypt for troubleshooting." msgstr "" -#: ../../../docs/faq.md:457 +#: ../../../docs/faq.md:456 msgid "Miscellaneous" msgstr "" -#: ../../../docs/faq.md:459 +#: ../../../docs/faq.md:458 msgid "I would like to see this favorite service of mine integrated and become available on my Matrix server. How can I request it?" msgstr "" -#: ../../../docs/faq.md:461 +#: ../../../docs/faq.md:460 msgid "You can freely create an issue for feature request on the repository at GitHub [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/new/choose). Note this is a community project with no financial backing, and there is not assurance that your request would be eventually picked up by others and the requested feature would become available. The easiest way to get a feature into this project is to just develop it yourself." msgstr "" -#: ../../../docs/faq.md:463 +#: ../../../docs/faq.md:462 msgid "Also, please note that this playbook intends to focus solely on Matrix and Matrix-related services. If your request is not specific to Matrix, you may as well to consider to submit it to the [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook), maintained by the members behind this matrix-docker-ansible-deploy project. [This document on the interoperability](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md) describes how to deploy services along with the Matrix services easily." msgstr "" diff --git a/i18n/translation-templates/docs/installing.pot b/i18n/translation-templates/docs/installing.pot index cac1ebcb1..a13419bd2 100644 --- a/i18n/translation-templates/docs/installing.pot +++ b/i18n/translation-templates/docs/installing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -249,61 +249,61 @@ msgid "or join some Matrix rooms:" msgstr "" #: ../../../docs/installing.md:148 -msgid "via the *Explore rooms* feature in Element Web or some other clients, or by discovering them using this [matrix-static list](https://view.matrix.org). **Note**: joining large rooms may overload small servers. For tuning guidance on constrained hosts, see [Limit joining heavy rooms on constrained hosts](configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts)." +msgid "via the *Explore rooms* feature in Element Web or some other clients, or by discovering them using this [matrix-static list](https://view.matrix.org). **Note**: joining large rooms may overload small servers." msgstr "" -#: ../../../docs/installing.md:150 +#: ../../../docs/installing.md:149 msgid "or come say Hi in our support room — [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting." msgstr "" -#: ../../../docs/installing.md:151 +#: ../../../docs/installing.md:150 msgid "or help make this playbook better by contributing (code, documentation, or [coffee/beer](https://liberapay.com/s.pantaleev/donate))" msgstr "" -#: ../../../docs/installing.md:153 +#: ../../../docs/installing.md:152 msgid "⚠️ Keep the playbook and services up-to-date" msgstr "" -#: ../../../docs/installing.md:155 +#: ../../../docs/installing.md:154 msgid "While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**." msgstr "" -#: ../../../docs/installing.md:157 +#: ../../../docs/installing.md:156 msgid "The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities." msgstr "" -#: ../../../docs/installing.md:159 +#: ../../../docs/installing.md:158 msgid "Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date." msgstr "" -#: ../../../docs/installing.md:161 +#: ../../../docs/installing.md:160 msgid "Also, do not forget to update your system regularly. While this playbook may install basic services, such as Docker, it will not interfere further with system maintenance. Keeping the system itself up-to-date is out of scope for this playbook." msgstr "" -#: ../../../docs/installing.md:163 +#: ../../../docs/installing.md:162 msgid "For more information about upgrading or maintaining services with the playbook, take a look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)" msgstr "" -#: ../../../docs/installing.md:165 +#: ../../../docs/installing.md:164 msgid "Feel free to **re-run the setup command any time** you think something is wrong with the server configuration. Ansible will take your configuration and update your server to match." msgstr "" -#: ../../../docs/installing.md:171 +#: ../../../docs/installing.md:170 msgid "**Note**: see [this page on the playbook tags](playbook-tags.md) for more information about those tags." msgstr "" -#: ../../../docs/installing.md:173 +#: ../../../docs/installing.md:172 msgid "Make full use of `just` shortcut commands" msgstr "" -#: ../../../docs/installing.md:175 +#: ../../../docs/installing.md:174 msgid "After you get familiar with reconfiguring and re-running the playbook to maintain the server, upgrade its services, etc., you probably would like to make use of `just` shortcut commands for faster input." msgstr "" -#: ../../../docs/installing.md:177 +#: ../../../docs/installing.md:176 msgid "For example, `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/installing.md:179 +#: ../../../docs/installing.md:178 msgid "You can learn about the shortcut commands on this page: [Running `just` commands](just.md)" msgstr "" diff --git a/i18n/translation-templates/docs/just.pot b/i18n/translation-templates/docs/just.pot index 2352e5a89..5d0ad118b 100644 --- a/i18n/translation-templates/docs/just.pot +++ b/i18n/translation-templates/docs/just.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -162,17 +162,17 @@ msgid "Conditional service restart" msgstr "" #: ../../../docs/just.md:49 -msgid "When running `install-all` or `install-service` (whether via `just` or raw `ansible-playbook`), only services whose configuration or container image actually changed during the playbook run will be restarted. Unchanged services are left running (or get started if they were stopped). This reduces unnecessary downtime." +msgid "When using `just install-all` or `just install-service`, only services whose configuration or container image actually changed during the playbook run will be restarted. Unchanged services are left running (or get started if they were stopped). This reduces unnecessary downtime." msgstr "" #: ../../../docs/just.md:51 -msgid "When running with `setup-*` tags (e.g. `setup-all`, `setup-synapse`), all services are unconditionally restarted regardless of whether changes were detected. This is appropriate for setup's thorough \"full setup\" semantics." +msgid "When using `just setup-all`, all services are unconditionally restarted regardless of whether changes were detected. This is appropriate for `setup-all`'s thorough \"full setup\" semantics." msgstr "" #: ../../../docs/just.md:53 -msgid "`start-all` and `start-group` always restart all targeted services, since no installation tasks run during these commands." +msgid "`just start-all` and `just start-group` always restart all targeted services, since no installation tasks run during these commands." msgstr "" #: ../../../docs/just.md:55 -msgid "This behavior is automatically determined based on the playbook tags in use. It can be overridden with the `devture_systemd_service_manager_conditional_restart_enabled` variable. For example, to force unconditional restarts during installation: `just install-all --extra-vars='devture_systemd_service_manager_conditional_restart_enabled=false'`" +msgid "This behavior is controlled by the `devture_systemd_service_manager_conditional_restart_enabled` variable (default: `true`). To force unconditional restarts during installation, pass: `just install-all --extra-vars='devture_systemd_service_manager_conditional_restart_enabled=false'`" msgstr "" diff --git a/i18n/translation-templates/docs/maintenance-synapse.pot b/i18n/translation-templates/docs/maintenance-synapse.pot index 6de45f8de..5889aa790 100644 --- a/i18n/translation-templates/docs/maintenance-synapse.pot +++ b/i18n/translation-templates/docs/maintenance-synapse.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -145,61 +145,57 @@ msgid "Synapse's presence feature which tracks which users are online and which msgstr "" #: ../../../docs/maintenance-synapse.md:86 -msgid "On smaller servers, consider limiting joins to very complex rooms with [the room complexity guard](configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts)." -msgstr "" - -#: ../../../docs/maintenance-synapse.md:88 msgid "If you have enough compute resources (CPU & RAM), you can make Synapse better use of them by [enabling load-balancing with workers](configuring-playbook-synapse.md#load-balancing-with-workers)." msgstr "" -#: ../../../docs/maintenance-synapse.md:90 +#: ../../../docs/maintenance-synapse.md:88 msgid "[Tuning your PostgreSQL database](maintenance-postgres.md#tuning-postgresql) could also improve Synapse performance. The playbook tunes the integrated Postgres database automatically, but based on your needs you may wish to adjust tuning variables manually. If you're using an [external Postgres database](configuring-playbook-external-postgres.md), you will also need to tune Postgres manually." msgstr "" -#: ../../../docs/maintenance-synapse.md:92 +#: ../../../docs/maintenance-synapse.md:90 msgid "Tuning caches and cache autotuning" msgstr "" -#: ../../../docs/maintenance-synapse.md:94 +#: ../../../docs/maintenance-synapse.md:92 msgid "Tuning Synapse's cache factor is useful for performance increases but also as part of controlling Synapse's memory use. Use the variable `matrix_synapse_caches_global_factor` to set the cache factor as part of this process." msgstr "" -#: ../../../docs/maintenance-synapse.md:96 +#: ../../../docs/maintenance-synapse.md:94 msgid "**The playbook defaults the global cache factor to a large value** (e.g. `10`). A smaller value (e.g. `0.5`) will decrease the amount used for caches, but will [not necessarily decrease RAM usage as a whole](https://github.com/matrix-org/synapse/issues/3939)." msgstr "" -#: ../../../docs/maintenance-synapse.md:98 +#: ../../../docs/maintenance-synapse.md:96 msgid "Tuning the cache factor is useful only to a limited degree (as its crude to do in isolation) and therefore users who are tuning their cache factor should likely look into tuning autotune variables as well (see below)." msgstr "" -#: ../../../docs/maintenance-synapse.md:100 +#: ../../../docs/maintenance-synapse.md:98 msgid "Cache autotuning is **enabled by default** and controlled via the following variables:" msgstr "" -#: ../../../docs/maintenance-synapse.md:102 +#: ../../../docs/maintenance-synapse.md:100 msgid "`matrix_synapse_cache_autotuning_max_cache_memory_usage` — defaults to 1/8 of total RAM with a cap of 2GB; values are specified in bytes" msgstr "" -#: ../../../docs/maintenance-synapse.md:103 +#: ../../../docs/maintenance-synapse.md:101 msgid "`matrix_synapse_cache_autotuning_target_cache_memory_usage` — defaults to 1/16 of total RAM with a cap of 1GB; values are specified in bytes" msgstr "" -#: ../../../docs/maintenance-synapse.md:104 +#: ../../../docs/maintenance-synapse.md:102 msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` — defaults to `30s`" msgstr "" -#: ../../../docs/maintenance-synapse.md:106 +#: ../../../docs/maintenance-synapse.md:104 msgid "You can **learn more about cache-autotuning and the global cache factor settings** in the [Synapse's documentation on caches and associated values](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values)." msgstr "" -#: ../../../docs/maintenance-synapse.md:108 +#: ../../../docs/maintenance-synapse.md:106 msgid "To **disable cache auto-tuning**, unset all values:" msgstr "" -#: ../../../docs/maintenance-synapse.md:116 +#: ../../../docs/maintenance-synapse.md:114 msgid "Users who wish to lower Synapse's RAM footprint should look into lowering the global cache factor and tweaking the autotune variables (or disabling auto-tuning). If your cache factor is too low for a given auto tune setting your caches will not reach autotune thresholds and autotune won't be able to do its job. Therefore, when auto-tuning is enabled (which it is by default), it's recommended to have your cache factor be large." msgstr "" -#: ../../../docs/maintenance-synapse.md:118 +#: ../../../docs/maintenance-synapse.md:116 msgid "See also [How do I optimize this setup for a low-power server?](faq.md#how-do-i-optimize-this-setup-for-a-low-power-server)." msgstr "" diff --git a/i18n/translation-templates/docs/prerequisites.pot b/i18n/translation-templates/docs/prerequisites.pot index 6b1f6de34..5790801ea 100644 --- a/i18n/translation-templates/docs/prerequisites.pot +++ b/i18n/translation-templates/docs/prerequisites.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-04-03 11:56+0100\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 \n" "Language-Team: LANGUAGE \n" @@ -125,13 +125,33 @@ msgid "`443/tcp` and `443/udp`: HTTPS webserver" msgstr "" #: ../../../docs/prerequisites.md:60 -msgid "`8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. Some components like [Matrix User Verification Service](configuring-playbook-user-verification-service.md#open-matrix-federation-port) require this port to be opened **even with federation disabled**." +msgid "`3478/tcp`: STUN/TURN over TCP (used by [coturn](./configuring-playbook-turn.md))" msgstr "" #: ../../../docs/prerequisites.md:61 -msgid "potentially some other ports, depending on the additional (non-default) services that you enable in the **configuring the playbook** step (later on). Consult each service's documentation page in `docs/` for that." +msgid "`3478/udp`: STUN/TURN over UDP (used by [coturn](./configuring-playbook-turn.md))" +msgstr "" + +#: ../../../docs/prerequisites.md:62 +msgid "`5349/tcp`: TURN over TCP (used by [coturn](./configuring-playbook-turn.md))" +msgstr "" + +#: ../../../docs/prerequisites.md:63 +msgid "`5349/udp`: TURN over UDP (used by [coturn](./configuring-playbook-turn.md))" +msgstr "" + +#: ../../../docs/prerequisites.md:64 +msgid "`8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. Some components like [Matrix User Verification Service](configuring-playbook-user-verification-service.md#open-matrix-federation-port) require this port to be opened **even with federation disabled**." msgstr "" #: ../../../docs/prerequisites.md:65 +msgid "the range `49152-49172/udp`: TURN over UDP" +msgstr "" + +#: ../../../docs/prerequisites.md:66 +msgid "potentially some other ports, depending on the additional (non-default) services that you enable in the **configuring the playbook** step (later on). Consult each service's documentation page in `docs/` for that." +msgstr "" + +#: ../../../docs/prerequisites.md:70 msgid "[▶️](configuring-dns.md) When ready to proceed, continue with [Configuring DNS](configuring-dns.md)." msgstr ""